Project Report

Project Report
Hospital Management System (Windows Form Application)
Submitted by

Muhammad Mudassir
BSTT-LD_17_62

2017-2021

Supervised by
Sir Muzammil Mahboob

DEPARTMENT OF INFORMATION TECHNOLOGY

BAHAUDDIN ZAKARIYA UNIVERSITY MULTAN SUB
CAMPUS LODHRAN

1
Project Report

FINAL APPROVAL

2
Project Report

It is certified that the project submitted by Muhammad Mudassir Roll No. BSTT-17-62
session (2017-2021) is up to standard.

Supervisor:

______________________

Sir Muzammil Mehboob Shb

3
Project Report

Lecturer

Dept. of Information Technology

Bahauddin Zakariya University, Multan Sub Campus Lodhran.

External Examiner:

______________________

Head of the Department

_____________________________

Dept. of Information Technology BZU Sub Campus Lodhran

Bahauddin Zakariya University, Multan

Dedication
To our parents, teachers and all of the people who prayed for us. A special
feeling of gratitude to my loving parents; I also dedicate this dissertation to my
friends and family who have supported me throughout the process.

4
Project Report

Declaration

I hereby declare that this Project Report titled “Hospital Management System” submitted to
the Department of Information Technology BZU Sub Campus Lodhran is a record of
Original work done by me under the guidance of my supervisor Sir Muzammil Mahboob,
This Project Report is not submitted to any other university or institution for the award of any
degree, diploma or published any time before. I also declare that there have no copy of the
source code in the project.

…………………………………..
Muhammad Mudassir

Submission Date:

5
Project Report

ACKNOWLEDGMENTS:
With the blessings of Almighty Allah and prayers of our parents I have made this attempt to achieve
the goal that was set for me to complete the MIT degree. Although the project was complex and
complicated, I put my maximum effort to fulfill the goal.

I deeply indebted to our teachers and special gratitude to our final year project supervisor,

Muzammil Mehboob Shb whose guidance, suggestion and encouragement remained a continuous
source of inspiration for us throughout the entire course of project.

I wish to seize this opportunity to thanks all our friends, who very patiently guided us through all the
stages of the project with regard to system support. Finally a special thanks to our parents, friends and
our family for their prayers, unending support and encouragement during the course of a long and
tedious struggle to accomplish the work in time.

___________________________________________________________________

BSIT Session (2017-21)

Roll# BSTT-LD_17_62

Name: Muhammad Mudassir

6
Project Report

Project Name:

Hospital Management system (Windows Form

Application)

Organization:

Public

Undertaken By:

Muhammad Mudassir

Internal Supervisor:

Sir Muzammil Mehboob

Starting Month:

Jan 2022

Completion Month:

March 2022

Development Tool Used:

MySQL Database

Visual Studio 2022

Operating System

Window 10

Machine Used:

INTEL(R) CORE(TM) I5-3340M CPU @ 2.70GHZ 2.70 GH

7
Project Report

Contents
Project Report........................................................................................................................................
Declaration.............................................................................................................................................
Chapter # 01: INTRODUCTION....................................................................................................12
1.1 Introduction:............................................................................................................................12
1.2 Problem Introduction................................................................................................................12
1.3 Scope of the Project...................................................................................................................13
1.4 Objective....................................................................................................................................14
1.5 Goals..........................................................................................................................................14
Chapter 2..............................................................................................................................................
System Requirement Analysis..............................................................................................................
2.1 System Analysis:.......................................................................................................................16
2.2 Analysis of the Exiting System:...................................................................................................16
2.3 Understanding the System:.......................................................................................................16
2.4 Proposed System:......................................................................................................................16
2.5 Data Analysis:............................................................................................................................17
2.6 Feasibility Study.........................................................................................................................17
2.6.1 Technical Feasibility...........................................................................................................17
2.6.2 Economic Feasibility...........................................................................................................18
2.6.3 Operational Feasibility.......................................................................................................18
2.7 The Proposed System................................................................................................................18
2.7.1 Advantages of Computerized System................................................................................18
2.7.2 Objectives of the Proposed System...................................................................................19
Chapter 3..............................................................................................................................................
System Design3.1 Introduction to System Design..........................................................................21
3.2 Visual Representation using UML:.............................................................................................21
3.3 Use Case Diagrams.....................................................................................................................22
3.3.1 Use case Relationships.......................................................................................................22
3.3.2 Elements of Use Case Diagram..........................................................................................22
Use Case Diagram of Admin/User....................................................................................................24

