Gambella University

Faculty of Natural and Computational Science

Department of Computer Science
Course of Software Engineering
Web Based GMBU Clinical Management System
Submitted By:
No Name Id
1. Chalchisa Kano ……………………… 9794
2. Mohammed Adem……………….. …...8767
3. Emebet Ayanaw………………………. 8516
4. Minalu Kassa………………………….. 5083
5. Nyahok Thanyang…………………….. 9107

Submitted to: Dagnachew A.

Submission date: 11/07/2016

Gambella Ethiopia
Table of content

Table of content………………………………………………………………..1
List of figures…………………………………………………………………..2
Abstract………………………………………………………………………...3

Chapter 1: Introduction
1. Introduction……………………………………………………………………...3
1.1 Back ground of study…………………………………………………………..4
1.2 Statement of Problem ………………………………………………………….4
1.3 Objectives …………………………………………………………………….5
1.4 Significance of study…………………………………………………………...6
1.5 Scope of the project…………………………………………………………......6
1.6 limitation of the project………………………………………………………….7

Chapter 2: Related work

2.1 Related work……………………………………………………………………...7

Chapter 3: methodology
3.1 Functional requirement ………………………………………………………….. 8
3.2 Non-functional requirement …………………………………………………..12
3.3 software requirement ……………………………………………………………..12

Chapter 4: system design

4.1 system environment ……………………………………………………………..15

Chapter 5: System implementation

5.1 Some system forms……………………………………………………………....16
5.2 System use cases ……………………………………………………………….. 16
5.2.1 Admin use cases…...………………………………………………………… 16
5.2.2 Doctor use cases…..…………………………………………………………. 19
5.2.3 Nurse use cases………………………………………………………………. 21
5.2.4 Pharmacist use cases ………………………………………………………….23
5.3 Sequence diagrams ……………………………………………………………….24
5.3.1 System sequence diagram……………………………………………………….25
5.3.2 Login sequence diagram…………………………………………………………26
5.3.3 Register student sequence diagram………………………………………………27
5.3.4 Delete user sequence diagram……………………………………………………28
5.3.5 Search user sequence diagram…………………………………………………...29

1
5.3.6 Update user data………………………………………………………………………30
5.4 Class diagram…………………………………………………………………………..31
5.5 Activity diagrams ……………………………………………………………………… 32
5.6 Collaboration diagram…………………………………………………………………...35
5.7 Deployment diagrams …………………………………………………………………...36
Chapter 6: conclusion
Conclusion…....………………………………………………………………………….. …37
References……………………………………………………………………………………37
LIST OF FIGURES
Figure 4.1 System environment ………………………………………………………….15
Figure 5.1 Admin use cases ……………………………………………………………….16
Figure 5.2 Doctor Use cases ……………………………………………………………….19
Figure 5.3 Nurse Use cases ………………………………………………….....................21
Figure 5.4 Pharmacy use cases ……………………………………………………………..23
Figure 5.5 System sequence diagram ………………………………………………………25
Figure 5.6 Login Sequence diagram ……………………………………………………….26
Figure 5.7 Register Student sequence diagram …………………………………………….27
Figure 5.8 delete user sequence diagram ………………………………………………….. 28
Figure 5.9 search user sequence diagram………………………………………………… 29
Figure 5.10 update user sequence diagram………………………………………………… 30
Figure 5.11 class diagram ………………………………………………………………….. 31
Figure 4.12 Login Activity diagram …………………………………………………………32
Figure 4.13 get debt Activity diagram ……………………………………………………… 33
Figure 4.14 Instant message Activity diagram………………………………………………. 34
Figure 5.15 Collaboration
Diagram…………………………………………………………..35
Figure 5.16 CMS deployment diagram ………………………………………………………
36

2
Abstract:
Clinical management system (CMS) is a user support system which is developed to assist clinical staffs
(doctors, nurses, pharmacist, and clinical managers) in patient, drug, and clinical staffs record management.
CMS reduce the burden of clinical staff and change the manual (paper based) system to computerized
system, CMS also provide an efficient and systematic management environment within the clinic. In order
to provide this functionalities there are five main modules that need to be developed in CMS. The
methodology used for developing CMS is system development life cycle (SDLC). This system is written in
python 3.SQLite was utilized as the database for the system. Python development server used as web
server. This thesis will explains background study, methodology, system analysis, system design, system
development and implementation.

