OSATE Installation Instructions
From DaVinci
Team, Below follow some instructions as how to install the latest complete OSATE toolset.
The following tools are required.
- Java SDK 1.4.10 (or possibly 1.5.6). I used 1.4.10
- Eclipse 3.1.1
- EMF 2.1.1 (the meta model framework)
- Omondo UML 2.1.0 (useful for looking at the AADL metamodel in UML)
- ADT (ATL Development Toolkit) 20051102 (I see that there is a later release 20060113, but since we are not using ATL this sprint we can stick with the slightly older version )
- OSATE 1.1
I am in process of uploading, to the FTP server, a zip file upload/complete_osate_installation_1_21_2006.zip, which contains everything mentioned above. I let you know when the upload is finished....
Install in the following order:
- Your Java SDK of choice. The zip contains both 1.4 and 1.5 windows versions
- ATL-eclipse-3.1.1-win32.zip. This zip was kindly provided by Peter. It contains Eclipse, EMF and ADT. Double click and choose for instance C:/eclipse as destination folder
- osate-frontend-1.1-11182005.zip. This is the OSATE plugin, which should be installed on top of Eclipse.
- eclipseUML_E310_studioEdition_2.1.0.beta.20050927.jar. Double-click and follow the instructions given in license_installation_instructions.txt
The upload zip also contains the example system provided by Peter. It shows a system 'before' and 'after' our forthcoming port-colapsing algorithm has been run on a small AADL system. You'll find the systems in complete_installation_1.21.2005\portgroupex
I'd think this works also on MAC, but I couldn't test it for obvious reasons. I don't know why Peter has a 'win32' in his zip file though. To my knowledge, everything should be pure Java. Let me know if you have any problems.
Below follow an explanation regarding the portgroup examples from Peter
- The file portgroups.aadl contains the original model that should be optimized. It has two models as two SSHipNavigation implementations. The first model has only one layer of components. Here the optimization can be performed within the ShipNavigation implementation without recursing down the hierarchy. The second model expands the systems down to the thread level. In this case we have to deal with multiple levels of the hierarchy and possible application of the optimization at each.
- The second file optportgroups.aadl shows the result of the optimization of the single layer system. It lets you work out the basics of the optimization. It can work on the top level implementation.
- The third file optportgroupsdetailed.aadl propagated the port groups down the hierarchy and also lets you apply the grouping at the lower layers. In this case you may want to consider operating on the instance model to identify the possible groupings at the leaf nodes (thread to thread connections).