Software Engineering

GROUP 05

Hospital Management System

AWAIZ HUSSAIN 18I-1593-D
MUHAMMAD RASHID 18I-1583-D
MUNTAHIM KHAN 18I-0707-D
FAHEEM ULLAH 18I-0679-D

DEGREE PROGRAM: BS-CS

Section: D
SUBJECT NAME: Software Engineering
DATE OF SUBMISSION: Monday 24/5/2021
SUBMITTED TO: Maam Maryam Abdul Ghafoor

1
Table of Contents

Title of Project: 3
Nature of Project: 3
Scope: 3
Sprint Backlog: 4
Software Architecture 5
Snapshots of Trello Scrum Board 5
Sprint Burn Down Charts 7
Snapshots of Trello Scrum Master Board 8
Scrum Roles: 9
- Product owner: 9
- Scrum Master: 9
- Team: 9

2
TITLE:
HOSPITAL MANAGEMENT SYSTEM

NATURE:
Desktop Application

SCOPE:
The purpose of this project is to create a major “Hospital Management System” based on desktop
application. This is an admin support desktop application in which the admin can login in and
use the application as a receptionist to add patient details, make schedules, make appointments,
make reports, check staff information, check lab resources, check equipment available, check
account details and print receipt.

3
SPRINT 2 BACKLOG:

Story Task Time

As an admin, I want to edit 1. Design interface 1. 4
Patient details so that I can 2. Create DB for patient 2. 2
credentials 3. 5
keep a record of his/her visits. 3. Code to add patient 4. 3
4. Make test cases

As an admin, I want to access 1. Design interface 1. 3

insurance policy so that I can 2. Create DB for storing 2. 2
insurance claim for 3. 4
verify insurance claims of patients 4. 3
patients. 3. Code to verify insurance
claim
4. Make test cases

As a doctor, I want to access 1. Design interface 1. 4

LAB Reports so that I can 2. Create DB for lab 2. 2
reports 3. 4
give patients precise 3. Code for checking lab 4. 3
prescriptions. reports
4. Make test cases

As an admin, I want to check 1. Design interface 1. 4

pharmacy warehouse so that I 2. Create DB for pharmacy 2. 3
can order supplies 3. Code to check for 3. 4
supplies and resources 4. 3
4. Make test cases to verify
only admin has access

4
Software Architecture:
In this Project we have used Layered Architecture (3 tier Architecture)

We have chosen this Architecture Design for following reasons

 Simple Implementation
 Layered approach supports portability
 Provides robustness and stability
 Maintainability
 Flexibility
 Scalability

5
Snapshots of Trello Scrum Board

This is Snapshot-1
Initial Board with All User Stories in Backlog (project Backlog)
Sprint 1 user stories completed (Done)

This is Snapshot-2
Halfway Board of Sprint 2
Here we are testing User Stories 4,5 which are past coding PHASE

6
This is Snapshot-3
Final / End of Sprint 2
Here we have completed all of our User Stories

Sprint Burn Down Chart

7
Snapshot of Trello Scrum Master Board

This is Snapshot-4
The two major problems we faced were both due to distant team
1) Leftover Task: we couldn’t complete the 1 user story on time because we had all been
working on different machines and it became hard for having same database at all-time
our table often clashed and didn’t combine well therefore we were having many
connection issue and it took time to resolve all but it was already late and we had to put
User Story 4 in leftover for next sprint to fix.
2) DB: As already mentioned due to working on different machines we had different
databases but we required 1 DB so that different User Stories could become compatible.

8
SCRUM ROLES:
Product Owner : Awaiz Hussain
Scrum Master : Muntahim Khan
Team : Muhammad Rashid
Faheem Ullah