DeriveRequirement : public class
Created: |
2006-10-19 11:50:25 |
Modified: |
2010-04-09 17:14:01 |
|
Project: |
|
Author: |
|
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Advanced: |
|
UUID: |
{06E94250-F158-4b2f-AF61-EC3DDB65AB41} |
Appears In: |
RequirementsRelationships |
<p>The DeriveRequirement is a relationship metaclass, which signifies a dependency relationship between two sets of Requirements, showing the relationship when a set of derived client Requirement (client requirement) is derived from a set of Requirements (supplier requirement).<br/></p><p><br/></p><p>Semantics:<br/></p><p>The DeriveRequirement metaclass signifies a derived/derived by relationship between Requirements, where the modification of the supplier Requirement may impact the derived client Requirement.<br/></p><p><br/></p><p>Notation: <br/></p><p>A DeriveRequirement relationship is shown as a dashed arrow between two Requirements. The Requirement at the tail of the arrow (the derived Requirement) depends on the Requirement at the arrowhead (the Requirement derived from).<br/></p><p><br/></p><p>Extension: <br/></p><p>To specialize SysML DeriveReqt, which specializes UML2 stereotype Trace, which extends Dependency.<br/></p><p><br/></p><p>Temporary change in the profile (to overcome bug in Eclipse/UML2 concerning standard stereotypes)<br/></p><p>- added extension towards Dependency<br/></p><p>- removed generalization link towards SysML::DeriveReqt<br/></p><p><br/></p><p>TODO:<br/></p><p>Move to Requirement package<br/></p>
- Associations To
- Other Links
Element |
Source Role |
Target Role |
Details |
Requirement
Class
|
Name:
|
Name: derived
The set of requirements derived from the supplier requirement.
|
|
Requirement
Class
|
Name:
|
Name: derivedFrom
The set of requirements that the client requirement are derived from.
|
|