New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run analysis on implementation #841
Comments
We need to find a generic solution that can be added to all existing instance model based analyses. |
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
|
Work with the new bus load analysis first. I need to
|
Running an analysis on an implementation should always create a fresh instance model. |
First thing I need to do is modify the
Should be abstracted to both instantiate and reinstantiate engines. End result should be |
Adding this to the 3rd-party API epic because it relates to fixing up the abstract handlers for OSATE analyses. |
Created The instantiate and reinstantiate handlers have been updated to use the engines. |
Okay, back to updating
|
Updated It was more work to update the |
API Issue Should make a template in the This is the |
Should update the old |
Added
Private definitions are meant to be used internally to define public definitions. Public definitions are to be part of the 3rd party API and should be documented. The above has
|
Updated the instantiate and reinstantiate commands to use the new definitions. |
Added "Reinstantiate" to the instance editor and instance outline view context menus. |
Added Bus load analysis to the instance editor and instance outline view context menus. Updated the NewAbstractAaxlHandler to deal with |
Cleaned up
This is used by toolbar commands. |
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.
The text was updated successfully, but these errors were encountered: