-
## Summary
In the following AADL model, the end to end flow "processing_flow" of system implementation "Test.basic" is not generated in the instance model.
## AADL code to reproduce the problem
…
-
When I open an instance file, I do not see any properties for flow declarations.
I can see some information about a flow in the Properties view. However, when I open an AADL Properties view on a f…
-
## Summary
In the following AADL model, a flow path implementation is specified that uses refined connections. The connections in the flow path are shown as errors in the AADL text editor.
## AADL…
-
ocarina version
```
$ ocarina --version
Ocarina 2017.x (Working Copy from re88d7c9)
Copyright (c) 2003-2009 Telecom ParisTech, 2010-2019 ESA & ISAE
```
I use cheddar (supported by ocarina) t…
-
-- What is the OSATE interpretation of the AADL standard as to whether
-- certain forms of subprogram calls inside subprogram calls sequences
-- do or do not implicitly declare a subprogram subcompo…
-
## Summary
Creating a new AADL package inserts it as the first element in the project.
## Expected and Current Behavior
The common navigator framework tries to insert the new package in the c…
-
## Summary
It would be convenient to have property constants that have the correct type proposed in content assist. Currently property constants are not proposed on Ctrl+Space.
## Environment
…
-
Errors reported by the behavior annex legality checker are generated but not reported to the user. For example, I (incorrectly) used a state transition with a `timeout` dispatch condition on a process…
-
When an end to end flow refers to a data access, an error is reported complaining that data access references are only permitted at the beginning or end of an end to end flow. This validation doesn't …
-
AADL model units are currently contributed via an extension point. We need a registry that can be populated programmatically to operate in standalone mode.
child of #1538