Chapter one
Introduction
1. Introduction

The purpose of this document is to present a detailed description of software system by which clinical
management system of Gambella university clinic will be built. It will explain the purpose, feature and
interface of the system as well as what the system will do and how it should interact with user of the
system. This document is mainly intended for the developers of the systems. By inspecting this document
painstakingly, they can develop user friendly, easy to use clinical management system for Gambella
university clinic. Since the system created from this document is also for GMBU clinical staffs (doctors,
nurses, pharmacist, and clinical manager) and Finance officers. These are just the user of the system, and
can see this document to verify whether the document include the functionalities that they needs.
Currently, GMBU clinic use manual (paper-based) system and store patient, drugs, and clinical staff’s
records on paper. For example, the clinic use cards to write down student’s medical information such as last
date visit, drug prescription, and laboratory results. Then those medical cards are placed in shelf which is
partitioned by department. And each department is categorized by year. And each year contains students’
medical card organized by students’ name sorted alphabetically. This work is troublesome and plaguing.
Moreover the student medical information is not secure.
The proposed system attempt to solve students’ medical information management and reduce the burden of
nurse and doctors. It is used as central repository of information that can be updated and accessed
electronically within a clinic, allowing sharing of vital student’s medical information between nurse and
doctors with security password access. These medical information has familiar resemblance to traditional
paper record that currently seen in GMBU clinic. The main aim of this proposed system is to computerize
the manual paper-based system.
As conclusion, the proposed system will bring benefits to doctors, nurses, pharmacist, clinical managers,
students, and finance officers. Its aims is to assist users in achieving their respective goals and objectives.

3
1.1 Back ground of study
GMBU clinic is found in Gambella University. Background of the Project Clinic Management System is
developed to improve the current Clinic management and automates the workflow that happens in the Clinic. This
system is considering all the activities in the Clinic. Patient will register first. However, if it is an existing patient
then the patient data is patient the time during the registration. In this process the record class will check whether
patient is exist in the previous registration or not by using the system itself. Then the system will update the patient
record and will be kept in in static html page. For the security, before the user enters the system they have to input
their username and password. The system has different access for the different users. For the management of the
Patient, they may view the daily report of daily work, also every doctor can have an account to do their task and card
room worker have an account to register Patient or to search the existing Patient. Our website reduces the manual
work, maintaining accuracy, increasing efficiency and saving time.

1.2 Statement of Problem

The paper-based system, which currently used in GMBU clinic, cause many problems to the user. When the
student first visit to the clinic, the nurse is required to fill in a new medical card for the student. This
include some private information that can be obtain from the student’s identity card such as name, identity
card number, department, gender … and then the nurse will pass this medical card to the doctor. After the
student sees the doctor, some diagnosis and treatment information will be written down on the medical card
by the doctor. After student getting their medicine, the nurse will keep that medical card on an organized
rack based on department as index of the card. These medical cards are grouped according to department
and year. Meaning that medical cards with the same department and year packed in single document case
and placed inside a cabinet. Plus the medical cards are arranged in alphabetical order according to the
student’s name. The nurse needs to search through the department, then year for the medical card that
match the student’s name for any subsequent visit of the student. Doing this manually is tedious, error
prone and plaguing. In addition after the doctor prescribe a drug, the student would go to the pharmacy and
receive the drug. When the student ask the pharmacist for what purpose the drug is for, it is not uncommon
to see pharmacist’s confused face which indicate lack of knowledge about all medicines. What is more,
during cost share calculations, the students those who get service from clinic pay the same amount of
money for health with the students those who do not get any kind of service from the clinic. This is also not
fair.

To summarize the following are the problems, which are observed in Gambella university clinic, lead us to
create a system.
 Lack of security
The medical card is easily exposed to unauthorized user. They can easily get the vital students’
medical information from the clinic because the medical card are just kept on the shelf without any
security lock.

4
  Time consuming
By using medical cards, times are wasted when the medical card need to pass from the nurse to
doctor. Besides that, the clinic also needs to speed times to organize the medical cards from time to
time. For example, when third year student become fourth year student, there are some information
need to be updated. Which also takes time.
 Space
