This document presents various UML diagrams for a Hospital Management System including:
1. A domain model showing the main entities and their relationships
2. Sequence diagrams showing the processes of a patient getting an appointment, having their vitals checked, and consulting a doctor
3. Collaboration diagrams depicting the processes of taking an appointment and checking vitals, and consulting a doctor
4. Operation contracts specifying operations for taking an appointment, checking vitals, and consulting a doctor
5. A class diagram modeling the design of the Hospital Management System
6. State charts showing the states and transitions for taking an appointment, checking vitals, and consulting a doctor
7. An entity relationship diagram as the data model for the Hospital
This document presents various UML diagrams for a Hospital Management System including:
1. A domain model showing the main entities and their relationships
2. Sequence diagrams showing the processes of a patient getting an appointment, having their vitals checked, and consulting a doctor
3. Collaboration diagrams depicting the processes of taking an appointment and checking vitals, and consulting a doctor
4. Operation contracts specifying operations for taking an appointment, checking vitals, and consulting a doctor
5. A class diagram modeling the design of the Hospital Management System
6. State charts showing the states and transitions for taking an appointment, checking vitals, and consulting a doctor
7. An entity relationship diagram as the data model for the Hospital
This document presents various UML diagrams for a Hospital Management System including:
1. A domain model showing the main entities and their relationships
2. Sequence diagrams showing the processes of a patient getting an appointment, having their vitals checked, and consulting a doctor
3. Collaboration diagrams depicting the processes of taking an appointment and checking vitals, and consulting a doctor
4. Operation contracts specifying operations for taking an appointment, checking vitals, and consulting a doctor
5. A class diagram modeling the design of the Hospital Management System
6. State charts showing the states and transitions for taking an appointment, checking vitals, and consulting a doctor
7. An entity relationship diagram as the data model for the Hospital
This document presents various UML diagrams for a Hospital Management System including:
1. A domain model showing the main entities and their relationships
2. Sequence diagrams showing the processes of a patient getting an appointment, having their vitals checked, and consulting a doctor
3. Collaboration diagrams depicting the processes of taking an appointment and checking vitals, and consulting a doctor
4. Operation contracts specifying operations for taking an appointment, checking vitals, and consulting a doctor
5. A class diagram modeling the design of the Hospital Management System
6. State charts showing the states and transitions for taking an appointment, checking vitals, and consulting a doctor
7. An entity relationship diagram as the data model for the Hospital
Download as PPTX, PDF, TXT or read online from Scribd
Download as pptx, pdf, or txt
You are on page 1of 12
Hospital Management
System
By: Muhammad Taha Ali
2oo11598-004 BSSE 4th (A)
To: Ma’am Reema
Domain Model of HMS
20011598-004 Hospital Management System 2
Sequence Diagram: Patient Getting Appointment
20011598-004 Hospital Management System 3
Sequence Diagram: Patients Go For Vitals
20011598-004 Hospital Management System 4
Sequence Diagram: Patient Consult Doctor & Doctor treat Patient
20011598-004 Hospital Management System 5
Collaboration Diagram: Taking Appointment and Checking Vitals
20011598-004 Hospital Management System 6
Collaboration Diagram: Consult Doctor
20011598-004 Hospital Management System 7
Operation Contracts: Operation takeappointment()
Responsibilities Patients take appointment from receptionist
Cross Reference Use case: UC_take_appointment
Pre-condition Patient must have ID card. Patients need an appointment
Operation consultdoctor() Post-condition 1. Appointment confirmed (Instance Creation) 2. Add patient details at database (modification) Responsibilities Doctor treat patient 3. Patient go to nursing staff for vitals (Instance formed) Cross Reference Use case: UC_consult_doctor Pre-condition Vitals of patients will be checked. Operation checkvitals() Post-condition 1. Doctor treat patient (Instance Creation) Responsibilities Nursing staff check vitals of patients 2. Doctor prescribe medicine and enter details on database (modification) Cross Reference Use case: UC_check_vitals 3. Admit serious patient (Instance formed) Pre-condition Patient must have appointment.