Author Topic: Usage of Use cases  (Read 1118 times)

Francis

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Usage of Use cases
« on: March 02, 2004, 07:57:36 am »
Hi All
wonder can u help. I'm just starting out on the UML pathway so bear with me. I have to design a component that will notify different actors (User, Authoriser, Owner) of certain tasks as to the status of the task at different stages in the lifestyle of the task. Do I create a new Use Case for every notification i.e. NotifyUser, NotifyOwner etc or can I use the same one in every instance. How would the 'extend' be of use here
Tks
Frank

fluxtah

  • EA User
  • **
  • Posts: 144
  • Karma: +0/-0
    • View Profile
Re: Usage of Use cases
« Reply #1 on: March 02, 2004, 09:15:45 am »
You could possibly use a use case here called 'Receive Notification', Just exactly how they would receive notification could be described in the Use Case Flows.

It would be best not to call your Actors User or Owner. It would be good to ask exactly what User, Authoriser and Owner will do with the system, why does the User, Owner and Authoriser Use the System?

They could be of Actor type 'Notification Receiver' but I am not to sure :]

If you can give some more information about the purpose of the system and what it will do for the Users, it would be easier to find Actors and Use Case.

Regards

- Fluxtah

Francis

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Usage of Use cases
« Reply #2 on: March 02, 2004, 09:29:28 am »
Fluxtah
tks for the reply, basically the following events will take place. As you can see the reciever is three different people

START
1. Owner creates main task including # of subtasks
2. Owner assigns Subtask1 to user1
3. System notifies user1 of their task
4. Owner assigns Subtask2  to user2
5. System notifies user2 of their task
6. User1 completes task
7. System notifies Owner, Authoriser & user1 of task1 completion
8. User2 completes task
9. System notifies Owner and Authoriser of task2 completion
10. System checks if all subtasks completed
11. If so, system notifies Owner
12. Owner makes overall task as completed
13. System notifies Authoriser
END



Frank

mchiuminatto

  • EA User
  • **
  • Posts: 113
  • Karma: +0/-0
    • View Profile
Re: Usage of Use cases
« Reply #3 on: March 02, 2004, 12:50:05 pm »
As first iteration I see:

I.  actors & goals.

Actor 1: Owner : the one who makes the work plan
Goals: - need to input tasks in a work plan
          - need to be notified of any changes in te task status
           - need to approve a task as completed.

Actor 2: User: the one who performs the work
Goals     - need to be notified when he is assigned to a task
             - need to be able to update the task status he owns.

Actor 3: Authoriser (it seems he is just a vouyerist ;)
Goals   :need to know when a task es comlpeted.


II. Use Cases.

1. Create a work plan
Primary Actor: Owner
Secondary actor(s): Authoriser, User (they receive the notifications)

Basic path: create a work plan steps
Alternate path: tas completion approval.

Extension point: Notify

2. Status Update.
Primary actor: User
Secondary actor(s) Owner, Authoriser (they receive notification)
Extension point: Notify

3. Notification.
Extends: Status Update, Create Work Plan
Extension point: Notify
Condition: status reach an specific condition.


Thos is a first iteration, iso is a tentative approach but you can use it as start  point,

Regards.
Regards.

Marcello