Clinic needs to provide space to store these medical cards. When the quantity of cards increases
every year, they need more and more space to store the cards. This is very burning issue for
Gambella university clinic because currently the university expands its student intakes capacity.
Plus Gambella is lowland area and malaria is common disease in lowland. As a result many
students are infected with malaria and the clinic need more space to store medical card of those
student.
 Redundant information
Sometimes, a student can have more than one medical card. This happen when the medical card is
misplaced and people who do the registration did not check properly and just directly use a new
medical card.
 Lack of knowledge
Sometimes, the pharmacist may not have enough information about all the medicine that is in the
store. This happened because there are ton of medicine out there and knowing all the information
about all medicine is humanely impossible.
 Over Cost share
In GMBU, this happened because the student those who get service from clinic and the student
those who do not get service from the clinic pay the same amount of money for health. And this is
over cost share for those who does not get service from the clinic.
1.3 Objectives
1.3.1 General objective
The main aim of this proposed system is to computerize the manual (paper-based) system of
Gambella university clinic and enhance clinical management process in advance.
1.3.2 Specific objectives

i. To assist nurses and doctors in student record management

ii. To assist pharmacist in drug record management
iii. To assist the manager in clinical staffs record management

5
 iv. To tracing doctor’s diagnosis and treatments

v. Assisting nurses, doctors, pharmacist, and manager in digital communication

1.4 Significance of study
Our project (clinic management system) will be designed to give service to patient. After accomplishing of this
project the team member will consider the following significant as will be achieved from the system.

The main significance is listed:-

Once the new system is implemented, the workers are benefited from the system in such a way that the quality
and performance of their work is improved, the time they spent for manual operation is significantly reduced and
their management and control of their job is improved. Specifically students obtain the following advantages from
our system.

 Able to generate fast and enough information to the patient.

 Requesting for help.
 Fast data processing.
 Reduces the manual work.
 maintaining accuracy
 Increasing efficiency and saving time.
 It will minimize the work load due search patient history
 Their patient history will keep safe.
 It will reduce cost and resource wastage due clinic service.
 It will reduce the work load of clinic staffs.
 It will minimize the time due transferring of information between clinic department

1.5 Scope of the project

The proposed system is to be used in Gambella university clinic. The target users of the system are doctors,
nurses, pharmacist, and manager of the clinic and finance officers. This project is mainly emphasized on
developing a system for storing electronic student medical, drug, and clinical staffs’ records. And the target
users have access to one or more of those records in their own workspace. It also include some other
functions that can help the target users to improve their performance. In order to achieve this goal, this
proposed system can be divided into five module. Such as:
i. Registration module
ii. Nurse module
iii. pharmacy module
iv. Admin module
v. Finance office module
vi. Doctor module

6
The first module is registration module. This is where every registration is takes place. Students, clinical
staffs’ and drug can be registered to the database using this modules. All other module can use the
functionality of this module but not finance module.
The second module is nurse module. This is where the nurses add and delete student’s data, search for
registered students as well as passing student’s digital medical card to the doctor.
The third module is pharmacy module. This is where the pharmacy manage drugs, register drugs, search
drugs and see details information about drugs
The fourth module is administration module. This module help the manager to manage the employee, of the
clinic. This is where new clinic’s employee get registered, updated and deleted (if necessary). Plus this
module provide the manager database interfaces. So the manager can easily manage the database.

The fifth module is finance office module. This module help finance officer to get students’ debt from the
clinic during cost share calculation.
The six module is doctor module. This is where the doctor describe disease, prescribe drug and view
laboratory results.
1.6. Limitation of the Project
Our project will limit on the following activities:-

 Patient management system that related to clinic

 Registration patient on static website Because we will have a limited time to do this project it is difficult to
include those all the above activities

Chapter two
Related Work
Tremendous efforts have been made to address problems in healthcare industries, and various researches
have been embarked to provide solutions to the existing problems. They employed different approaches
and tools for requirement analysis, project design and implementation as steps towards enhancing the
effective processes needed for a modern healthcare system. Healthcare information systems are developed
to meet the following goals: improve quality of care, reduce organizational expense, and produce’ a data
stream for electronic billing. The CMS meets these goals through workflow automation, connectivity, and
consistent data sharing.
In research projects there were no functionalities such as online consultation and report generation.
However, the systems (mentioned above) need to be adjusted to comply with current requirements needed
in modern healthcare services. In view of this, functionalities such as online consultation, appointment
scheduling, diagnosis manager, report generator are added to the new system.

