System Analysis and Design for Desklib Online Library

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Use Case Diagram:..........................................................................................................................2
Use Case Description:......................................................................................................................2
Class Diagram:.................................................................................................................................6
Sequence Diagram:..........................................................................................................................7
Activity Diagram:............................................................................................................................9
Bibliography:.................................................................................................................................10

2SYSTEM ANALYSIS AND DESIGN
Use Case Diagram:
Figure 1: Use Case Diagram
(Source: Created by Author)
Use Case Description:
Use Case Name Book Appointment
Use Case ID UC_ADMIN_PATIENT_01

3SYSTEM ANALYSIS AND DESIGN
Actor(s) Patient and Admin
Stakeholders Organization and patient
Precondition The patient must be registered into the system
Post Condition The selected dates must be available for appointment
Activities The patients sends request for booking the appointment
System check user validity
Check if dates available
If dates available then appointment is booked
Exception The patient is not present at the time of appointment
Use Case Name Search Patient Record
Use Case ID UC_ADMIN _01
Actor(s) Admin
Stakeholders Organization and Administrator
Precondition The patient must be registered into the system
Post Condition The patient must have booked at least a single appointment
Activities The administrator enters the patient id or name
The system checks the patient with the inputted keyword is present in the
system or not
The system then fetches all the data of the patient from the database and
shows to the admin through a UI
Exception The patient name is changed and admin is not notified of this fact