Thursday, September 27, 2012

Medical Clinic System - UseCase Diagram

UML Use Case diagram for Medical Clinic System is shown below. The various participants of the same are detailed below:-

Actors:- Receptionist, Patient, Doctor

The corresponding use cases for these actors are:-
  • Receptionist: Provide Information, Fill Time Sheet, Give Appointment, Cancel Appointment, Collect Fees
  • Patient: Take Appointment, Cancel Appointment, Show To Doctor, Pay Fees
  • Doctor: Check Patient, Give Prescription
Here we have some dependencies also like Give Appointment and Take Appointment <<extend>> Cancel Appointment as appointment given by receptionist and taken by patient both can be cancelled. Also if one goes to doctor and gets a check up then, he has to pay the fees. Hence, Show to Doctor <<includes>> Pay Fees.

The Use Case UML diagram for Medical Clinic System is shown below:-


 Related Articles
 Use Case Diagram Examples

Retail Banking System - UseCase Diagram

UML Use Case diagram for Retail Banking System is shown below. The various participants of the same are detailed below:-

Actors:- Customer, Employees

The corresponding use cases for these actors are:-

  • Customer: General Enquiry, Loan Enquiry, Open Acc. Enquiry, D-Mat Enquiry, Open Acc., Close Acc., Borrow Loan, Deposit Money, Withdraw Money, Pay EMI, Apply For Online Banking Acc., Open D-Mat Acc.
  • Employees: Open Acc., Close Acc., Open D-Mat Acc., Provide Information, Collect Money, Open Online Banking Acc.

Here we have some dependencies also like General Enquiry <<extend>> Loan Enquiry, D-Mat Acc. Enquiry, Open Acc. Enquiry. If one borrows loan from the bank then, he has to pay EMI's to return the loan. Hence, Borrow Loan <<includes>> Pay EMI.

The Use Case UML diagram for Retail Banking System is shown below:-


 Related Articles
 Use Case Diagram Examples

Wednesday, September 26, 2012

Airport Security And Check-In System-UseCase Diagram

UML Use Case diagram for Airport Security And Check-In System is shown below. The various participants of the same are detailed below:-

Actors:- Traveller, Security Persons, Boarding Pass Counter

The corresponding use cases for these actors are:-
  • Traveller: Go to Security Check, Go To Boarding Pass Counter, Collect Passes, Traveller Check-In
  • Security Persons: Security Man Checks Traveller, Baggage Security Check, Baggage Check-In
  • Boarding Pass Counter: Check Ticket, Distribute Passes
Here we have some dependencies also like Collect Passes <<includes>> Traveller Check-In. Also Check Ticket <<include>> Distribute Passes.

The Use Case UML diagram for Airport Security And Check-In System is shown below:-


 Related Articles
 Use Case Diagram Examples

Online Shopping System- Usecase Diagram

UML Use Case diagram for Online Shopping System is shown below. The various participants of the same are detailed below:-

Actors:- Registered Customer, Guest, Administrator, Paypal

The corresponding use cases for these actors are:-
  • Registered Customer: Login, Add Item To The Cart, Delete Item From The Cart, View Items, Make Payment
  • Guest: View Items, Get Registered, Guest Page
  • Administrator: Maintain Stocks, Get Payments, Add Items, Delete Items, Modify Items, Ship Sold Items, Make Delivery
  • Paypal: Do_Authentication, Make Finalized Payment, Tax
Here we have some dependencies also like Add Items To The Cart <<include>> Make Payment, Maintain Stocks <<include>> Add Items, Delete Items and Modify Items. Also,Get Payments <<include>> Make Delivery, Ship Sold Items and Do_Authentication <<include>> Make Finalized Payment, Tax .

Also Add Item To The Cart <<extends>> Delete Items From The Cart.

The Use Case UML diagram for Online Shopping System is shown below:-


 Related Articles
 Use Case Diagram Examples

Tuesday, September 25, 2012

Library Management System - UseCase Diagram

UML Use Case diagram for Library Management System is shown below. The various participants of the same are detailed below:-

Actors:- Member, Librarian

The corresponding use cases for these actors are:-
  • Member: Inquiry For Membership, Search Book, Book Issue, Book Return, Pay Fine

  • Librarian: Search Book, Issue Membership Card, Cancel Membership, Issue Book, Return Book, Charge Fine In Case of Late Return, Maintain the Book Records, Add Books, Remove Books, Add Members, Remove Members, Update Member Details
 Here we have some dependencies also like Request For Book Return <<extends>> Pay Fine. Also Maintain Book Records <<includes>> Add Book, Remove Book and Update Book. Again Return Book <<extends>> Charge Fine in case of late return.

The Use Case UML diagram for Library Management System is shown below:-


 Related Articles
 Use Case Diagram Examples

Monday, September 24, 2012

Airline Ticket Reservation-Use Case Diagram

Use Case Diagram for Airline Ticket Reservation System is shown below. The various participants of the same are detailed below:

Actors: Traveller, Travel Agent, Airline Counter Incharge

The corresponding usecases  for these actors are:

  • Traveller: Book Ticket Online, Cancel Booking Online, Book via Agent, Cancel Ticket via Agent, Book At Counter, Cancel Ticket At Counter, Online Inquiry, Fill Details, Cancel Ticket, Book Ticket, Make Payment, Update Database, Receive Money On Cancellation

  • Travel Agent: Book via Agent, Cancel Ticket via Agent, Online Inquiry, Fill Details, Book Ticket, Make Payment, Cancel Ticket, Update Database, Receive Money On Cancellation

  • Travel Counter Incharge: Book At Counter, Cancel Ticket At Counter, Online Inquiry, Fill Details, Book Ticket, Make Payment, Cancel Ticket, Update Database, Receive Money On Cancellation

Here we have some dependencies like Book Ticket Online, Book Via Agent and Book at Counter all three have <<include>> relationship with Online inquiry and Fill Details. In all these cases one needs to do online inquiry and then filling details. Fill Details further has a dependency <<include>> with Book ticket that again depends on Make Payment. Until and unless payment is made ticket can't be booked.

Again, Cancel Booking Online, Cancel Ticket at Counter and Cancel via Agent all three has a <<include>> dependency with Cancel Ticket and which further <<includes>> Receive Money On Cancellation, and updating database. Make Payment also <<includes>> updating database.

The Usecase UML Diagram for Airline Ticket Reservation is shown below:


 Related Articles
 Use Case Diagram Examples