7
Hospitals and clinics can be regarded as organizations based on high technology and information’ intensive
processes.
Such organizations are not hierarchically structured bureaucracies but are often based on democratic
control mechanisms with institutionalized stakeholder influence in decision processes. It is also expected’
that health care budgets and funding will depend significantly on the sophisticated patient and diagnosis
classifications. The use of IT in diagnostic and treatment’ processes will add to the development of
networks of clinical, hospital and healthcare processes.
A considerable amount of literature has indicated that; healthcare management is a growing profession
with increasing opportunities in both direct and non-direct care settings. Direct-care settings are those
organizations that provide care directly to’ a patient, resident or client who seeks’ services from the
organization. Non direct care settings are not directly involved in providing’ care to persons needing health
services, but rather support the care of individuals through products and services made available to direct
care settings.
GMBU clinic is currently operating manually. Its various services include; patient consultation,
resuscitation and admission for observation during working hours, follow-up for hypertensive patients,
treatment of minor trauma and counseling with medical issues, patient treatment services such as wound
dressing and bandaging. The Clinic has full stocked pharmacy for provision of drugs and is being overseen
by Pharmacist. The administrative section handles data processing services. Such services are being
managed by assistant data processing officer and clerical officer using file processing approach. Therefore,
with the ill-equipped Information System, the stock cannot be managed properly. Most of these problems
can only be addressed if a proper Information System is developed.

Chapter 3
Methodology
3.1 Functional Requirement
This product have the following functional requirements
Login operation [Taking User Name; password]
Instant message
Front end requirement
3.1.1 Manage student
3.1.1.1 Student Registration
3.1.1.1.1 Taking Student first name (Mandatory)

8
 3.1.1.1.2 Taking Student last name (Mandatory)
3.1.1.1.3 Taking Student Identification number (Mandatory)
3.1.1.1.4 Selecting Student Department (Mandatory)
3.1.1.1.5 Select Department Year (Mandatory)
3.1.1.1.6 Selecting Student Age (Mandatory)
3.1.1.1.7 Selecting Student Sex (Mandatory)
3.1.1.1.8 Submitting the Form
3.1.1.1.9 Resetting the form
3.1.1.2 Search Student
3.1.1.2.1 Taking student identification number
3.1.1.2.1 Submission to search

3.1.1.3 Update student’s data

 Go through list of user, select particular user
 Able to see detail information
 Selecting update user
 Able to update user data in the separate screen

1. Update Student first name

2. Update Student last name
3. update Student Identification number
4. Selecting Student Department
5. Select Year
6. Selecting Student Age
7. Selecting Student Sex
8. Submitting the Form
9. Resetting the form
3.1.2 User Login
3.1.2.1 Taking user name
3.1.2.2 Taking password

9
 3.1.2.3 Submission of the Login
3.1.3 Manage Drug
3.1.3.1 Add Drug
3.1.3.1.1 Taking drug name
3.1.3.1.2 Taking drug expire date
3.1.3.1.3 Taking drug production date
3.1.3.1.4 Taking what it treat
3.1.3.1.5 Selecting production country
3.1.3.1.6 Selecting manufacturer
3.1.3.1.7 Selecting drug weight
3.1.3.1.8 Selecting side effects
3.1.3.1.9 Taking description
3.1.3.1.10 taking procedures
3.1.4.1.5 Submitting the form
3.1.4.2 Search Drug
3.1.4.1.1 Select Drug Name
3.1.4.1.2 Submission to Search
3.1.4.3 View drug details
3.1.4.4 Update drug
3.1.4 Get Student Debt
3.1.5 Instant message
3.1.6 Add payment
Back end (Administrative tools) requirement
1.1 Admin home page – All features availability
1.2 Manage users
1.2.1 Adding new user
1.2.1.1 Taking Login Name (Mandatory)

10
 1.2.1.2 Taking login Password (Mandatory)
1.2.1.3 Taking confirm Password (Mandatory)
1.2.1.4 . Taking first name (Mandatory)
1.2.1.5 . Taking last name (Mandatory)
1.2.1.6 . Taking e-mail in the e-mail format
1.2.1.7 . Taking phone number (Mandatory)
1.2.1.8 . Selecting user type (Mandatory)
1.2.1.9 . Submitting the form
1.2.1.10 . Resetting the form
1.2.2. Updating user
 Go through lists, selecting a particular user.