8
Project Report

Use Case Doctor Patient..................................................................................................................25

3.4 Sequence Diagram..........................................................................................................................
3.5 Activity Diagram.......................................................................................................................
3.6 Component Diagram......................................................................................................................
3.7 Class Diagram.................................................................................................................................
3.8 Data Base Introduction:..................................................................................................................
3.8.1 Logical Database Design:...................................................................................................32
3.8.2 Physical Database Design:.................................................................................................32
3.9 Database:.......................................................................................................................................
First Normal Form............................................................................................................................34
Second Normal Form.......................................................................................................................34
Third Normal Form:.........................................................................................................................34
Database Design Approaches:.........................................................................................................35
Top down approach.........................................................................................................................35
Bottom up approach........................................................................................................................35
Mixed approach...............................................................................................................................35
Description of Database Tables.......................................................................................................37
Chapter 4:.............................................................................................................................................
System Implementation & Development.............................................................................................
4.1 Introduction to System Development......................................................................................48
4.1.1 Testing of Software.................................................................................................................48
4.2 Introduction to System Development........................................................................................49
4.3 Software Development & Implementation................................................................................49
4.3.1 Methods of Implementation..............................................................................................49
In this method individual component of the new computerized system are implemented one by
one.4.4 Performance Testing:..........................................................................................................50
4.5 Language Selection....................................................................................................................51
Chapter 5..............................................................................................................................................
User Guide...........................................................................................................................................
START OF THE PROJECT...................................................................................................................54
Register Your Self.............................................................................................................................55
Login................................................................................................................................................56
Test Cases Scenarios........................................................................................................................57
Main Menu......................................................................................................................................58

9
Project Report

Department Information.................................................................................................................59
Room Information...........................................................................................................................60
Doctor Information..........................................................................................................................61
Register New Patient.......................................................................................................................62
Register Checkup.............................................................................................................................63
Search Patient..................................................................................................................................64
Search Doctor..................................................................................................................................65
Chapter 6 Conclusion............................................................................................................................
6.1 Conclusion.................................................................................................................................67
6.2Future work................................................................................................................................67
References...........................................................................................................................................

10
Project Report

Chapter 1
Introduction

11
Project Report

Chapter # 01: INTRODUCTION

1.1 Introduction:

The project Hospital Management system includes registration of patients, storing their
details into the system, and also computerized billing in the pharmacy, and labs. The software
has the facility to give a unique id for every patient and stores the details of every patient and
the staff automatically. It includes a search facility to know the current status of each room.
User can search availability of a doctor and the details of a patient using the id.

The Hospital Management System can be entered using a username and password. It is
accessible either by an administrator or receptionist. Only they can add data into the database.
The data can be retrieved easily. The interface is very user-friendly. The data are well
protected for personal use and makes the data processing very fast.

Hospital Management System is powerful, flexible, and easy to use and is designed and
developed to deliver real conceivable benefits to hospitals.

Hospital Management System is designed for multispecialty hospitals, to cover a wide range
of hospital administration and management processes. It is an integrated end-to-end Hospital
Management System that provides relevant information across the hospital to support
effective decision making for patient care, hospital administration and critical financial
accounting, in a seamless flow.

Hospital Management System is a software product suite designed to improve the quality and
management of hospital management in the areas of clinical process analysis and activity-
based costing. Hospital Management System enables you to develop your organization and
improve its effectiveness and quality of work. Managing the key processes efficiently is
critical to the success of the hospital helps you manage your processes.

1.2 Problem Introduction

 Lack of immediate retrievals: -

12
Project Report

The information is very difficult to retrieve and to find particular information like- E.g. - To
find out about the patient’s history, the user has to go through various registers. This results
in in convenience and wastage of time.

 Lack of immediate information storage: -

