Author Topic: 'asynchronous' events in use case  (Read 2148 times)


  • EA User
  • **
  • Posts: 20
  • Karma: +0/-0
    • View Profile
'asynchronous' events in use case
« on: February 09, 2011, 10:39:09 am »
Just wondering how people model the situation where the user can perform an action during a step being performed by the system.

For example:
1. User asks system to initiate (ongoing) process A
2. System starts performing process A (which keeps going until explicitly stopped)
3. User asks system to stop process A

During step 2 the user can adjust some parameter of process A, that the system must take into account.

I had something like (simplified):

Alternate Flow : Adjust Inputs
Prior to step 3 of the Main Flow, the user can adjust input values:
1. user changes value XYZ
2. return to main flow

But it's not really an 'alternate' flow for step 3, or any other step.

I guess there are 2 questions here: how to word an ongoing process in a use case; and how to model the situation described above.

« Last Edit: February 09, 2011, 10:40:11 am by vjr »


  • EA User
  • **
  • Posts: 634
  • Karma: +16/-0
  • UML/EA Principal Consultant / Trainer
    • View Profile
Re: 'asynchronous' events in use case
« Reply #1 on: February 10, 2011, 12:37:35 am »
I would use an activity diagram with an interruptable region surrounding the steps where the user coluld adjust the parameter.

Capture the request to adjust as an "Accept Event", connection to the setting action with an "Interupt Flow", then resume the flow just before the interrupt region.

Alternatively, the behaviour could be modelled using a State Machine Diagram capturing the events as triggers on transitions


follow me on Twitter



  • EA User
  • **
  • Posts: 20
  • Karma: +0/-0
    • View Profile
Re: 'asynchronous' events in use case
« Reply #2 on: February 10, 2011, 06:26:39 am »
Thanks. I guess the point is that not everything can be put into use case text/prose. I was trying to massage EA into generating the correct activity diagram for me from the structured scenario. One thing you can't do is to have one activity join back to a decision point (rather than an activity) which you can do manually.
« Last Edit: February 10, 2011, 06:26:52 am by vjr »


  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: 'asynchronous' events in use case
« Reply #3 on: February 13, 2011, 09:22:19 pm »
You have three use cases.
Start Process A
Tell Process A
Stop Process A

Please continue.
"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.