University of Electronic Science and

Technology of china
Software Development techniques
Mini Project

Hospital management system

Group members:
Alimey Fred John- 201424070134 - School of automation
Kussia Bulbula Kumeda 201424060134 School of computer science
Batamuliza Jenifer 2014240600124 - School of computer science
Nteziriza Nkerabahizi Josbert 201424060135 - School of computer science

Table of Contents
INTRODUCTION

AIMS AND OBJECTIVES

APPROACHES TO PROJECT

REQUIREMENTS SPECIFICATION

METHODOLOGY

SYSTEM DESIGN

USE CASE DIAGRAM

CLASS DIAGRAM

12

LOGIN STATE CHART/TRANSITION DIAGRAM

13

OBJECT RELATIONSHIP DIAGRAM

14

CONCLUSION

15

SUMMARY OF PROBLEMS, ACHIEVEMENTS AND CHALLENGES

15

INTRODUCTION
Most typical hospitals around the world maintain records of all their patients, doctors,
nurses and their staffs. These hospitals follow all cases reported by patients through the
process of registering the patient for new comers and giving them a card, which contains
a unique identity with which the patient can always check back if he/she has a health
problem for treatment. Initially these hospitals keep this record using the manual system
(File system) which can be very slow, time consuming, difficulty in retrieving patient
data as their might be a huge bank of data files to check, limited security and many more.
Considering the rapid growth of computer systems and the constraints of the manual
system (file system), there is the need for faster and efficient data storage and retrieval
system which is leading to manual system (File systems), gradually moving to automated
system, as this system proves to store and retrieve data faster and efficiently.
Even with the great change over from manual to automated systems, challenges still
abound, Such challenges majors around privacy and security hence, the need for a system
that will provide privacy, security (i.e. a system that controls who sees what and can do
what) combined with faster and efficient data storage and retrieval. Hospital management
system is designed take care of both the constraints of the file system and the privacy and
security challenges that arise with most automated system.

Aims and objectives

The aim of this project is to use a windows-based technology to develop application for
hospital management that runs on cross platform. This is to enable the various entities in
a hospital setup, to effectively manage patients data in a more efficient and secure
manner. To achieve this aim, we would design system that provides the following:
A central and secured repository of patient data.
Tools for faster record search in case of patient file retrieval.
Easy storing and updating patient details.

 Granting data access to specific system users so as to protect user privacy

Approaches to Project
Due to time constraint we would also use the observation and existing document
sampling technique for requirement gathering, as every other technique (e.g. Interviews,
questionnaire etc.) might be difficult and time consuming (Requirement gathering) this
requirements would further be classified into functional and non-functional requirement.
The project is jackleg using the incremental model of software engineering. This objectoriented technique enables the project to be to be developed in bits (Increment) with
increased functionality from subsequent increments (Methodologies and designs). For
reasons of availability and compatibility, we would be building the system using VB
.NET and SQL server development tools on a windows platform (Development tools
and Environment)

Requirements Specification
Functional requirement: This requirement describes the functions and
behaviors of hospital management system i.e. it shows what the system does
or what is expected of the system.
No.

Requirements

Use Case(s)

1.

To Capture and store, update Patient details

Capture and store new patient details

2.

To create users (Hospital staff)

Create new user

3.

To assign access level to staff

Assign access level to user

4.

To Capture, store, update delete staff

Capture, store, update user

5.

Assign nurse to patient (temporarily)

Assigns nurse

6.

Assign Doctors to patients

Assign doctors

7.

Capture Patient diagnosis information

Store patient Diagnosis

8.

Capture patient test results

Store test results

Non-Functional requirements
Describe functions not really concerned with system functions but with how
well the system does what it should, how reliable the system is etc.
I.
II.
III.

Easy to navigate user interface

To provide easy and fast retrieval of patient data
Easy storage ability

Methodology

The Incremental Approach to the system development
Hospital management system is a system that is in design process for the purpose of
recording, storing and the identification of patient records. This system is being built
using the incremental approach to system development as it a huge project, which needs
more time, genuine requirements from user etc.

Putting all these factors into

consideration (getting all requirements from the users at once would be very difficult and
time consuming), the project team has decided to build the system in phases such that any
additional functionality gained from user requirement can be added in future.

Hospital management system is currently built to take care of the basic operations of a
typical hospital.
With the incremental approach to the system development, the system would be
designed, implemented and tested incrementally (a little more added each time) until the
system is finished. This approach involves both development and maintenance.
The hospital management system would be defined as finished when it satisfies all of its
requirements.
This model combines elements of the waterfall with the iterative philosophy of
prototyping. As said earlier, with the incremental approach, the system is decomposed
into a number of components each of which is designed separately, and delivered to the
user when finished. This allows for the partial utilization of the products and avoids long
development time amongst many more advantages to using incremental approach of
system development (Hospital management system).
Some other advantages include:
This approach avoids a large initial capital outlay and subsequent long waiting
period
After each iteration, a regression testing is conducted, during testing faulty
elements of the system can be quickly identified and corrected
This approach is generally easier to test and debug than other methods of software
development.
More flexible, less costly to change scope and requirements

Even though the incremental approach to system development has a numerous number of
advantages, it also has some drawbacks, which can easily be taken care of.
Some disadvantages include:
Resulting cost may exceed cost budgeted
Needs a clear definition and complete definition of the whole system before it can
be broken down
As additional functionality is added, problems may arise related to the system
architecture which were not evident in earlier prototypes

System Design
Hospital management system design will be demonstrated using some popular UML
diagrams. These diagrams include:
Used Cases diagram
Class diagram
State transition (Behavioral model)
Object relationship

Use case diagram

I. System administrator

II. Receptionist

III. Nurse

IV. Doctors

V. Lab Technician


Class Diagram

Login State chart/transition diagram

Object relationship diagram

Development tools and environments

The system is developed using
I. Database management system (DBMS) Sql server 2005
II.

VB .NET 2008 and Dev Express for interface design.

Reasons for tool and environment choices

SQL server is compatible with most programing languages, it is also less
expensive as compared to oracle and easily available VB .NET easy for
designing windows based user interface Windows OS- it is widely used and
Available.

Conclusion
Summary of Problems, Achievements and Challenges
Coming this far has not been without any challenge. A strategy was devised
to cope with the circumstances in order to come out with the best. The task
was quite onerous such that any information needed had to be traced from
the project site, which was an inconvenience.
A major challenge in the development of this package was, choosing an
appropriate technology to meet the short time development requirement