The information generated by various transactions takes time and efforts to be stored at right
place.

 Lack of prompt updating: -

Various changes to information like patient details or immunization details of child are
difficult to make as paper work is involved.

 Error prone manual calculation: -

Manual calculations are error prone and take a lot of time this may result in incorrect
information. For example, calculation of patient’s bill based on various treatments.

 Preparation of accurate and prompt reports: -

This becomes a difficult task as information is difficult to collect from various register.

1.3 Scope of the Project

 Information about Patients is done by just writing the Patients name, age and gender.
Whenever the Patient comes up his information is stored freshly.
 Bills are generated by recording price for each facility provided to Patient on a
separate sheet and at last they all are summed up.
 Diagnosis information to patients is generally recorded on the document, which
contains Patient information. It is destroyed after some time period to decrease the
paper load in the office.
 Immunization records of children are maintained in pre-formatted sheets, which are
kept in a file.
 Information about various diseases is not kept as any document. Doctors themselves
do this job by remembering various medicines.

All this work is done manually by the receptionist and other operational staff and lot of papers are
needed to be handled and taken care of. Doctors have to remember various medicines available for
diagnosis and sometimes miss better alternatives as they can’t remember them at that time.

13
Project Report

The proposed software product is the Hospital Management system (HMS). The system will be used
in any hospital, clinic, dispensary or pathology labs. Clinic, dispensary or pathology to get the
information from the patients and then storing that data for future usages. The current system in
use is a paper based system. It is too slow and cannot provide updated lists of patients within
reasonable timeframe.

1.4 Objective
The intention of the system is to reduce over-time pay and increase the number of patients that can be
treated accurately. Requirement statements in these documents are both functional and non-functional

1) Define hospital
2) Recording information about the Patients that come.
3) Recording information related to diagnosis given to Patients.
4) Keeping record of the Immunization provided to patients.
5) Keeping information about various diseases and medicines available to cure them.

These are the various jobs that need to be done in a Hospital by the operational staff and
Doctors. All these works are done on papers.

1.5 Goals
1-User friendly

2-Simple fast

3-Low cost and effective

4-It deals with the collection of patient’s information

5- Diagnosis

14
Project Report

Chapter 2
System Requirement Analysis

15
Project Report

System Requirement Analysis

2.1 System Analysis:

One of the most important factors in developing a system is to understanding the existing
system, its problems and limitations. A good understanding of the system enables designers
to identify the correct problem or limitation and suggested realistic solutions for the
problems. We must thoroughly understand the problem of the existing system and determine
how the computer can be used to make its operation more effective. The main responsibility
of conducting system studies, to learn relevant facts about working of the existing system,
thus only after the existing system if fully understood. It is responsibility to analyze it and
assemble recommendations for the system design. Therefore the study of the working of the
system and limitations of the existing system is an important task before the design phase.

2.2 Analysis of the Exiting System:

Hospitals currently use a manual system for the management and maintenance of critical
information. The current system requires numerous paper forms, with data stores spread
throughout the hospital management infrastructure. Often information is incomplete or does
not follow management standards. Forms are often lost in transit between departments
requiring a comprehensive auditing process to ensure that no vital information is lost.
Multiple copies of the same information exist in the hospital and may lead to inconsistencies
in data in various data stores.

2.3 Understanding the System:

The most important thing for successful system is proper understanding of existing system. In
manual shopping system their might be so many complexities, ambiguities, misconceptions
for taking attendance manually. So we decided to make the manual attendance system to be
computerized within a hand held device where a user can take attendance by his/her card.

2.4 Proposed System:

The Hospital Management System is designed for any hospital to replace their existing
manual paper based system. The new system is to control the information of patients. Room
availability, staff and operating room schedules and patient invoices. These services are to be

16
Project Report

provided in an efficient, cost effective manner, with the goal of reducing the time and
resources currently required for such tasks.

2.5 Data Analysis:

Data Analysis (DA) is a practice of science for examining the raw data to get organized so
that useful information can be extracted from it. The process of organizing and thinking about
data is a key to understanding what the data does and does not contain. Data analysis is the
process of systematically applying statistical and/ or logical techniques to describe and
illustrate, condense and recap, and evaluate data. The collected data serves as foundation for
the documentation of the system analysis phase.

System Requirements:
The purpose of gathering and analyzing the data is to establish the system requirements
because the design of the new system will be based on these requirements. Requirement
analysis provides the software designer with a model of:
System Information
Function
Behavior

2.6 Feasibility Study

A feasibility study is a test report of a proposed system. It identifies proposed system
workability, impact on the organization, ability to meet user needs, and effective use of
resource.

System feasibility is accessed in three principal ways:

 Technical
 Economical
 Operational

2.6.1 Technical Feasibility

This study is carried out to check the technical feasibility, that is, the technical requirements
of the system. Any system developed must not have a high demand on the available technical
resources. This will lead to high demands being placed on the client. The developed system
must have a modest requirement, as only minimal or null changes for the implementing this
system.

17
Project Report

2.6.2 Economic Feasibility

This study is carried out to check the economic impact will have on the system will have on
the organization. The amount of fund that the company can pour into the research and
development of the system is limited. The expenditures must be justified. Thus the developed
system as well within the budget and this was achieved because most of the technologies
used are freely available. Only the customized products have to be purchased.

2.6.3 Operational Feasibility

This study is carried out to check the technical feasibility, that is,the technical requirements
of the system. Any system developed must not have a high demand on the available technical
resources. This will lead to high demands being placed on the client. The developed system
must have a modest requirement, as only minimal or null changes for the implementing this
system.

2.7 The Proposed System

After the detailed study of existing system of shopping suggested an automated
(Computerized) system i.e. it eliminates the different problems faced by the admin and
member and manual system. This new Computerized System is the best possible solution to
the problems faced in existing system.

Through this system admin can add products, approve online request, add category, add
brands, view products, view brands, update category, customers and manage expense
information efficiently.

2.7.1 Advantages of Computerized System

Our project system has following advantages:

 User Friendly Interface

 Fast Access to database
 Less error
 More storage capacity
 Search facility
 Quick fee submission

18
Project Report

2.7.2 Objectives of the Proposed System

The new proposed computerized system is to design in a way to minimize the drawbacks of
present system. The proposed system has the following objectives:

Data Security:

The data required for decision-making is highly sensitive and valuable. Therefore the
proposed system will be secure and provides the options of password for data security.

Accuracy:

The new system will provide accurate and error free results. In this way, it ensures accuracy
and efficiency. It will ensure accurate record keeping.

Acceptability:

The new system should be acceptable for the store owner. It should satisfy the deficiencies of
existing system.

Reliability:

The new system is more reliable than existing one due to its accuracy and security, so that
timely decisions may be possible.

Flexibility:

The system allows changes and amendments to incorporate future requirements of the
management.

User Friendly:

No doubt, users want a system, which provides them user interface. The system will be as
much user friendly as possible so that the user could communicate with the system through
simple conversation. No specialized computer staff will be required.

Productivity:

Significant reduction of clerical staff will lead too much improved staff productivity.

Performance:
19
Project Report

The proposed system should reduce the time and efforts required to retrieve information. It
should have the capability to answer various queries instantly and efficiently.

Minimize the Redundancy:

The proposed system controls redundancy. This means the files are designed in such a way
that minimum data is duplicated in the files.

Comprehensive Database:

The proposed system have comprehensive database in which facilities of insertion,

modification, retrieval of records and facilities of various queries and reports are available.
There will be such facilities in the system that the users will feel ease and comfort to drive the
system and to save the data according to his will.

Time Factor:

Time is important factor in decision-making. The higher authorities require quick response to
their questions because decisions are based on updated information. The proposed
computerized system is too fast than old manual system.

Efficiency:

The proposed system will be more efficient than existing system because proposed system is
not time consuming. Efficiency is the degree to which we maximize of resources for
achieving an object or goal.

Ease of Operation:

Menu driven facility in main form and command button in other form makes it very easy to
operate the proposed system. Screen guides the operator through the system to provide the
required task.