Able to view detail information
Selecting update user
Able to update user data in the separate screen

1.2.2.1. Update Login Name (Provided previous login name)

1.2.2.2. Update login Password (Provide previous login password)
1.2.2.4 . Update first name (Provide previous first name)
1.2.2.5 . Update last name (Provide previous last name)
1.2.2.6 . Update e-mail in the e-mail format (provided previous email-none)
1.2.2.7 . Update phone number (provided previous phone number)
1.2.2.8 . Update user type (provided previous value)
1.2.2.9 . Submitting the form
1.2.2.10 . Resetting the form
1.2.3. Search User
1.2.3.1 Select user name/user_id
1.2.3.2 Submission to search
1.2.4. Delete User
 Go through list of user, selecting a particular user.
 Able to view detail information

11
  Remove user

1.2.5. View User Activity

 Go thought list of user, select particular user
 Able to view detail information
 View history

1.2.6. Table of user data

1.3 manage databases
1.4 Instant message

3.2 Non-functional Requirement

• Operating System:
The software will be run on all operating system
• Usability:
Usability of software will be easy. So the users can use it without any difficulty
• Maintainability:
Software would be build up in such a way that classifications of error and
Maintenance of mechanism become easy
• Flexibility:
Software would be flexible so that it can easily accept all changes at low cost, time
and experience.
• Security:
Software will be secure. No one can use this application without Username
and password
• Access:
Software will be accessible over the internet
3.3. Software requirements

3.3.1. Framework, Language, and Tools

The language and tools that have been used to develop this project are as follows. We used
Django as a framework, python, HTML, MySQL, Cascading Style Sheets (CSS), JavaScript as an
implementing language.
3.3.2. Django

12
Django is python framework that makes it easier to create web sites using python. It takes care of
the difficult stuff. So that you can concentrate on building your web application. The main reason
we select Django is that it follows MVT design pattern (Model View Template).

Model – the data we want to present, usually data from database

View – a request handler that returns the relevant template and content-based on the request from
user. Template – a text file containing the layout of the web page, with logic on how to display the
data.

3.3.3. PYTHON
Python is a popular programming language. It was created by Guido van Rossum, and released
in 1991. It is an easy to learn, powerful programming language. It has efficient high-level data
structures and a simple but effective approach to object-oriented programming. Python’s elegant
syntax and dynamic typing, together with its interpreted nature, make it an ideal language for
scripting and rapid application development in many areas on most platforms

It is used for:

• web development (server-side),

• software development,
• mathematics,
• System scripting.
3.3.4. HTML
HTML stands for Hyper Text Markup Language. HTML is a language for defining the building of
Web pages. HTML grants authors the means to,

• Distribute online documents with tables, lists, photos, titles, topic, etc.
• Improve online data via hypertext links, at the click of a button.
• Design schemes for operating activities with foreign services, for use in exploring for data, presenting
licenses, ordering products, etc.
• Include covers-sheets, video clips, sound clips, and other applications immediately in their reports.

3.3.5 CSS
CSS is the language for describing the performance of Web pages, including appearances, layout
design, and fonts. It enables one to adjust the presentation to various types of devices, such as big
screens, small screens, or printers. CSS is confident of HTML and can be used with any XML based
markup language. The division of HTML from CSS performs it more comfortable to establish sites,

13
receive style sheets pages, and original pages to different conditions. That is committed to as the
division of construction from a presentation

3.3.6 JavaScript
JavaScript is the world’s most successful web-based programming language. It is the language for
HTML, for the web, for servers, PCs, laptops, tablets, phones, and more. JavaScript is a Scripting
Language.
• JavaScript is programming code that can be implanted into HTML pages.
• All modern web browsers can perform JavaScript code.
• JavaScript is clear to learn

3.3.7 Tools
A software development tool is a program or applications that Software Developers use to design,
debug, maintain, or otherwise maintain other programs and applications. The term applies
typically to nearly simple programs, which can be connected coincidentally to perform a
Task, much as one might use multiple control tools fix a physical object to
improve this website utilizing the following tools:

