1. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FRIEDENTHAL
A Practical Guide to SysML
The Systems Modeling Language
Third edition
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

2. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
CH13 - MODELING TEXT-BASED
REQUIREMENTS AND THEIR
RELATIONSHIP TO DESIGN
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

3. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.1
Generic example of a requirement diagram.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

4. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.2
Example of a requirement as depicted in SysML.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

5. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.3
Example of direct notation depicting a satisfy relationship.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

6. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.4
Example of compartment notation depicting a satisfy relationship.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

7. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.5
Example of callout notation depicting a satisfy relationship.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

8. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.6
Example of rationale as depicted on any SysML diagram.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

9. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.7
Example of requirements table.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

10. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.8
Example of table following the deriveReqt relationship.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

11. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.9
Example of tabular view of requirements as matrices tracing satisfy and derive requirement relationships, respectively.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

12. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.10
Example of a package structure for organizing requirements.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

13. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.11
Two equivalent examples of requirements contained in a package.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

14. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.12
Example of requirements containment hierarchy.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

15. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.13
Example of requirements containment in a tool browser.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

16. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.14
Example of «deriveReqt» relationship, with rationale attached.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

17. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.15
Example of requirement satisfy relationship and associated callout notation.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

18. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.16
Example of satisfy relationship using compartment notation.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

19. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.17
Example of verify relationship.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

20. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.18
Example of a test case interaction depicted as a sequence diagram.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

21. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE cont’d
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

22. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.19
Example of refine relationship applied to requirement.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

23. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.20
Example of trace relationship linking a requirement to an element representing an external document.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.

24. Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
FIGURE 13.21
Example of a requirement copy relationship.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.