2.2 What’s New in OSATE 1.1
OSATE has been updated to run under Eclipse 3.1 and EMF 2.1.  This combination is now the preferred execution platform.  Because EMF 2.1 is not compatible with Eclipse 3.0.2, we have made the decision also release a version of OSATE 1.1 that runs under Eclipse 3.0.2 and EMF 2.0.  This legacy support is for the 1.1 release only, and will not be continued with future releases.
The following are updated and new capabilities in OSATE 1.1:
    • AADL processing menu and analysis menus are now organized hierarchically. Root menus are named “OSATE” and “Analysis”.
    • The “AADL” context menu has also been improved.
    • OSATE now features wizards for creating new property set, package, and specification files, both as textual aadl specifications and aaxl model files.
    • OSATE now has “annex extension points” to ease the integration of plug-ins that support AADL Annex extensions.
    • Standard property set loading is improved.
    • OSATE can now generate HTML report files logging marker results from the “Problems” view.
    • The “AADL Property Values” view can now be used to create new property associations and edit existing ones.
    • Instance model generation now includes end-to-end flow instances for modal systems. Problems with access connection instances have been corrected.
    • Predeclared ports (e.g., “Dispatch”) are now explicitly created in the model if they are used in connections.
    • Checking for circular references among property values is improved.  This check used to be part of the build process, but it is now a separate analysis because it is relatively time consuming.
    • OSATE now detects if a model has containment cycles, i.e., a component contains a second component, whose classifier is that of the former component. This is detected at instantiation time.
    • Meta model updated so that connection instances can record in which mode transitions they exist.
    • Meta model updated to be compliant with the standardized AADL Meta Model & XML/XMI Interchange Format Annex. ComponentFeatures class is now called Features (no impact on XML representation).  End-to-end flow instances have reference to both ModeInstance and SystemOperationMode. The packageSpec containment label was renamed to aadlPackage to be consistent with other containment labels (change in XML element tag).  The name spaces of the meta model packages now include ///AADL as prefix – this requires the second line in existing aaxl files to be updated to include this prefix, e.g., xmlns:core="http:///AADL/core".  A simple way of migrating to the updated XML representation is to rebuild all models from their text representation (aadl files).
    • ModeTransitions, ModeTransitionInstances, and ConnectionInstances all have unique non-null names.
    • OSATE is compliant with the AADL Errata Sheet of July 2005.
    • Analysis result reporting through Eclipse Markers:  Each analysis plug-in now has its own Marker subclass. This allows visibility of problems to be controlled per analysis, and one analysis does not delete the markers of other analyses.  Plug-in developers can introduce their own Marker subclasses (see plug-in development guide).
    • The security level and safety level analyses are now mode savvy.