• Pycharm community text editors: for writing the program

• Notepad++
• MySQL Workbench
• Xampp Server: for hosting web application
• Browser
• Wonder share edraw max : for drawing diagrams
• Microsoft office word 2013, Liber Office writer: to write this SRS document
• Window 10 photo applications: to edit drawn diagram of edraw max
• Window 10 screen shot application: to take screenshot
3.4 Database
A database is an arranged group of data. The data are typically prepared to design essential characters
of reality in a way that maintains means demanding this information. The resulting database is
working to improve this website is MySQL.
Database is a must for our Project. All the experience will be stored in that database. For our
application, the database is a significant aspect. The database needs to be stable and secure because
security is a significant problem for a web application. So to select a database is essential and more
important than any other things for our project. We like MySQL because it is the most suitable
database for us for some reasons. Those reasons will be given below. A MySQL database is a
hosting database that is used to store students, drug, and clinical staffs. A MySQL database is the
usual general type of relational database on the web today. That is partly because it is free but also
very important. In basic terms, a MySQL database is intelligent about saving any data that you
want. It will let you quickly store and retrieve information MySQL is a database server.

14
 • It is ideal for both small and large application.
• MySQL Supports standard SQL.
• It is free to download and use.
• It compiles on some platforms.
These are the purposes we used MySQL as our database because it is so important to select the
right database for our application otherwise the whole hard work may go in vain. That’s why
considering all the options we’ve chosen this database, and it was so useful for our project as well
as the web application.
To build our web application, we needed a database server which is perfect for small and large use.
We needed a database that maintains standard SQL and also compiles some platforms. The end
and essential fact of the database is if it is free to download and practice or not.

Chapter 4 System design

4.1 System environment

Figure 4.1 System environment

15
 Chapter 5
System Implementation

5.1. Some system forms

The web-based clinic management system includes various forms and use cases to help facilitate the
management of a clinic. The system includes forms such as patient registration, appointment request,
medical history, prescription, and billing. Generally, a form serves as a user interface where information is
entered by the user. The information is then passed to a back-end server for processing.

5.2. System Use Cases

This section outlines the use cases for each users. All users have more than one use cases
5.2.1 Admin use case
The clinical manager has the following sets of use cases:

16
 Figure 5.1 Admin use cases

Use case: login

Brief description
The admin can login to the system as administrator
Initial Step-by-Step Description
Before this use case can be initiated, the system will provide a login page with username and
password
1. The admin will provide username and password
2. The admin will interact with login button
Use case: manage database
Brief description:
The admin manage the database that this system based on.

Initial Step-By-Step Description

17
  Before this use case can be initiated, the admin has to login to the system as admin and should have
access to the admin home page.

1 System presents manage database button in action panel

2 The admin will click (choose) “manage database” button
3 The system present list of databases and “create database” button
4 The admin can see the tables in the give database and perform any CRUD operation or he can
create new database and table
Use case: Add user
Brief description
 The admin can register (add) a new employee to the system.
Initial Step-by-Step Description
 Before this use case can be initiated, the admin has to login to the system as admin and should
have access to the admin home page.
1. The system present “add user” button
2. The admin will interact with the button
3. The system will provide a submit form
4. The admin will fill all the required field and hit submit button
5 .The system will tell the admin whether the operation is successful or not
Use case: search user
Brief description:
 The admin can search a particular registered user using UID.
Initial Step-By-Step Description
 Before this use case can be initiated, the admin has to login to the system as admin and should have
access to the admin home page.

1) The system provide “search user here” text field and search button
2) The admin will provide user’s ID to text field and hit search button 3) The system will
display all the information about the user, “delete user”, “Update user”, and “User
activates” buttons.

Use case: update user

Brief description
 The admin can user data if necessary
Initial Step-by-Step Description
 Before this use case initiated, the admin has to login to the system as admin and should have
access to the admin home page and click on particular user.
1) The system will provide a form with pre-filled fields and “save” button
2) the admin will replace the fields which are necessary to be updated and hit
“save” button
3) The system will let the admin know whether it is updated successfully or not.

18
Use case: delete user
Brief description
 The admin can delete a particular user if necessary
Initial Step-by-Step Description
 Before this use case initiated, the admin has to login to the system as admin and should have
