Acharya Prafulla Chandra College

Name: RISHI CHATTERJEE

Roll:
Registration: 1012011400397
Sem: 4th MSc
Department: COMPUTER SCIENCE
Subject: SOFTWARE ENGINEERING
LABORATORY
Subject code: CMSPCOR15P
 INDEX

Sl. Assignment Page

Assignment Name
No. No. No.

1 Assignment 1 Preparation of software requirement. 3

2 Assignment 2 Preparation of Project Management Plan. 5

3 Assignment 3 Drawing of UML diagram and prepare Software Design. 7

4 Assignment 4 Estimate project size using Function Point (FP). 10

Develop Code for assigned application using any

5 Assignment 5 11
platform.

Design Test Plan (both Black Box and White Box

6 Assignment 6 16
approach) for a small component of the proposed project.
 Assignment 1: Preparation of software requirement

1. Introduction
The Hospital Management System (HMS) is designed to manage all aspects of a
hospital's operations such as patient registration, appointment scheduling, doctor
allocation, billing, and medical records management. This system improves the
efficiency and accessibility of hospital services for staff and patients.
2. Functional Requirements
 Patient Registration: Capture and manage patient information like
name, age, gender, contact, and medical history.
 Doctor Management: Add, update, and manage doctors' profiles and
their schedules.
 Appointment Booking: Patients can book appointments with available
doctors.
 Billing System: Automated billing based on services, consultation, and
prescriptions.
 Medical Records Management: Store, retrieve, and update patient
diagnosis, prescriptions, and treatment history.
 User Authentication: Login system for admin, doctor, and patient with
role-specific access.
3. Non-Functional Requirements
 Performance: The system should support at least 50 concurrent users
without noticeable delay.
 Security: Data must be encrypted and accessible only to authorized roles.
 Scalability: Should support future expansion like new departments or
branches.
 Usability: Easy-to-use GUI for both tech-savvy and non-technical users.
 Availability: 24/7 availability with 99.5% uptime.
 Portability: Should be accessible from desktop and mobile browsers.
4. System Models

Context-Level Diagram:
+----------------+
| Patient |
+-------+--------+
|
v
+-------+--------+
| Hospital Mgmt |
| System |
+-------+--------+
^
|
+-------+--------+
| Doctor |
+----------------+

Explanation: Patients and doctors interact with the system for registration,
appointments, and management. The system handles all logic and
communication in between.
 Assignment 2: Preparation of Project Management Plan

1. Project Schedule
The project schedule outlines the major phases of development along with their
tasks and estimated durations. It helps in planning and managing the timeline
effectively.
Duration
Phase Task Description
(Days)

Requirement Requirement Gathering 5

Design UML Diagrams & Design Planning 4

Implementation Code Development 10

Testing Black Box and White Box Testing 3

2
Deployment Deployment & Documentation

2. Gantt Chart
The Gantt Chart visually represents the schedule, showing each task’s start
date, duration, and overlap with other tasks. It helps track progress and
manage deadlines.

3. PERT Chart
The PERT Chart shows task dependencies and sequences. It identifies the
critical path and helps analyze the time required to complete the entire project.
 Assignment 3: Drawing of UML diagram & prepare Software
Design

1. UML Diagrams
The following UML diagrams illustrate the system design for the Hospital
Management System:
a) Use Case Diagram
Depicts the functionalities of the system from a user's perspective. It outlines
how different users (Patient, Doctor, Admin) interact with the system.
b) Class Diagram
Describes the structure of the system by showing classes, their attributes,
methods, and relationships. It helps in understanding data organization and
object-oriented design.
c) Sequence Diagram
Demonstrates the order of interactions between entities over time. It helps
visualize the communication flow, such as how a patient books an appointment
with a doctor via the system.
d) Activity Diagram
Shows the workflow of a specific process within the system. For example, in
the patient discharge activity diagram, it displays steps like consultation,
treatment, billing, and discharge.

2. Software Design
 Architecture: The system follows an MVC (Model-View-Controller)
architecture separating data handling, user interface, and control logic.
 Modularity: Functional modules include Patient Management,
Appointment Scheduling, Billing, and Medical Records.
 Data Flow: Data flows from user interface (e.g., patient booking form) to
the database through backend logic.

These diagrams and explanations define the internal structure, interactions, and
flow of the Hospital Management System in a way that supports efficient
implementation and testing.
 Assignment 4: Estimate project size using Function Point (FP)

1. Identification of Components
 External Inputs (EI): 5 (e.g., Patient Registration, Appointment
Booking, Billing, Login, Add Doctor)
 External Outputs (EO): 4 (e.g., Bill Print, Appointment Slip,
Prescription, Discharge Summary)
 External Inquiries (EQ): 3 (e.g., Search Patient Record, View Doctor
Availability, Check Appointment Status)
 Internal Logical Files (ILF): 3 (e.g., Patient Database, Doctor Database,
Appointment Records)
 External Interface Files (EIF): 2 (e.g., Pharmacy System, Lab Report
System)

2. Complexity Weight Table

 Assignment 5: Develop Code for assigned application using any
platform.

Platform Used: Python (Flask Framework) with SQLite Database

1. Overview of Modules Implemented:
 Patient Registration
 Doctor Management
 Appointment Booking
 Billing System
 User Login System

2. Sample Code Implementation

a) Setup: Database Initialization
b) Patient Registration

c) Doctor Management
d) Appointment Booking
e) Billing System

f) User Login System

 Assignment 6: Design Test Plan (both Black Box and White Box
approach) for a small component of the proposed project.

1. Component Chosen for Testing: Appointment Booking Module

This module handles patient appointment requests, stores them in the database,
and ensures doctor availability. It involves form input, validation, and DB
interaction.

2. Black Box Testing : Black box testing checks if the system behaves correctly
for various inputs without looking at internal code. It validates outputs against
expected results.

Test Case ID Input Expected Output Actual Output Status

Patient ID: 101, Doctor

Appointment Appointment
TC01 ID: 202, Date: 2025-07- Pass
Booked Booked
01

Patient ID: (empty), Error: Missing Error: Missing

TC02 Pass
Doctor ID: 202 Patient ID Patient ID

Error: Doctor not Error: Doctor not

TC03 Invalid Doctor ID Pass
found found

3. White Box Testing : White box testing examines the internal code logic and
flow. It ensures that different code paths produce the correct outcome for given
inputs.
Path ID Code Path Description Condition Expected Outcome Status

Valid patient and doctor

P1 All validations pass Appointment Booked Pass
IDs, valid date

P2 Empty patient ID input patient_id is empty Show error message Pass

Doctor not found in doctor_id does not

P3 Show error message Pass
database match any record