OMG-OCSMP-MBI300 practice question 8 of 10

How ate use cases and requirements used for requirements analysis in SysML?

Full set: 45 questions
Answer options
A: in a SysML model, either use cases or requirements are modeled, but never both
B: Use cases are a relic from UML and are. strictly speaking, useless in a SysML model
C: Use cases are good for capturing functional requirements. For nonfunctional requirements, the requirement element is needed Correct answer
D: Use cases are the basis for all requirements in a model. Requirements refine the use cases by adding additional information through then properties.
Correct Answer:
C. Use cases are good for capturing functional requirements. For nonfunctional requirements, the requirement element is needed
Explanation

Use cases and requirements serve complementary roles in SysML. Use cases are excellent for capturing functional requirements by describing user-system interactions to achieve a goal. The generic Requirement element is more flexible and is essential for capturing non-functional requirements (e.g., performance, reliability, security, maintainability) and other constraints that do not fit the user-interaction paradigm of a use case. Both are used together for comprehensive requirements analysis.

Why Incorrect

A. Models frequently contain both use cases (for function) and requirements (for non-functional aspects and constraints) to provide a complete specification.
B. Use cases are a fundamental and widely used part of SysML for capturing functional requirements and system context.
D. Requirements can be derived from many sources (stakeholder needs, regulations, etc.), not just use cases. The relationship is not strictly one of refinement.

References

1. Object Management Group, "OMG Systems Modeling Language (OMG SysML®) Version 1.6," December 2019. Compare Section 15.1, "Use Cases," which focuses on "required usages," with Section 16.1, "Requirements," which describes a more general capability or condition.

2. Friedenthal, S., Moore, A., & Steiner, R. (2014). A Practical Guide to SysML: The Systems Modeling Language. Morgan Kaufmann. Chapter 5, "Capturing Requirements," clearly distinguishes the roles of use cases for functional requirements and the requirement stereotype for non-functional requirements.

3. Holt, J., & Perry, S. (2013). SysML for Systems Engineering. The Institution of Engineering and Technology. Chapter 5 discusses using use cases for functional requirements and requirement elements for non-functional requirements.

Scroll to Top