RequirementsHierarchy represents a larger unit or module of specification information. It is used to bundle several Requirements which are semantically related to each other. Thus, to preserve the ordering of requirement specification objects, the order of child hierarchies is very important here.<br/><br/>The RequirementsHierarchy with its reference to Requirement is the basic element for structuring requirement information into a forest structure.<br/><br/>RequirementsHierarchy correponds to ReqIF SpecHierarchy when exporting to ReqIF so that for each containedRequirement an associated RequirementsHierarchy is created. This way EAST-ADL users don’t need to create RequirementsHierarchy items per Requirement.<br/><br/>Constraints:<br/>[1] Only non-root RequirementsHierarchy which is contained in another RequirementHierarchy are allowed to reference a Requirement.<br/><br/>Semantics:<br/>RequirementsHierarchy organizes Requirements in groups. The semantics of the group is user-defined.<br/><br/>Notation:<br/>RequirementsHierarchy is shown as a solid-outline rectangle containing the name. Contained entities may also be shown inside (White-box view)<br/><br/>Extension: Package<br/>
Name: childHierarchy
Sub hierarchies of a requirements hierarchy. Sub hierarchies may have references (each time max. one) to requirement specification objects. To preserve the original ordering of requirement specification objects, the ordering of sub hierarchies is very important here.
Name: childHierarchy
Sub hierarchies of a requirements hierarchy. Sub hierarchies may have references (each time max. one) to requirement specification objects. To preserve the original ordering of requirement specification objects, the ordering of sub hierarchies is very important here.