20
Project Report

Chapter 3
System Design3.1 Introduction to System Design
System design lies at the core of the software engineering process and is applied regardless of
the software process model that is sued for development. Design simulation serves at the
foundation in the computer based development is a time consuming task. Beginning from
computer based system requirement analysis, system design is the first of three technical
activities i.e. design, code generation and test that are required to build and verify the validate
computer based system. The major goals of the design phase are creation of a system that
provides certain predefined functions, reliability of the system, flexibility, maintainability,
efficiency and security. After the comprehensive study of existing system, the developer
designs a system, which fulfills the requirements of the organization. The design of the
project is user friendly. The names of database tables and fields are simple and easy to
understand. In database design, database tables and fields are developed after careful
consideration of existing system to avoid redundancy and the errors. Any user can easily
understand the system. System provides the security to prevent illegal access. An interface
applies the flow of information. This phase deals with the design of system which consists of
following design consideration:

 Software design
 Database Design
 User Interface Design

3.2 Visual Representation using UML:

Visual modeling is the process of taking the information from the model and displaying it
graphically using some sort of standard set of graphical elements. The foremost purpose of
visual modeling is to represent the communication between users, developers, analysts,
testers, managers and anyone else involved with the project graphically and visually. In case
of increasing complex system, visualization and modeling become essential. The UML is a
well-defined and widely accepted response to that need.

A use case modeling language (UML) allows a software engineering express an analysis
modeling that is governed set of syntactic, semantic pragmatic rules.

21
Project Report

UML is a standard that has been adopted by the majority of the industries as well as the
standards governing boards such as ANSI and Object Management Group (OMG). UML
allows people to develop several different types of visual diagrams that represent various
aspects of the system. The diagrams which we discuss are as follows:

1. Use Case Diagram

2. Sequence Diagram
3. Activity Diagram

3.3 Use Case Diagrams

Use case diagrams describe what a system does from the standpoint of an external observer.
The emphasis is on what a system does rather than how. Use case diagrams are helpful in
three areas.

1. Determining feature (requirements).

2. Communication with clients
3. Generating test cases.

3.3.1 Use case Relationships

1. A use case generalization shows that one use case is simply a special kind of another.
2. Include relationships factor use case into additional ones.
3. An extend relationship indicates that one use case is a variation of another.
4. Each vertical dotted line is a lifetime, representing the time that an object exists.
5. Each arrow is a message call.

3.3.2 Elements of Use Case Diagram

1. Boundary- System boundary can be a computer system, organization boundary,
course boundary. The system functions and actors may change depending on the
system boundary location.
2. Actors- An external entity (person or machine) that interacts with or uses the system.
3. Sequence of events description- This describes a high level process of what an actor
will do with a system. An actor may perform an event to start the system.

This description does not represent individual steps in the process but represents the high
level process itself.

The two main components of the use case diagram are:

22
Project Report

1. Actor
2. Use case

Their description is given below

Actor
An actor represents a user or another system that will interact with the system you are modeling.

Use Case
A use case is the external view of the system that represents some action that user might perform in
order to complete a task.

23
Project Report

Use Case Diagram of Admin/User

Use Case Doctor

Patient

24
Project Report

3.4 Sequence Diagram

A sequence diagram is an interaction diagram that shows how processes operate with one
another and in what a sequence diagram shows object interactions arranged in time sequence.
It depicts the objects and classes involved in the scenario and the sequence of messages
exchanged between the objects needed to carry out the functionality of the scenario.
Sequence diagrams are typically associated with use case realizations in the Logical View of
the system under development. Sequence diagrams are sometimes called event diagrams or
event scenarios.

Actors and objects are showed at the top of the diagram. Each arrow represents a message
pass between actor and object or object and object to perform the required function.

25
Project Report

3.5 Activity Diagram

Activity diagrams are graphical representations of workflows of stepwise activities

and actions with support for choice, iteration and concurrency.

An activity diagram shows business and software

processes as a progression of actions. These actions can be
carried out by people, software components or computers.
Activity diagrams are used to describe business processes
and use cases as well as to document the
implementation of system processes.

