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.
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.
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.
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.
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.
Patti
3 months agoMel
3 months agoKristofer
3 months agoArdella
4 months agoJaime
4 months agoDominga
4 months agoFelix
4 months agoMerrilee
4 months agoTrinidad
5 months agoKara
5 months agoColby
5 months agoJudy
5 months agoMicaela
5 months agoBritt
5 months agoLorrie
5 months agoEulah
5 months agoCatalina
2 years agoPilar
2 years agoKris
2 years agoCarline
2 years agoCatalina
2 years agoKris
2 years ago