-
If lockers are considered full the logic should probably still allow it if the patron already has a pickup scheduled for that exact timeslot/date.
This would probably clean up some of the situatio…
-
For now, the internal features are not supported. Supporting them would then allow the interaction between the core, the ba and other annexes.
See an example of a model that uses the internal feature…
juli1 updated
10 years ago
-
Submitted on behalf of Danielle Stewart after a joint review of this section with John Hatcliff and Jerome Hugues.
We need to clarify 5.4.2 to build a precise definition of the following concepts
…
-
(this issue was referenced as G-04 in the [SaeAadlWiki](https://wiki.sei.cmu.edu/sae-aadl-subcommittee/index.php/Errata_from_the_Behavior_Annex))
Missing formal semantics for the Behavior Annex.
It …
-
## Summary
OSATE warns me that I need complete states on behavior specifications for `device` and `memory` types (those are all I've tested). When I add complete states, it tells me that I am not a…
-
PolyORB-HI/C and PolyORB-HI/Ada backends do not correctly handle situations where systems are inside systems, so as to model deep hierarchy.
yoogx updated
3 years ago
-
I would like to see the ability to have ports which are contained in other ports. Both the outer port and the inner ports should be useable as an edge end. This capability should allow for arbitrary l…
-
An AADL subprogram can have multiple language (e.g. as part of its transitive closure, mixing C and C++)
We should rework the makefile to address this
yoogx updated
4 years ago
-
Features may be grouped differently in different subsystems and need to be connected.
It is desirable to declare connections that can identify individual features in feature groups when connecting two…
-
Currently error type libraries are implicitly assigned the name of the package they reside in. Furthermore, only one error type library can be included in one EMV2 library clause.
Proposal to require…