26
Project Report

3.6 Component Diagram

A component diagram, also known as a UML component diagram, describes the organization

and wiring of the physical components in a system. Component diagrams are often drawn to
help model implementation details and double-check that every aspect of the system's
required functions is covered by planned development.

27
Project Report

3.7 Class Diagram

 Class diagram in the Unified Modeling Language (UML) is a type of static structure diagram

that describes the structure of a system by showing the system's classes, their attributes,
operations (or methods), and the relationships among objects.

The class diagram is the main building block of object-oriented modeling. It is used for
general conceptual modeling of the structure of the application, and for detailed modeling,

28
Project Report

translating the models into programming code. Class diagrams can also be used for data
modeling. The classes in a class diagram represent both the main elements, interactions in the
application, and the classes to be programmed.

In the diagram, classes are represented with boxes that contain three compartments:

The top compartment contains the name of the class. It is printed in bold and centered, and
the first letter is capitalized.

The middle compartment contains the attributes of the class. They are left-aligned and the
first letter is lowercase.

29
Project Report

3.8 Data Base

Introduction:
Every organization has some important needs. A company has to save information about their
running system. These pieces of information are called data. Organization can store data on
various media and in different formats. For example, a hard copy document in a filing cabinet
or data stored in electronic spreadsheets or in the database.

30
Project Report

Database is an organized collection of information. To manage databases, we need database

management system (DBMS). A database management system is a program that stores,
retrieves and modified data in a database on request.

The data is stored in computers in tables and databases; so far an accurate and free from
anomalies system, table designing is of key importance. Database designing is further sub
divided into two parts:

 Logical Database Design

 Physical Database Design

3.8.1 Logical Database Design:

Logical design of an information system defines the logical and conceptual relationship
among the components of information system. A logical design defines all the inputs that are
available to the system, all the output that must be produced by the system and all the process
that must be performed to meet the defined system requirements independent of how they
will be physically accomplished. The logical design does not address the actual methods of
implementation.

3.8.2 Physical Database Design:

Physical database design is the process of mapping the logical database structures developed
in previous stages into an internal model. Physical database is the last step in the database
design process. There are three major inputs to physical database design:

 Logical database structures that were developed during logical design. The database
design structures may be expressed as hierarchal, network and relational data models.
 User processing requirements that were identified during requirement definitions,
including size and frequency of use of the database and requirements for each of the
following:
o Response time
o Security
o Backup
o Relation of data
 Characteristics of the database management system (DBMS) and other components of
the computer operating environments.

31
Project Report

3.9 Database:
A database is collection of data, which is organized in such a way that each piece of data is
available to those who need it and with minimum duplication of data.

 Advantages of database

The most common advantages of database are:

 Minimal data redundancy

 Consistency of data
 Data integrity
 Uniform security, privacy and integrity controls
 Reduced program maintenance

 Constraints

These are the conditions that obey database.

 Entity
 Attributes
 Keys
 Super key
 Primary key
 Foreign key
 Candidate key.

Normalization:

The process of finding stable set of relations that is faithful model of the enterprise is known
as normalization. By following the principles of normalization we can achieve a design that is
highly flexible, allowing the model to be extended when needed to account for new
attributed, entity sets and relationship. We can also reduce redundancy in the database and
ensure that the design is free of certain updates, insertion and deletion anomalies. An
anomaly is an inconsistent, incomplete, or contra dictionary state of the database. If these
anomalies were present, we would be unable to represent some information, we might lose

32
Project Report

information when certain updates were prepared, and we would run the risk of having data
become inconsistent over time.

First Normal Form

First Normal Form sets very basic rules for an organized database:

 Eliminate duplicate columns from the same table

 Create separate tables for each group of related data and identify each row with a
unique column o set of columns

Second Normal Form

Second Normal Form further addresses the concept of removing duplicative data:

 Meet all the requirements of 1NF

 Remove subsets of data that apply to multiply rows of a table and place them in
separate tables
 Create relationship between these tables and their predecessors through the use of
foreign keys

Third Normal Form:

