Author Topic: How we draw a usecase diagram from a case study?  (Read 6558 times)


  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: How we draw a usecase diagram from a case study?
« Reply #45 on: April 01, 2020, 11:26:50 am »
Main pointers to be remembered while drawing a use case diagram are:
1. Have one round of overview on the case study and come up with the list of actors who will have interaction with the system.
2. For these actors, system should have use cases, and use cases are always "actions" that actors interact with the system.
3. So, taking point-2 as reference, break the case study into smaller chunks and try to analyze every point. Identify if they have interaction with the system or not.
4. If they have, notate them in verbal forms (as an action, Ex: Makes Payment, Generates Bill). These can be termed as 'use cases.'
5. Map them with the corresponding actors.
6. Try to identify include, extend and generalization relationships, if possible as they add more information to the diagram.
      a. include : When your child use case cannot exist without the parent use case, they have an <include> relationship established.
      b. extends : When your child use case can exist with/without the parent use case existence, they have <extends> relationship
      c. Generalization : When the child use case exhibits the properties of a parent use case, then they can be exhibited by
                         generalization relation. It implies for actors also. Ex: When financial transaction is a parent use case, Pay by Credit
                         Card, Pay by Cash will fall as child use cases. Pay by Credit Card, Pay by Cash are type of financial transaction.

These are the major concerns to be considered while deriving a UCD from a case study. Hope it helps !!!!


  • Global Moderator
  • Newbie
  • *****
  • Posts: 14
Re: How we draw a usecase diagram from a case study?
« Reply #46 on: April 11, 2020, 02:19:54 pm »
identify the Actors (role of users) of the system.
For each category of users, identify all roles played by the users relevant to the system.
Identify what are the users required the system to be performed to achieve these goals.
Create use cases for every goal.
Structure the use cases.
Prioritize, review, estimate and validate the users.