AS5506D -- AADLv2.3 Document preparation

This issue tracks the preparation of AS5506D document. This document is a revision of the AADLv2.2 core document and addresses the following errata:

Extensions to AADLv2.2: the following are additions to AADLv2.2

saeaadl/aadlv2.2#29 extend flow specification to reach down multiple levels in nested feature groups
saeaadl/aadlv2.2#39 add flow spec between subprogram access
saeaadl/aadlv2.2#40 added abstract category in reference and classifier property types
saeaadl/aadlv2.2#43 flow specifications can connect to a feature in an array
saeaadl/aadlv2.2#51 introduced a pattern to capture multi-core processors using system category
saeaadl/aadlv2.2#53 add Kbps, MBps and Gbps units and Kibits variants
saeaadl/aadlv2.2#61 adds additional legality rules for connections in section 9.1
saeaadl/aadlv2.2#62 has been significantly revised the section 5.4.2 on thread dispatching to bring definitions in order
saeaadl/aadlv2.2#63 and saeaadl/aadlv2.2#64 addressed issues in the definition of Input_Time, Output_Time, and the notion of frozen port
saeaadl/aadlv2.2#68 revised definition for Classifier_Matching_Rule and Classifier_Substitution_Rule

Bugfixes to AADLv2.2: the following are corrections to AADLv2.2

saeaadl/aadlv2.2#13 clarified naming rules for flow implementation
saeaadl/aadlv2.2#28 corrected the BNF for flow_feature_identifier
saeaadl/aadlv2.2#35 clarified 12 (L2) in the case a component extends another one
saeaadl/aadlv2.2#37 clarified legality rules for property constants
saeaadl/aadlv2.2#41 clarified that flow implementations are optional
saeaadl/aadlv2.2#46 added virtual bus and bus as subcomponents of memory components, since they can have provides access to those elements.
saeaadl/aadlv2.2#47 added connection to bus and virtual bus to allow for mode trigger propagation
saeaadl/aadlv2.2#49 clarified legality rule (L3) for subprogram group and thread group
saeaadl/aadlv2.2#66 updated the definition of Data_Size to match usage in toolsets
saeaadl/aadlv2.2#67 added a consistency rule in A.2 that only trigger features might be listed in Dispatch_Trigger.

No action, as the issue reported is not sufficiently described

Editorial updates

saeaadl/aadlv2.2#10 corrected a typo
saeaadl/aadlv2.2#11 corrected reference to Base_Types in A.9
saeaadl/aadlv2.2#12 clarified with runtime services can be called by the user
saeaadl/aadlv2.2#14 clarified that Compute_Execution_Time is a upper-bound for any execution triggered by the component this property applies to.
saeaadl/aadlv2.2#16 clarified that 9.1 (L7) only applies to feature groups nested features
saeaadl/aadlv2.2#36 clarified the definition of a deterministic transition function for modes.

Property sets have been updated and are at https://github.com/saeaadl/aadlv2.2

saeaadl / aadlv2.2