Third Normal Form goes on large step further

 Meet all the requirements of 2NF

 Remove columns that are not dependent upon the primary key

Database Design Approaches:

Design method and strategies are tools for the designer. The common design methods are
given below:

 Top down approach

 Bottom down approach
 Mixed approach

Top down approach

In this approach, we developed ERD based on the grouping of information given by the
business. But this grouping shows the current way of working of the business. It does not
cope with the needs of the new system.

33
Project Report

Bottom up approach
In this approach, we take the information from the business. Then on the basis of business
rules, we group them into a group of tables having certain relationship with one another
through normalization process. But by using this approach, keeping large organization in
view is quite tedious and somewhere impractical, where there are thousands of attributes. The
drawback of this approach is that we just ignore the grouping given by the business.

Mixed approach
Here we start with top down design by taking the logical grouping given by the business.
Then we use normalization to take that grouping into a form which matches new system
requirements. We have used mixed approach for our database design.

3.8 Tables of database:

 Login Details
 Department
 Rooms
 All Doctors
 Doctors Regular
 Doctor On Call
 Patient Entry
 Patient Checkup
 Regular Patients
 Operated Patients
 Admitted Patients
 Patient Discharged

34
Project Report

Description of Database Tables

Table Name: Signup

35
Project Report

Table Name: Department

Table Name: Room

36
Project Report

Table Name: All Doctors

37
Project Report

Table Name: Doctor On Call

38
Project Report

Table Name: Doctor Regular

39
Project Report

Table Name: Patient Entry

40
Project Report

Table Name: Patient Regular

41
Project Report

Table Name: Patient Operated

Table Name: Patient Admitted

42
Project Report

Table Name: Patient Discharged

43
Project Report

Chapter 4:
System Implementation & Development

44
Project Report

4.1 Introduction to System Development

Once the system design has been accomplished, the designer moves towards the development
phase of the software in accordance with the proposed system and design specification.
Special care is to be taken while selecting software. Development phase may be summarized
as collection

4.1.1 Testing of Software

The objective of testing the software is to determine whether the software satisfies the
requirements of the user or not. It will surely not satisfy some requirements if it still contains
errors. Testing is done throughout system, some of them are explained below:

 System Testing

This is applied on the software to ensure that the software has been operated according to its
desired requirements or not. In case of software failure, all necessary changes have to be done
in software in order to get required results. This test checks the size and structure of the data
fields using actual data and also the flow of test data.

 Unit Testing

In unit testing, each and every module of the software is tested independently form the other
using test data. This test is actually conducted to find errors like calculations, data formats,
I/O, comparisons and so forth.

 Black Box Testing:

Internal system design is not considered in this type of testing. Tests are based on
requirements and functionality.

 White Box Testing:

45
Project Report

This testing is based on knowledge of the internal logic of an application’s code. Also known
as Glass box Testing. Internal software and code working should be known for this type of
testing. Tests are based on coverage of code statements, branches, paths and conditions.
 Internal Integration Testing:

It is the bottom up approach for testing i.e. continuous testing of an application as new
functionality is added. Application functionality and modules should be independent enough
to test separately done by programmers or by testers.

4.2 Introduction to System Development

Once the system design has been accomplished, the designer moves towards the development
phase of the software in accordance with the proposed system and design specification.
Special care is to be taken while selecting software. Development phase may be summarized
as collection of the following steps:

Development for computer programs

Hardware and software
Testing of computer programs

4.3 Software Development & Implementation

The implementation stage of software is the process of converting a system specification into
executable system. It almost always involves processes of software design and programming.

4.3.1 Methods of Implementation

At some stage the methods by which implementation are to achieve will need to be decided.
The traditional methods are:

Parallel Running

In this method the new system and old system are running side-by-side. This method, I
believe that new software contains bugs, which came to know when real and massive data is
inserted into the database.

Pilot Running

In this method the new system is run for a part of the installation.
46
Project Report

Direct Change Over

In this method the new computerized system is introduced and old system simultaneously
abandoned.

Phased Conversion

In this method individual component of the new computerized system are

implemented one by one.4.4 Performance Testing:

