Refining requirements

Gallery
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
Section
16:01: Requirements engineering in SysML
UML keywords
tagged value
element property
UseCase
SysML keywords
Requirement
AbstractRequirement::/refinedBy
Refine
Refine::getRefines(in ref : NamedElement)
Slide kind
SysML Requirement Diagram
Click on the image to view it full size
Here both the Note callout and the element property compartment styles have been used to display the information about the /refinedBy query on a Requirement and the /refines query on a UseCase (a NamedElement) that refines the Requirement where:
SysML-1.6: 'Refine::getRefines (in ref : NamedElement) : AbstractRequirement [0..*] The query getRefines() gives all the requirements that are suppliers ("to"end of the concrete syntax) of a «Refine» relationships whose client is the element in parameter ...'
We explore next the Satisfy relationship.
Up next
Satisfying Requirements and the Satisfy relationship
Notes
[DISPLAY, QUESTION, STYLE, TOOL] MagicDraw/Cameo: How disable icons in requirement relationship compartments and tagged values compartment on Requirement symbol?
Snippets (quotes/extracts)
  [SysML-1.6] The Refine stereotype specializes UML4SysML Refine and DirectedRelationshipPropertyPath to enable refinements to identify their sources and targets by a multi-level path of accessible properties from context blocks for the sources and targets.
  [SysML-1.6] SysML has added some notational extensions to represent stereotype properties in compartments as well as notes.
  [SysML-1.6] Refine::getRefines (in ref : NamedElement) : AbstractRequirement [0..*] The query getRefines() gives all the requirements that are suppliers ("to"end of the concrete syntax) of a «Refine» relationships whose client is the element in parameter ...
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Figure D.11 - Establishing HSUV Requirements Hierarchy (containment)
Figure D.12 - Establishing Derived Requirements and Rationale from Lowest Tier of Requirements Hierarchy
Figure D.13 - Acceleration Requirement Relationships
Figure D.14 - Requirements Relationships Expressed in Tabular Format (Table)
Figure 16-1: Abstract Syntax for Requirements Stereotypes
Figure 16-2: Requirements Derivation
Figure 16-3: Links between requirements and design
Related slides (backlinks, includes other tutorials)