Package Relationships Sample Clauses

Package Relationships. The Infrastructure::CoreConstructs::Relationships subpackage of EAST-ADL2 defines general- purpose relationship constructs that may be used to model dependencies between structural constructs. The purpose of the metaclasses in the Infrastructure::CoreConstructs::Relationships domain metamodel package is to specify rigorously ("formally") the various relationships that may exist between ADL basic constructs. 6.2.3.1 EAST-ADL2 – Construct for Relationships, «ADLRelationship« The EAST-ADL2 construct for relationships makes it possible for various relationships in the language to be owned by a specific context. A specialization of a relationship is for example the EAST-ADL2 satisfy requirement relationship. 6.2.3.2 EAST-ADL2 – Derive Requirements Relationship, «ADLDeriveReq« The derive requirement relationship in EAST-ADL2 is an automotive specialization of the SysML derive requirement relationship [4]. The EAST-ADL2 derive requirement relationship signifies a dependency relationship in-between two sets of EAST-ADL2|SysML requirement constructs, showing the relationship when a set of derived client EAST-ADL2|SysML requirements are derived from a set of supplier EAST-ADL2|SysML requirements. As with other UML dependencies [4] the dependency arrow direction points from the derived (client) EAST-ADL2|SysML requirement, to the (supplier) EAST-ADL2|SysML requirement. The following constraints apply to the EAST-ADL2 derive requirement relationship: [1] The first and second constraint in the SysML specification related to derive requirement relationship [4] is not applicable. [2] The supplier must be an element stereotyped by EAST-ADL2|SysML requirement or one of EAST-ADL2|SysML requirement subtypes. [3] The client must be an element stereotyped by EAST-ADL2|SysML requirement or one of EAST-ADL2|SysML requirement subtypes. 6.2.3.3 EAST-ADL2 – Refine Requirements Relationship, «ADLRefine« The refine requirement relationship in EAST-ADL2 signifies a dependency relationship in-between an EAST-ADL2|SysML requirement and an EAST-ADL2 entity, showing the relationship when a client EAST-ADL2 entity construct refines the supplier EAST-ADL2|SysML requirement. As with other UML dependencies [4] the arrow direction points from the EAST-ADL2 entity that refines the EAST-ADL2|SysML requirement to the refined (supplier) EAST-ADL2|SysML requirement. The following constraints apply to the EAST-ADL2 refine requirement relationship: [1] The supplier must be an element stereotyped by E...