This term often used interchangeably with ‘stress’ testing and ‘load’ testing to check whether
system meets performance requirements. It requires use of different performance and load
tools.

 Usability Testing:

It is the user friendliness testing of the application. Here application flow is tested. We have
to check either the new user understand the application easily or not. We also check here that
either the proper help is documented whenever the user stuck at any point or not. Basically
we check the system navigation in this testing.

 Testing Strategies

There are two strategies adopted mostly for the system testing, which are as follows:

1. Code Testing
2. Specification Testing

Code Testing

In code testing, the logic of the entire software has been tested and results are checked in time
and again to ensure 100% success during its run.

Specification Testing

47
Project Report

In this strategy, first the software specification is examined as what the software should do
and how should it do under various conditions. Then different test cases have been developed
and each of them is applied to confirm the performance of the requirements.

4.5 Language Selection

C-Sharp (C#):

C# is fastest and easiest way to create application for Microsoft Windows. Whether you are
an experienced professional or new to windows programming. C# provides you a complete
set of tools to develop simple rapid application.

The “VISUAL” part refers to the method used to create the graphical user interface rather
than writing numerous lines of code to describe the appearance and location of the interface
elements. The “BASIC” part refers to BASIC (Beginner’s All Purpose Symbolic Instruction
Code) language, a language used by more programmers than other languages in the history of
computing.

The Microsoft C# product has always been about providing a state-of-the-art Agile unified
process environment for Microsoft Windows. With the release of C# 3.5, the C# product
family has added functionality at the very highest level of the developer workspace, fully
supporting the development of enterprise-wide, line-of-business applications in a
programming environment that literally millions of developers have mastered.

C# is not just a language. It’s an Integrated Development Environment in which we can

develop, run, test and debug our programs. Controls available in this language are the basic
elements that we can use to design the user interface. We can add these controls to our
program and start using them without knowing how they will handle things going around.

Characteristics of C-Sharp (C#):

 It is one of the most famous programming languages in the world

 It is not difficult to learn and easy to utilize

48
Project Report

 It has a huge community support

 C# is an object-oriented language which gives a clear structure to programs and

allows code to be reused, lowering development costs.

 As C# is close to C, C++ and Java, it makes it easy for programmers to switch to C#

or vice versa

49
Project Report

Chapter 5
User Guide

50
Project Report

START OF THE PROJECT

51
Project Report

Register Your Self

52
Project Report

Login

53
Project Report

Test Cases Scenarios

Test Case ID T.1 Status

User Case Name UC-1 User Login

Test Scenario 1 Inputs: Invalid
User name:mudassirmalik
Password:12345
Output:
This error shown

Test Scenario 2 Inputs: Valid

User Name: Mudassir
Password: 123
Output:
Success Message Shown

54
Project Report

Main Menu

Close app: Button to close the program

Patient registration: Login to record patient information

Patient information: Login to see patient information

Chekout: Log in to the account list

55
Project Report

Room info: Access the room list and its information

Department Information

56
Project Report

All Information Off The Department,Location And About The Facilities Which
Are Provided.

Room Information

57
Project Report

Doctor Information

58
Project Report

Register New Patient

59
Project Report

Register Checkup

60
Project Report

Search Patient

61
Project Report

Search Doctor

62
Project Report

Chapter 6 Conclusion

63
Project Report

6.1 Conclusion

The project Hospital Management System (HMS) is for computerizing the working in a
hospital. The software takes care of all the requirements of an average hospital and is capable
to provide easy and effective storage of information related to patients that come up to the
hospital.

6.2Future work
Since we are entering details of the patients electronically in the” Hospital Management
System”, data will be secured. Using this application we can retrieve patient’s history with a
single click. Thus processing information will be faster. It guarantees accurate maintenance
of Patient details. It easily reduces the book keeping task and thus reduces the human effort
and increases accuracy speed.

64
Project Report

References

BOOKS

1 Database system Design Implementation and management

2 C# for Programmer 6th Edition

3 Object Oriented Programming IT Series

Websites

https://docs.microsoft.com/

www.Youtube .com

65