Monday, January 30, 2012

Hospital Management System Use Case Diagram Example

For the Hospital Management System, a general example is shown below. This module can be massive and many more sub modules can be added as per requirement.

The Actors and their use cases are identified as:-
  • Receptionist--Interact with Visitors, Give appointments to Medical Representatives, Revert to Phone Queries, Handles Patient Registration.
  • Doctors--Give prescription to Patient, Do Operation, Review Patients health.
  • Nurse--Give Medicine to Patient, Coordinate with Doctors in Operation, Report to doctors, Monitors Patients health.
  • Staff--Do Cleaning, Dispose Wastes, Maintain Beds and Rooms.
  • Patient--Interact with Doctor, Follow Doctor Instructions, Pay Bills.
  • Billing Section--Patient Billing, Discharge Billing, Give salaries to Nurse,Staff and Doctors, Maintain Tax Records
Here for the Billing Section we have considered Patient Billing and Discharge billing as separate, as the Patient might not be admitted and is charged for only counseling. But if the patient was admitted then the discharge billing is also added to its usecase, that's why we have an <<extend>> relationship their. The use case diagram for hospital management system is shown below:-

 Related Articles
 Use Case Diagram Examples

Sunday, January 29, 2012

Use Case for ATM Machine Example

For an ATM Machine, we consider a general use case. Here we have the actors as Bank Customer, Maintenance Person and the Cashier. The Bank Customer is allowed certain operations like withdraw money, change pin, transfer funds, etc. The Maintenance Person checks and repairs machine. And the Cashier deposits the cash in the ATM machine.

Have a look at the include and exclude stereotype dependency in the below use case diagram for ATM machine.
The include dependency is required as the customer needs to be validated before he is allowed any operation. The exclude dependency signifies that the help is an add on and not a compulsion for any of the operations above.

 Related Articles
Use Case Diagram Examples

Use Case Diagram Examples

The Use Case Examples are linked below:-


 Related Articles
Use Case Diagram

    Friday, January 13, 2012

    Use Case Diagram

    Behaviour diagrams------>Use case diagram
    Functional View------>Use case diagram


    Components of a Use Case Diagram
    System: Sets the boundary of the system
    Actor: A role played by a person, system, or device
    Use Case: Identifies a key feature of the system. Each Use Case is named using a verb phrase that expresses a goal the system must accomplish, for example, deposit money, withdraw money, and adjust account.
    Association: Identifies an interaction between actors and Use Cases.
    Dependency: Identifies a communication relationship between two Use Cases.
    Generalization: Defines a relationship between two actors or two Use Cases where one Use Case inherits and adds to or overrides the properties of the other.


    Dependency types:
    <<include>>,<<extend>>
    The <<extend>> dependency stereotype says that one Use Case might need help from another Use Case. In contrast, the <<include>> dependency stereotype says that one Use Case will always call the other Use Case.
    The other contrast between the two dependency stereotypes is the direction of the dependency arrow. The <<include>> dependency arrow points from the main Use Case (the one currently executing) to the one that it needs help from. The <<extend>> dependency arrow points from the extension Use Case (the one providing the extra help) to the main Use Case that it is helping.

    The main point is that an include relationship is not optional, while an extend relationship is optional.

    generalization is basically inheritance relationship ("is a" relationship)


    Here, if the student attends college, then he has to get enrolled in the college. It is a compulsion and not optional. So that's an include dependency..
    If the student attends Engineering college, then he may or may not go to the canteen, so that's optional. Therefore it is an extend dependency.
    Finally, the engineering college "is a" college, so it's a pure form of inheritance, that's why its a generalization.

     Related Articles
    Use Case Diagram Examples