access to the admin home page and click on particular user need to be deleted
1) The system will provide “delete user” button in action panel
2) The admin will click “delete user” button
3) The system will ask the admin “action cannot be undo, are you sure to delete?”
4) The admin will choose “yes” to delete or “no” to cancel the deletion.

5.2.2 Doctor Use case

 The doctor have the following set of use cases:

19
Figure 5.2 Doctor Use cases
Use case: login
Brief Description
 The doctor can login to the system as doctor.
Initial Step-by-Step Description
 Before this use case can be initiated, the doctor should go to home page with appropriate URL.
1. The system provide to doctor a form which contain Username and password field.
2 .The doctor will fill the form and interact with login button.
Use case: Search student
Brief Description
 The doctor can search a student using their CID
Initial Step-by-Step Description
20
  Before this use case can be initiated, the doctor should have access to Doctor’s home page
1) The system will provide “search student here” text field and “search” button
2) The doctor will fill the text field with student CID and hit “search” button
3) The system will display user as clickable list

Use case: show student medical history

Brief Description
 The doctor view student’s medical history if necessary
Initial Step-by-Step Description
 Before this use case can be initiated, the doctor should login to the system and have access
to the doctor’s home page as well as click a particular student.
1. The system will display basic student information (full name, age …) and
“medical history” button
2. The doctor will interact with “medical history” button
3. The system will provide him student past medical treatment (like diseases, drugs, laboratory
result) categorizing by month.

Use case: Drug prescription

Brief Description
 The doctor can order drug for student
Initial Step-by-Step Description
 Before this use case can be initiated, the doctor have to access to doctor’s home page and
click on a particular student among the list.
1. The system will provide “drug prescription” button
2. The doctor click on “drug prescription” button
3. the system will provide him a form
4. the doctor will fill the form and click “save” button
Use case: disease description
Brief Description
 The doctor can order drug for student
Initial Step-by-Step Description
 Before this use case can be initiated, the doctor have to access to doctor’s home page and click on a
particular student among the list.

1) The system will provide “disease description” button in diagnosis panel

2) The doctor click on “drug prescription” button
3) The system will provide him a form
4) The doctor will fill the form and click “save” button
5.2.3 Nurse Use Case
 The nurse have the following use cases

21
Figure 5.3 Nurse Use cases

Use case: login

Brief Description
 The nurse can login to the system as nurse
Initial Step-by-Step Description
 Before this use case can be initiated, the system should provide login page
1. The system provide a form which contain username and Password field

22
 2. The nurse will fill the form and hit login button
Use Case: Register Student
Brief Description
 The nurse can register a new students and observe their information
Initial Step-by-Step Description
 Before this use case can be initiated, the nurse have to access the nurse’s home page
1. The system provide “register student” button in nurse panel
2. The nurse will click “register student” button
3. The system will redirect the nurse to registration page
4. The nurse will fill the form with the appropriate data and submit the data to save
5. the system will tell the nurse whether it is registered successfully or not

Use Case: Search student

Brief Description
 The nurse can search a particular student using CID
Initial Step-by-Step Description
 Before this use case can be initiated, the nurse have to access to the nurse’s home page
1. The system will provide a text field and “search” button
2. The nurse will fill the student’s CID to text field and hit “search” button
3. The system will display a user as clickable list.
Use case: Update student’s data
Brief Description
 The nurse can modify student’s data if necessary
Initial Step-by-Step Description
 Before this use case can be initiated, the nurse have to access to the nurse’s home page and should
search and click at particular student.
1) The system will provide “update user” button in action panel
2) The nurse will click “update user” button
3) The system will provide a form with pre-filled fields
4) The nurse will replace the pre-filled fields with new database
5) The nurse will hit “save” button

5.2.4 Pharmacist Use case

 The pharmacist have the following use cases

23
 Figure 5.4 Pharmacy use cases
Use case: login
Brief Description
 The pharmacist login to the system as a pharmacist
Initial Step-by-Step Description
 Before this use case can be initiated, the system should provide him a login page
1) The system provide to pharmacist a form which contain username and password field
2) The pharmacist will fill the form and hit login button

Use case: add drug

Brief Description

24
  The pharmacist will register drug when not registered drug is available
Initial Step-by-Step Description
 Before this use case can be initiated, the pharmacist have to access the pharmacist home page
