OMG Exam OMG-OCSMP-MBI300 Topic 1 Question 48 Discussion

Actual exam question for OMG's OMG-OCSMP-MBI300 exam

Question #: 48
Topic #: 1

Choose the correct answer

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

Ain a SysML model, either use cases or requirements are modeled, but never both

BUse cases are a relic from UML and are. strictly speaking, useless in a SysML model

CUse cases are good for capturing functional requirements. For nonfunctional requirements, the requirement element is needed

DUse cases are the basis for all requirements in a model. Requirements refine the use cases by adding additional information through then properties.

Show Suggested Answer

Suggested Answer: A

by Twila at Jun 18, 2024, 12:08 PM

Limited Time Offer

25%

Off

Get Premium OMG-OCSMP-MBI300 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Micah

1 months ago

Hmm, I think I'll go with C. Keeps the functional and non-functional separate, like sorting socks and underwear. Wait, do they even wear socks in SysML land?

upvoted 0 times

...

Janessa

1 months ago

B? Really? Use cases are so 2000s. This is SysML, man. We're living in the future now. Let's just use requirements and be done with it.

upvoted 0 times

Dottie

9 days ago

I agree, use cases can still be useful for capturing functional requirements, but requirements are definitely essential for a thorough analysis in SysML.

upvoted 0 times

...

Rashad

12 days ago

D) Use cases are the basis for all requirements in a model. Requirements refine the use cases by adding additional information through then properties.

upvoted 0 times

...

Melissia

13 days ago

C) Use cases are good for capturing functional requirements. For nonfunctional requirements, the requirement element is needed

upvoted 0 times

...

Jesusa

2 months ago

D is clearly the correct answer. Use cases are the foundation, and requirements add more details. Nice and simple, just the way I like it.

upvoted 0 times

Elina

10 days ago

Absolutely, D is the way to go. Use cases are essential for understanding the system's behavior.

upvoted 0 times

...

Corazon

14 days ago

Yes, use cases set the stage and requirements fill in the specifics. D is the way to go.

upvoted 0 times

...

Ashton

1 months ago

I agree, D is definitely the correct answer. Use cases provide the initial structure.

upvoted 0 times

...

Gabriele

2 months ago

Option C seems logical. Use cases are good for functional requirements, while the requirement element is needed for non-functional ones. Keeps things organized, you know?

upvoted 0 times