New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

OMG-OCSMP-MBA400 Exam - Topic 2 Question 7 Discussion

Actual exam question for OMG's OMG-OCSMP-MBA400 exam
Question #: 7
Topic #: 2
[All OMG-OCSMP-MBA400 Questions]

Choose the correct answer

In a scenario-based development approach, which SysML diagram type could best be used to describe the scenarios?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Patti
3 months ago
I thought requirements diagrams were for something else entirely!
upvoted 0 times
...
Mel
3 months ago
State diagrams are too rigid for this, right?
upvoted 0 times
...
Kristofer
3 months ago
Wait, are we sure it's not an activity diagram?
upvoted 0 times
...
Ardella
4 months ago
Totally agree, use case diagrams are perfect for scenarios!
upvoted 0 times
...
Jaime
4 months ago
I think a use case diagram is the way to go here.
upvoted 0 times
...
Dominga
4 months ago
I thought requirements diagrams were more about capturing needs, so I don't think that's the answer, but I could be wrong.
upvoted 0 times
...
Felix
4 months ago
I feel like state diagrams could work too, but they seem more about states rather than scenarios.
upvoted 0 times
...
Merrilee
4 months ago
I remember practicing with activity diagrams for workflows, but I'm not confident if that's the right fit for scenarios.
upvoted 0 times
...
Trinidad
5 months ago
I think the use case diagram might be the best choice since it focuses on interactions and scenarios, but I'm not entirely sure.
upvoted 0 times
...
Kara
5 months ago
Based on what I know about SysML, I'd say the activity diagram is the way to go. It's designed to model the dynamic behavior of a system, which is perfect for describing scenarios.
upvoted 0 times
...
Colby
5 months ago
The state diagram could work too, since it can model the different states the system can be in during the scenarios. I'll have to think this through a bit more.
upvoted 0 times
...
Judy
5 months ago
I think the activity diagram would be the best choice here to describe the scenarios. It can show the flow of actions and events in the system.
upvoted 0 times
...
Micaela
5 months ago
Hmm, I'm not sure about this one. I was thinking the use case diagram might be a good option to capture the different scenarios, but I'm not totally confident.
upvoted 0 times
...
Britt
5 months ago
Option B seems like the simplest solution - create one new work queue and split the tasks by type. That way we don't have to manage multiple queues or groups.
upvoted 0 times
...
Lorrie
5 months ago
Alright, time to put my pharmacy math skills to the test. Let's do this!
upvoted 0 times
...
Eulah
5 months ago
Okay, I've got it! The authentication method being described is multi-factor, since it uses both smart cards and usernames/passwords. That's the only option that fits the details provided.
upvoted 0 times
...
Catalina
2 years ago
Ok, I'm convinced. Use case it is. Thanks everyone!
upvoted 0 times
...
Pilar
2 years ago
I lean towards User3's choice. Use case diagrams capture scenarios well.
upvoted 0 times
...
Kris
2 years ago
Use case diagrams do make sense for scenarios. But aren't activity diagrams more detailed?
upvoted 0 times
...
Carline
2 years ago
I disagree. I think it's C) use case diagram, because it focuses on interactions.
upvoted 0 times
...
Catalina
2 years ago
Yes, especially with SysML diagrams! I think it might be B) activity diagram.
upvoted 0 times
...
Kris
2 years ago
This question is a bit tricky.
upvoted 0 times
...

Save Cancel