I would like to know what's the best way to model a situation when both initiator and a receiver actors are involved in a Use case.
- initiator sends a request for contact exchange (the inititator has a contact on pending state)
- receiver approves the contact exchange (the receiver has a contact on active state)
- initiator receives a confirmation (the inititator has contact on active state)
My ideas would be:
- state diagram for "Contact" object - but that will only reflect the changes only for one Actor.
- BPMN diagram to reflect the process flow for both Actors
Is this enough or there is another diagram I can use?
Also, these diagrams focus on the main scenario but the alternatives how should be described in a diagram?
Thanks!
Hi Madalinaro,
Looks to me like you have a process with at least 2 use cases.
Use case #1: Initiator "Request Contact Exchange"
Use case #2: Receiver "Approve Contact Exchange" with the initiator getting a confirmation.
expect each use case has alternate scenarios, etc.
So your deliverables are:
1. The two use cases with alternate scenarios
2. business process diagram - bpmn or activity diagram
3. Statechart diagram for the contact class
4. You could even specify the business domain model using a class diagram to show the "contact" class and related classes.
It'd be overkill for your example but I expect you've simplified it hugely.
Kimbo
Thank you, this clarifies a lot!
It's true, the flow I described here is hugely simplified; in reality there are more steps plus alternative scenarios
brought to you by enabling practitioners & organizations to achieve their goals using: