Run analysis on implementation

[joeseibel]

For analyses that operate on the instance model, it should be possible to run them on an implementation. The analysis should automatically generate the instance before running the analysis. This request came up during the AADL standards committee meeting.

[lwrage]

We need to find a generic solution that can be added to all existing instance model based analyses.

[AaronGreenhouse]

Going to experiment with this using the bus load analysis which was written with a new action handler, and the flow latency analysis, which was written the old way.

It sounds like people want to be able to invoke an analysis on a component implementation, and then have one of the following things happen

• If the implementation is already instantiated, have the analysis run on that instance.
• If the implementation is not already instantiated, instantiate it, and then run over the instance.

[AaronGreenhouse]

Work with the new bus load analysis first.

I need to

1. Update the plugin.xml so that the command is active for component implementations (basically anything that can be instantiated) (see the instantiation commands).
2. Update the kick off job to find all the component implementations
3. For each component implementation determine if it already has an instantiation. IF so, add it to the regular list of aaxl files to process. If not, we need to add it to a new list of files to be instantiated.
4. Instantiate the necessary files. If there is some kind of failure report it, otherwise add the instantiated file to the list of aaxl files to process.
5. Process the aaxl files as usual.

[lwrage]

Running an analysis on an implementation should always create a fresh instance model.