1) The system provide “add drug” button in action panel
2) The pharmacist will hit “add drug” button
3) The system will redirect the pharmacist to drug registration page
4) The system will show form fields
5) The pharmacist will fill the form and hit register button
6) The system let the pharmacist know whether or not the operation is successfully.

Use Case: Search drug

Brief Description
 The pharmacist can search particular drug by using DID
Initial Step-by-Step Description
 Before this use case can be initiated, the pharmacist have to access pharmacist home page
1) The system will provide “search drug here” text field and “search” button
2) The pharmacists will providing DID for text field and hit “search” button
3) The system will show detail information about drug.

Use Case: View drug detail

Brief Description
 The pharmacist can see detail information about drug
Initial Step-by-Step Description
 Before this use case can be initiated, the pharmacist have to access pharmacist home page and search
particular drug
1) The actor will click on searched drug
2) The system will show detail data about the drug such production data, expiration date, drug’s
name
3) The system will show detail information about drug.

5.3 Sequence diagram

Sequence diagrams model the interactions between objects in a single use case. They illustrate
how the different parts of a system interact with each other to carry out a function, and the order in
which the interactions occur when a particular use case is executed.
In simpler words, a sequence diagram shows how different parts of a system work in a
‘Sequence’ to get something done. The following sequence diagrams show each steps that
happened on each use cases.

25
A sequence diagram is structured in such a way that it represents a timeline that begins at the top
and descends gradually to mark the sequence of interactions. Each object has a column and the
messages exchanged between them are represented by arrows.
5.3.1 System sequence diagram:

The figure down below show each sequences that are performed when a particular student visit
the clinic and get service from it. Which shows the processes that happed from student registration
up to taking drugs and going back to dorm.

Figure 5.5 system sequence diagram

26
5.3.2 Login sequence diagram:
Login is the use case of all users. Which mean that this product will cover the database records with
username and password. The login sequence diagram shows things that happened during the login
process. How each user can login and what steps have to implemented during login is depicted by
the following sequence diagram

Figure 5.6 Login sequence diagram

27
5.3.3 Register student sequence diagram

The following diagram show the sequence of actions that need to be performed during register student
use case

Figure 5.7 register student sequence diagram

28
5.3.4 Delete user sequence diagram

Figure 5.8 delete user sequence diagram

29
5.3.5 Search user sequence diagram

Figure 5.9 search user sequence diagram

30
5.3.6 Update user data

Figure 5.10 update user sequence diagram

31
5.4 Class Diagram

Figure 5.11 class diagram

32
5.5 Activity Diagram
 An activity diagram visually presents a series of actions or flow of control in a system similar to
data flow diagram. It can also describe the steps in a use case diagram.

5.5.1 Login Activity diagram

 The following diagram show flow control of login use case

Figure 5.12 Login Activity diagram

33
5.5.2 Get debt Activity diagram

Figure 5.13 get debt Activity diagram

34
5.5.3 Instant Message activity diagram

Figure 5.14 Instant Message Activity diagram

35
5.6 Collaboration Diagram

Figure 5.15 Collaboration Diagram

36
5.7 Deployment Diagram Deployment diagram describes the software system’s specifications
and physical hardware system required to run the software. The deployment diagram also
determines the installation of the software on the hardware. It maps software segments of
method to the device that is going to implement it. The following diagram deployment
diagram of GMBU clinic management system.

Figure 5.16 CMS deployment diagram

37
 Chapter 6
Conclusion
As described above, each chapter of this SRS document explain different thing about the
proposed applications. In chapter one allover description explained perfectly including
hardware and software requirement that CMS need to run. Functionality of products
explained from chapter two up to the chapter three. Diagrammatically fives chapter
diagramed most of the software components not mentioning lot of limitation of this
software and this documents. So any software developer can see this document and create
web-based clinical management system which computerize paper-based system and reduce
the burden of clinical staff.
References:
 https://www.studocu.com/in/document/apj-abdul-kalam-technologicaluniversity/software-
project-management/srs-example-for-web-application/20881481

 https://ir.unimas.my/id/eprint/3354/1/Clinical%20management%20system%20(CM
S).pdf

 https://www.slideshare.net/vidyasg/srs-present

 https://www.slideshare.net/susheel2658/srs-for-virtual-eucation

38