Webel: SysML: TIP: Try "reverse" time ordered effect-from-cause Dependencies. Because it's harder to depend on something that does not already exist!
Webel: SysML: TIP: CONVENTION (default policy suggestion): Use reverse time ordering for Dependency, reserve Usage, PackageImport, ElementImport for software dependencies
The UML «Trace» and SysML Trace can't be applied to a Slot as target (because Slot is just an Element, not a NamedElement).
Webel: A plain Dependency that is not stereotyped is always strictly timed-ordered; the supplier (target) must exist before the client (source).
A Usage is a Dependency in which the client Element requires the supplier Element (or set of Elements) for its full implementation or operation. Source Unified Modeling Language 2.5.1
This means that the complete semantics of the client Element(s) are either semantically or structurally dependent on the definition of the supplier Element(s). Source Unified Modeling Language 2.5.1
A Dependency is a Relationship that signifies that a single model Element or a set of model Elements requires other model Elements for their specification or implementation. Source Unified Modeling Language 2.5.1
AllocateActivityPartition::1_actions_on_client_ends An Action appearing in an "AllocateActivityPartition" shall be the /client (from) end of an "allocate" dependency. The element that represents the "AllocateActivityPartition" shall be the /supplier ... Source OMG Systems Modeling Language (SysML) 1.6
SysML-1.6: The constraint that ''An Action appearing in an “AllocateActivityPartition” shall be the /client (from) end of an “allocate” dependency.' is not compatible with all Activity Diagram swimlane configurations.
AbstractRequirement::/master : AbstractRequirement [0..*] This is a derived property that lists the master requirement for this slave requirement. The master attribute is derived from the supplier of the Copy dependency ... Source OMG Systems Modeling Language (SysML) 1.6
The master/slave relationship is indicated by the use of the copy relationship. Source OMG Systems Modeling Language (SysML) 1.6
A slave requirement is a requirement whose text property is a read-only copy of the text property of a master requirement. The text property of the slave requirement is constrained to be the same as the text property of the related master requirement. Source OMG Systems Modeling Language (SysML) 1.6
A Verify relationship is a dependency between a requirement and a test case or other model element that can determine whether a system fulfills the requirement. As with other dependencies, the arrow direction points from the (client) element to the (suppl Source OMG Systems Modeling Language (SysML) 1.6
Figure 16-5 illustrates the use of the Copy dependency to allow a single requirement to be reused in several requirements hierarchies. The master tag provides a textual reference to the reused requirement. Source OMG Systems Modeling Language (SysML) 1.6
Figure 16-5: Use of the copy dependency to facilitate reuse Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6 specification diagrams: 16 Requirements Slide kind SysML Requirement Diagram
Copy::2_same_text The text property of the client requirement is constrained to be a read-only copy of the text property of the supplier requirement and this applies recursively to all subrequirements Source OMG Systems Modeling Language (SysML) 1.6
Copy::1_source_and_taget_are_requirements A Copy dependency may only be created between two NamedElements that have a subtype of the abstractRequirement stereotype applied Source OMG Systems Modeling Language (SysML) 1.6
When a Copy dependency exists between two requirements, the requirement text of the client requirement is a read-only copy of the requirement text of the requirement at the supplier end of the dependency. Source OMG Systems Modeling Language (SysML) 1.6
A Copy dependency created between two requirements maintains a master/slave relationship between the two elements for the purpose of requirements re-use in different contexts Source OMG Systems Modeling Language (SysML) 1.6
A Copy relationship is a dependency between a supplier requirement and a client requirement that specifies that the text of the client requirement is a read-only copy of the text of the supplier requirement. Source OMG Systems Modeling Language (SysML) 1.6
Satisfy::getSatisfies (in ref : NamedElement) : AbstractRequirement [0..*] Source OMG Systems Modeling Language (SysML) 1.6
Satisfy::1_supplier_is_requirement The supplier shall be an element stereotyped by any subtype of «AbstractRequirement». Source OMG Systems Modeling Language (SysML) 1.6
As with other dependencies, the arrow direction points from the satisfying (client) model element to the (supplier) requirement that is satisfied. Source OMG Systems Modeling Language (SysML) 1.6
DeriveReqt::1_supplier_is_requirement The supplier shall be an element stereotyped by a subtype of AbstractRequirement. Source OMG Systems Modeling Language (SysML) 1.6
As with other dependencies, the arrow direction points from the derived (client) requirement to the (supplier) requirement from which it is derived. Source OMG Systems Modeling Language (SysML) 1.6
A DeriveReqt relationship is a dependency between two requirements in which a client requirement can be derived from the supplier requirement. Source OMG Systems Modeling Language (SysML) 1.6
