Home
>
7. Managing the Results of an OSATE Plug-in
>
7.1 Comparison of Result Management Mechanisms
|
Previous
Next
|
|
|
|
|
|
- separation of recording
and reporting - The plug-in records them, the user chooses
when to view them.
- Persistent beyond the execution
of the plug-in. Markers are kept with the resources
(files).
- Auto-reset on plug-in execution.
- Categories of markers for
different plug-ins.
- Markers can also be used
non-persistently by changing the value of its persistent
attribute in the marker definition (see above).
- Decoration icon on the
resource in the Navigator.
- Marker location indicators
on the sidebar of an open editor window.
- Markers are accessible
programmatically via org.eclipse.core.resources.
For
more details see Section 8 Persistent Markers with AADL Models.
|
|
- Immediate reporting.
- Synchronous or asynchronous
popup. Synchronous popup requires user confirmation
(ok button) before letting the user proceed. Asynchronous popup produces the
window, but lets the user change the focus without closing the window.
- Messages only exist for
the duration of the popup.
|
|
- Persistently kept in the
AADL model.
- New properties can be introduced
through the property set construct in AADL
- AADL properties, both predeclared
and those introduced through property sets, are
accessible programmatically via the AADL model API for AADL properties; results of
one plug-in can be used by other plug-ins
- All AADL properties are
visible via AADL model via AADL model presentation
mechanisms such as the AADL Property Viewer, Graphical editor etc.
|
|
- In-core addition of information
to AADL model without requiring extensions to the
model representation itself
- Information is accessible
programmatically through the AADL model objects by
utilizing an adapter concept. A generic set of adapters for each class in the AADL meta
model and an adapter factory have already been generated by EMF. They can be
subclassed for plug-inspecific uses.
- Allows model object specific
information to be passed in context between different
passes of one OSATE plug-in or between plug-ins executed in succession.
|
|
- Persistent record in file
system
- Visible a resource in Navigator
- Permits use of representation
appropriate for analysis or generation tool (e.g.,
generation of textual AADL or MetaH)
- Supports interchange representations
of external tools
|
|
- Use EMF to define meta
model for target object model/XML; this can be achieved by
importing an existing XML schema of an object model or by creating a meta model
interactively.
- Generate the target object
model in-core by traversing the AADL object model; add
the root object as content of a (EMF) resource; call on save method of resource to
store as XML document
- This method is used to
generate the AADL instance model
|
|
|
|