-
## Summary
When running an FTA on the attached model no fault tree is created. There is also no error message displayed.
## Expected and Current Behavior
Either a fault tree should be created…
-
## Summary
When calling GetProperties.getDispatchProtocol on a ThreadType, null is returned in code written long ago.
## Expected and Current Behavior
Return of an EnumerationLiteral is expe…
-
The new AADL Auth setting added on May 14/15th 2019 when running the command on my machines for some reason deletes the cert private key. The first running of the commandlet will connect to the Office…
-
Example model: AutonomousVehicleSystem from https://github.com/bisc/collision_detection_aadl.git
Instantiate system implementation `avoidance_subsystem.impl` in `avoidance_subsystem.aadl`
Connection i…
-
## Summary
The Osate always said that my behavior annex was wrong, but I think it is correct.
## Expected and Current Behavior
![Error](https://user-images.githubusercontent.com/29940173/62…
-
## Summary
The error decorations in the navigator should reflect error markers on the resource.
## Expected and Current Behavior
When an error is fixed in an aadl file the error decoration in…
-
If I make a small error like swapping a colon and semicolon, OSATE flags the _entire_ BA block as being an error.
```aadl
thread group implementation threadB.impl
subcomponents
…
-
When I select a group of objects in an AADL diagram and move them, anchor points on flows and connections between the objects don't move with them. By anchor points I'm referring to "turns" in the lin…
-
## Summary
AADL allows a flow source implementation to begin with a data subcomponent. However, the current OSATE implementation gives an error on the subsequent connection in the flow implementa…
-
## Summary
When running FTA on a composite state, the resulting probability was zero. So I created FTA_example.aadl (attached) which has the smallest difference between FTA that gets the correct r…