Experiment ID3 - Acme system lookup
Element | Content Description |
Experiment ID | ID3 |
Responsible Engineer | Snehal |
Purpose | Investigate how we can look for system files in AcmeStudio. |
Expected Outcomes | After experiment, we know that we can implement "Link an instance to Acme System" basic flow in UC1 |
Artifacts | Software: svn://waterfall.able.cs.cmu.edu/arch-evol/experiments/trunk/sfulzele/edu.cmu.pangea.experiments/AE_UC01_LookupAcmeSystem svn://waterfall.able.cs.cmu.edu/arch-evol/experiments/trunk/sfulzele/edu.cmu.pangea.experiments/AE_UC01_LookupAcmeSystem_edit svn://waterfall.able.cs.cmu.edu/arch-evol/experiments/trunk/sfulzele/edu.cmu.pangea.experiments/AE_UC01_LookupAcmeSystem_diagram |
Experiment Description | - This experiment is a GMF application built on top of AcmeStudio. The objective was to get the acme system list within the acme file from GMF application (AE overview diagram). - Run the project as an eclipse application. A new menu item 'GMFAction' will get created under Design menu. Clicking GMFAction will try to search the hardcode 'System1.acme' resource within the runtime eclipse instance and output the names on to the console. - The related code is in a file called GMFAction.java under the package acmetest (in the project AE_UC01_LookupAcmeSystem). |
Duration | 02/20/2008 - 02/27/2008 (Hours spent - 7 hours) |
Results | - The experiment has hard coded a resource name and looked up that resource from outside the context of the AcmeStudio. |
Recommendations | - We need to learn which things can be best achieved using Eclipse plug-in API and which services AcmeStudio API provides us. For this, a continuous learning curve is required and the best possible way to get this expertise is by doing more such experiments, especially where GMF + Acme + Eclipse is involved. |