DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

HAWASSA UNIVERSITY

HAWASSA UNIVERSITY

INSTITUTE OF TECHNOLOGY

FACULTY OF INFORMATICS

DEPARTMENT OF INFORMATION SYSTEM

DEVELOPMENT OF NURSE AID MOBILE APPLICATION (NAMA)

BY

FULL NAME ID NUMBER

1. ABRHAM TIRUYE IS/0005/07
2. MULATU FURGASA IS/0103/07
3. GIZAT METALGN IS/0063/07
4. SHIMELIS NIGUSSIE IS/0068/06
5. TOLERA DELESA IS/0136/07

1|Page
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

ADVISORS: INSTRUCTOR. AMSALU DINOTE

FINAL PROJECT REPORT SUBMITED TO DEPARETEMENT OF INFORMATION
SYSTEM IN PARTIAL FULFILLEMENT OF THE REQUIREMENTS FOR THE
DEGREE OF BACHELOR OF SCIENCE IN INFORMATION SYSTEM
January 29
HAWASSA, ETHIOPIA

Declaration

The Project is our own and has not been presented for a degree in any other university and all the
sources of material used for the project/thesis have been duly acknowledged. (Name and
Signature of the project group members)

Name signature

1. ABRHAM TIRUYE …………………..

2. MULATU FURGASA …………………....

3. GIZAT METALGN ……………………

4. SHIMELIS NIGUSSIE ……………………

5. TOLERA DELESA ……………………

This is to certify that I have read this project and that in my opinion it is fully adequate, in scope

2|Page
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

and quality, as a project for the degree of Bachelor of Science.

Name of Advisor Signature

AMSALU DINOTE ………………………………….

Examiner Name Signature

1. Examiner 1 ………………………………………. …………………….

2. Examiner 2 ……………………………………….. ……………………..

3. Examiner 3 ……………………………………….. ……………………..

4. Examiner 4 ……………………………………….. …………………….

Acknowledgment
First of all, we would like to thank our GOD for giving all the capabilities to do things and
helped us from the start to the end. Secondly, our great thank goes to the school of informatics
for giving us the chance of getting the opportunity of education there. Third, we would like to
thank our advisor Instructor Amsalu Dinote for his indispensible comments, advises and ideas
from the start of the project to the end. And we would also like to convey thanks to the School of
informatics for providing the computer laboratory facilities .Finally, we have also a great
pleasure for employees of Hawassa university referral hospital especially Dr. Getu Shewa and
sister Belayinesh for spending their precious time with us and giving us the information we were
searching for.

3|Page
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Abstract
This document is written to give detail information about developing a nurse aid mobile
application (NAMA). It is intended to describe the general operations of the nurse that are being
performed daily. It is also aimed to describe the general approaches to be followed to automate
the existing manual system to android application. It is done using the object oriented approach
for development of the project. For the ease of understanding of the document, we have
structured it into five chapters. The first chapter is a general introduction and overview of the
proposed system. The second chapter onwards, we have given detail descriptions for the existing
and the newly proposed systems. The chapter also includes the existing system description
including its strength and weakness. The third chapter is about requirement elicitation processes
that include the functional, non-functional and system requirement , system modeling and

4|Page
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

includes concepts such as use case diagram, use case description, activity diagram, sequence
diagram, and class diagram etc. The fourth chapter is about system design and includes system
architecture, deployment diagram and the database architecture. The final chapter is aimed to
give conclusion and recommendation. The document is done by all the members of the group
and we attached the interview questions used while data collection as appendix at the end.

List of Acronyms
AVD……………………………….……………Android Virtual Device

BP………………………………………………..Blood rate

CD-ROM ………………………………………..Compact Disk Read Only Memory

DB………………………………………………..Database
DBMS…………………………………………….Database Management System

GUI ………………………………………………Graphical User Interface

HTML………………………………………………Hypertext Markup Language

5|Page
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

IPD…………………………………………………Inpatient Department

MySQL…………………………………………… My Structural Query Language 

NAMA………………………………………………Nurse Aid Mobile Application

OO…………………………………………………..Object oriented

OOP………………………………………………….Object Oriented Programming

OOSAD ………………………………………............Object oriented system analysis and design

OPD…………………………………………………..Outpatient Department

OS…………………………………………………….Operating System

PR………………………………………………………Pulse rate

RR………………………………………………………Respiration rate

UI ……………………………………………………..User Interface

UML…………………………………………………..Unified Markup Language

XML……………………………………………………eXtensible Markup Language

Table of Contents
Contents Pages
Declaration...................................................................................................................................................i
Acknowledgment.........................................................................................................................................ii
Abstract......................................................................................................................................................iii
List of Acronyms........................................................................................................................................iv
List of Tables.............................................................................................................................................vii
List of figures.............................................................................................................................................vii
CHAPTER ONE..........................................................................................................................................1
1. Introduction.........................................................................................................................................1

6|Page
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

1.1 Background of the Study...................................................................................................................1

1.2 Statement of the Problem...................................................................................................................2
1.3 Objective of the project.....................................................................................................................2
1.3.1 General objective........................................................................................................................2
1.3.2 Specific objective........................................................................................................................2
1.4 Scope of the study..............................................................................................................................2
1.5 Limitation of the study.......................................................................................................................3
1.6 Methodology.....................................................................................................................................3
1.6.1 Method of data collection...........................................................................................................3
1.6.2 System Analysis and Design Methodology.................................................................................4
1.6.3 Testing Methodology..................................................................................................................5
1.7 Development Environment............................................................................................................5
1.8 System Development Methodology...............................................................................................6
1.9 Feasibility Study............................................................................................................................6
CHAPTER TWO.........................................................................................................................................9
2 .Description of Existing System...............................................................................................................9
2.0 Introduction.......................................................................................................................................9
2.1 Description of the Existing System....................................................................................................9
2.1.1 Players of Existing System..........................................................................................................9
2.1.2 Business Rules for Existing system...........................................................................................10
2.2 Strength of the Existing System.......................................................................................................10
2.3 Forms and other Documents of the Existing Systems......................................................................11
2.4 Weakness of the Existing System....................................................................................................12
2.5 Proposed System Description..........................................................................................................12
CHAPTER THREE...................................................................................................................................13
3 .System Analysis and Modeling.............................................................................................................13
3.0 Requirements of the Proposed System..............................................................................................13
3.1 Functional requirements..................................................................................................................13
3.2 Nonfunctional Requirement.............................................................................................................14
3.3 System Use-Case Diagram..............................................................................................................15
3.3.1 Actors of the system...........................................................................................................15
3.3.2 Use cases of the system......................................................................................................16

7|Page
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

3.3.3 Description and relationship of actors and use cases..........................................................16

3.4 Sequence diagrams..........................................................................................................................25
3.5 Activity Diagram.............................................................................................................................28
3.7 Class Diagram.................................................................................................................................32
3.8 User Interface Design......................................................................................................................33
3.9 User Interface prototyping...............................................................................................................38
CHAPTER FOUR.....................................................................................................................................40
4. System Design.......................................................................................................................................40
4.1 Introduction.....................................................................................................................................40
4.2 Purpose and Goals of Design...........................................................................................................40
4.3 Proposed Software Architecture......................................................................................................41
4.3.1 Hardware/Software Mapping....................................................................................................42
4.4 Subsystem Decomposition...............................................................................................................43
4.5 Component Diagram........................................................................................................................44
4.6 Deployment Diagram.......................................................................................................................44
4.7 Database Design..............................................................................................................................45
4.7.1 Normalization...........................................................................................................................45
4.7.2 The General Database Table Structures....................................................................................47
4.8 Access control and security.............................................................................................................48
4.8.1 Security.....................................................................................................................................48
5.8.2 Access control matrix’s......................................................................................................49
CHAPTER FIVE.......................................................................................................................................50
5 Conclusion and Recommendation.....................................................................................................50
5.1 Conclusion.................................................................................................................................50
5.2 Recommendation.......................................................................................................................51
Appendixes............................................................................................................................................52
References.............................................................................................................................................54

List of Tables

8|Page
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Table 1-1 hardware and software tools........................................................................................................6

Table 3-1 Use case description for create user...........................................................................................18
Table 3-2 description for update account...................................................................................................19
Table 3-3 description for delete account....................................................................................................20
Table 3-4 Use case description for login...................................................................................................21
Table 3-5 Use case description for record prescription..............................................................................22
Table 3-6 Use case description for record vital sign..................................................................................23
Table 3-7 Use case description for generate report....................................................................................24
Table 3-8 Use case description for Search patient.....................................................................................25
Table 4-1 Access control matrix................................................................................................................49

List of figures
Figure 2-1 Patient identification card and doctor prescription form..........................................................11
Figure 2-2 Nurse vital sign form................................................................................................................11
Figure 3-1 Use case diagram for NAMA...................................................................................................16
Figure 3-2 sequence diagram for login......................................................................................................25
Figure 3-3 use case diagram for create account.........................................................................................25
Figure 3-4 Sequence diagram for record prescription................................................................................26
Figure 3-5 Sequence diagram for record vital sign....................................................................................26
Figure 3-6 Sequence diagram for generate report......................................................................................27
Figure 3-7 Activity diagram for create account.........................................................................................28
Figure 3-8 Figure Activity diagram for login............................................................................................29

9|Page
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 3-9 Activity diagram for record vital sign......................................................................................29

Figure 3-10 Activity diagram for recording prescription...........................................................................30
Figure 3-11 Activity diagram for generate report......................................................................................30
Figure 3-12 Activity diagram for search patient........................................................................................31
Figure 3-13 Class diagram of NAMA.......................................................................................................32
Figure 3-14 User interface for login..........................................................................................................33
Figure 3-15 user interface for medical director and signup form...............................................................34
Figure 3-16 User interface for Nurse Main menu and record patient information.....................................35
Figure 3-17 User interface for record vital sign and record prescription...................................................36
Figure 3-18 User interface for search patient.............................................................................................37
Figure 3-19 User interface prototyping......................................................................................................38
Figure 4-1 proposed software architecture for NAMA..............................................................................41
Figure 4-2 Hardware/software mapping....................................................................................................41
Figure 4-3 Subsystem decomposition for system......................................................................................42
Figure 4-4 Component diagram for NAMA..............................................................................................43
Figure 4-5 Deployment diagram for NAMA.............................................................................................44

CHAPTER ONE

1. Introduction
These days the numbers of mobile users are increasing and a lot of applications, and services
generate a lot of data, and information to mobile users and almost everyone is becoming a
mobile service user. As technology is the most dominating factor of these times in one or other
ways all human activities are becoming dependent on it and mobile computing is becoming fast
growing technology, for this reason integrating the medical system with the developing

10 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

technology specially making the system functional on mobile devices increases the availability
of the system and can address almost all users also facilitate service giving.

1.1 Background of the Study

The Hawassa referral hospital is an organization which gives healthy services for Ethiopian
peoples and Hawassa city societies. That was established in 1996 E.C in Hawassa town to solve
the health problem of Hawassa town peoples. This institution was under the control of Hawassa
University and SNNPR region and has power to perform works by its own and its annual budget
is only depending on the regional government because it is general hospital.
The hospital now a day has different services such as clinical services (Out Patient Department,
general surgery, dentistry, delivery, inpatient, and emergency) laboratory services (clinical
chemistry, hematology, serology, and bacteriology), other services (conventional x-ray,
ultrasound, and pharmacy) and also give maternal health care (Post-natal care, family planning,
and antenatal care).The hospital is using manual system for managing the overall activities of the
institution. In the hospital the advice to mothers is also being done by physical contact. The
circulation of information from one department to another is performed by people with paper and
card. Having the above core idea in mind our team builds an android based nurse aid mobile
application.

1.2 Statement of the Problem

In our project point of view the existing systems are manual based system has the following
major problems.

 Paper-based recording system is not secure which means patient’s information

can be visible for others, it can also get damaged.
 Wastage of time (in efficient use of time): during the exchange of information
between workers they use letters. So, the time is wasted until the required

11 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

information is reached to the required person. Also to generate a report from

manual system requires much effort and it is time consuming.
 Wastage of materials: the system needs pen; paper for printing the
documents for permanent recording. This is one reason for the wastage of
economy for the institution.

1.3 Objective of the project

1.3.1 General objective

The main objective of this project is to design and implement a nurse aid mobile application
which works on android operating system based mobile devices.

1.3.2 Specific objective

To achieve our general objective we set the following specific objectives

 Identify the problems of the existing system,

 Gathering and analyzing requirements of the existing system,
 Designing the database of the proposed system,
 Developing graphical user interface for proposed system,
 Testing the proposed developed system

1.4 Scope of the study

The scope of this project is developing Nurse Aid Mobile Application that is applicable only for
inpatient nurses, which gives fast service for the users of this application such as:

 Recording patient prescription

 Recording patient vital sign information
 Generating report which is used to show the status of a patient
 Searching patient’s medical records
 Chat used to facilitate the communication between nurse and medical director

12 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

1.5 Limitation of the study

There are many constraints that limit effectiveness and performance of our proposed system.

 As this system is android based (mobile based) it only works on smart phones
(android supportive platforms).

 Time: - comprehensive analysis of the existing system requires long time,

however, we couldn’t get enough time as we are also attending other courses
 System is applicable only for supporting inpatient nurses’ tasks
 The system is not going to be used to record some complex information about
patients like X-RAY results, ultrasound results and also some complex
diagrams, long text responses.
 The system is not support notification or alert message for chat
communication.

1.6 Methodology

1.6.1 Method of data collection

The data collection process to conduct this project includes both the qualitative and quantitative
data. This will be done through the use of instruments such as observation, interview. From these
two data gathering tools, interview will be used to collect data from the Hawassa University
referral and Hawassa Adair hospitals. Observation will also be used to oversee how the system
under study carrying out its tasks.

1.6.1.1 Interview
Interview is a conversation or questioning for the purpose of eliciting information for publication
using the available statement so elicited. To get the basic information and background
information about the existing system the team members has interviewed the health service
doctor and some health service nurses and identified some problems associated with that
environment.

13 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

1.6.1.2 Observation
Observation is the other instrument that was used to collect data which will be necessary for
developing our proposed application. In this process we tried to investigate the information by
physically availing ourselves and looking at what and how tasks are carried out in the system
under investigation. And observation also helped us to relate the information obtained from the
interview by looking to the reality of existing system.

1.6.2 System Analysis and Design Methodology

For our proposed system we preferred the object-oriented system analysis and design
(OOSAD) approach, which is usually facilitated by using unified modeling language
(UML). UML includes the overall features of OOSAD.

 Object-oriented techniques work well in situations where complicated systems

are undergoing contentious maintenance, adaptation and design

 Simplicity: software objects model real world objects, so the complexity is

reduced and the program structure is very clear.

 Reusability: the object oriented provides opportunities for reuse through the
concepts of inheritance, polymorphism, encapsulation and modularity. .
 Increased extensibility: -when we need to add new feature to the system we
only need to make changes in one part of the applicable class.

 Maintainable: OOP methods make code more maintainable. Objects can be

maintained separately, making locating and fixing problems easier. The
principles of good OOP design contribute to an application's maintainability.
 Modifiability: It is easy to make minor changes in the data
representation or the procedures in an OO program

14 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

1.6.3 Testing Methodology

Testing methodologies are approaches to testing, from unit testing through system testing and
beyond. There is no formally recognized body of testing methodologies, and very rarely will you
ever find a unified set of definitions. But here are some common methodologies:

1.6.3.1Unit testing: The act of testing software at the most basic (object) level. Generally
performed by developers, run in "friend classes" with code-level access to read and manipulate
objects.

1.6.3.2 Acceptance testing: Also known as acceptance tests, build verification tests, basic
verification tests, these are rudimentary tests which prove whether or not a given build is worth
deeper testing.

1.6.3.3 Functional testing: Functional testing takes a user story or a product feature and tests all
of the functionality contained within that feature. For example, in a photo application like
Photoshop, functional testing would cover all the functionality contained within a feature like
opening files (resolving file paths, determining appropriate format filters, passing the file path
off to the filter) as well as handling errors within that functionality.

1.6.3.4 System testing: Testing the project as a collective system. System testing generally
combines multiple features into an end-to-end process or scenario.

1.6.3.5 Performance testing: Tests an application's performance characteristics, be it file size,

concurrent users, or mean-time-to-failure.

1.6.3.6 Security testing: A collection of tests focused on probing an application's security, or its
ability to protect user assets.

1.7 Development Environment

The tools that we are going to use throughout our project are listed in the following table as
grouped into hardware tools &software tools.

15 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Tools
Hardware Software

 Processor: Intel(R) core(TM).i5-  Microsoft 2010 :to write the entire documents
[email protected]  Power point 2010 :for presentation for both
 Personal computer(Pc) phase1 and phase 2
 Pen and paper  Android studio to write and run the code
 Flash Disk : at minimum 8GB effectively & efficiently.
 RAM : to the minimum of 2GB  Programming Language like Java and XML
 Hard Disk: to the maximum of  Xampp server database for storing some
464.6GB useful information and data
 CD-R : to the maximum of 700MB  Visual paradigm for UML 10.2 : to draw
UML diagrams
Table 1-1 hardware and software tools
1.8 System Development Methodology
Object Oriented Approach: the method of system development paradigm we selected is the
object oriented approach because this approach is helpful for us to represent the different phases
of the project through many diagrammatic representations such as activity diagrams, use cases,
sequence diagrams, class diagrams etc.

Iterative System development approach: it is unusual to design a complete project once.

Therefore, to design our project we are required to review and redesign in each phase iteratively
to meet user requirements.

1.9 Feasibility Study

A feasibility study is a preliminary study undertaken to determine and document a project
practically. It is essential to evaluate the cost and benefits of the new system. On the basis of the
feasibility study, decision is taken on whether to proceed or to cancel the project.

Feasibility study categorized under four sections:

 Economic feasibility

16 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

 Technical feasibility
 Operational feasibility
 Schedule feasibility
 Political /behavioral feasibility

1.9.1 Technical Feasibility

It is the process of accessing the developed system by the institution. Technical feasibility is the
measure of practicality of the specific technical solution and the availability of technical
resources and expertise. The proposed system can be easily maintained and repaired without
requiring high Experts or technical assistants, because the system was developed by familiar
programming language (environment). The project team members have learned programming
languages that required for the successful completion of the project such as JAVA, HTML/XML,
OOP, and MySQL. Team members have the required skill to develop the system, So that the
project can be said technically feasible.

1.9.2 Economic Feasibility

The application is economically feasible as it only requires an android device with Android SDK
2.3 or higher. This would be the only cost incurred on the project and this project is
economically feasible; because the system is developed in low cost.

The system to be developed is economically feasible and the benefit is outweighing the cost.
Generally the system we developed for users (society) and hospitals will brought a number of
tangible and intangible benefits.

Tangible benefit:

 The reduction of cost

 Saves time and resources and impose easy and fast user treatment for hospitals.

Intangible benefits:

 The system we are developing has many in tangible benefits that revolve around
mental satisfaction.

17 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

 Gaining faster, efficient and satisfying service.

1.9.3 Operational Feasibility

This focuses on weather our system is operational. The system is operational in way that we have
decided to work it by effort and in collaboration with Nurses, and hospitals. This includes
detailed observations of existing system and preparing guidelines on how to use the system.

1.9.4 Schedule Feasibility

Our project is to be prepared or completed in a given time of period properly using some
methods like payback period (I.e. is concerned method of analysis with serious limitations and
qualification for its use).

Project team will develop the new system in the given period of time for the industrial project
since we have efficient number of members with the quality of respecting meeting times and
capacity of fulfilling responsibilities.

1.9.5 Behavioral /Political Feasibility

The New system doesn’t conflict with any government directives, because it gives services for
the people effectively and efficiently and doesn’t interrupt with any governmental (political) rule
and regulation so the government is profitable and the system will be politically feasible.

18 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

CHAPTER TWO

2 .Description of Existing System

2.0 Introduction
This chapter deals with analyzing the general work flow of the existing system, players in the
existing system. It produces a broad outline of the proposed system that identifies the function to
be performed and the technical aspect that the system must fulfill and briefly describes the
existing system functionality problem of the existing system.

2.1 Description of the Existing System

Currently the Hawassa university referral hospital is operating some of the functions of the
hospital manually. A detailed study/investigation has been made on the traditional system of the
healthcare by techniques like interviews and observation. The data collected by these techniques
also has been studied to arrive to a conclusion. The conclusion is an understanding of how the
system functions. The health system of Ethiopia is a four level health system, characterized by a
primary health care unit, and then the district hospital, zonal hospital and specialized hospital.

2.1.1 Players of Existing System

Patients: - peoples who need to take medication. Patient can be either inpatient or outpatient.

Nurse: -Person who keeps the patient and performs some tasks assigned by the doctor and has
the responsibility to take care of the patient in the given ward and serves the patient under the
order of the doctor. He/she also gives daily report about specific patient to the doctor.

Doctors: - are the persons who are skilled with various knowledge and perform appropriate
treatment to the patients and gives prescription for the patient. Some of their activities include:

 Treat the patient according to the lab result of the laboratory.

19 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

 Determine the patient to OPD and IPD.

 Generate report about the patient and sends to the record office.

Institution manager

 Observing the services given to the patient physically and also

observing the patient document.
 Examining reports reported from the record office.
 Manage workers of the institution.
 Approving referral for the patient.

Clerk:-Register and give identity card or patient card for the customers.

Runners:-persons who transfer patient information from clerk to doctor.

Pharmacist:-Give the drug/medicine ordered by the doctors. And generate report

for the record offices.

2.1.2 Business Rules for Existing system

The current system business rules are:-

1. In order to get diagnosis the patient must have service identification card.
2. The patient should stay until the order of payment is reached.
3. Perform payment.
4. Get the doctor and getting the advisory class by the order of the staff.
5. The doctor determine the patient is either IPD or OPD
6. The patient should wait until the doctor write the prescription to the nurse
7. The nurse can treat patient and advisory his/her

20 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

2.2 Strength of the Existing System

The major advantages of the current system are often used manual or paper based has the
following strengths:

 It is easy implemented: in order to use the system the user can understand and use easily.
 They have an organized structure to facilitate the tasks that are done by them.
 It is helpful for editing than on the paper

2.3 Forms and other Documents of the Existing Systems

Figure 2-1 Patient identification card and doctor prescription form

21 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 2-2 Nurse vital sign form

2.4 Weakness of the Existing System

The major problem of the existing system is often used manual (paper) based system so that it
takes much time to manipulate the overall activity of this system.
 Performance: Since the system is manual there is no good performance. Therefore, they
lack speed.
 It is difficult for searching and retrieving information
 Unable to provide effective and efficient service to the users or patients due to every
activity is performed by manual this problem is caused by the use of the manual system
and involvement of a number of employees. This also causes unnecessary wastage of
time, material, man power and other stationary materials and user dissatisfaction

 It is performing every task manually

 There is no centralized database to store all the data.

22 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

 Security: Free public access or an open environment refers to data or information read
by unauthorized people

2.5 Proposed System Description

Our proposed system will overcome the problems that are being seen in the manual system of
nurse aid. We are designing a mobile application that is manipulated by the managers of the
hospital or medical director and nurse that will serve as user for the system. The system that we
will develop can solve different problems that we have mentioned in the existing system. Our
Nurse Aid mobile application system a new system designed to be designed to minimize the
problem of current system which has described in the problem statement.

In general the proposed system has the following basic importance:

 It minimizes the time that required to do tasks and minimizes the cost that will invested
 The system can record appropriate new information within the database
 The system has high database security. Since each member in the school has its own
privilege to do any operation on the database
 Make the task easy and interactive
 It is user friendly, users can use it easily

CHAPTER THREE
3 .System Analysis and Modeling

3.0 Requirements of the Proposed System

We have undergone observation and interview methods of requirement gathering to collect the
requirements proposed to be done and what specifications or properties are required to have for
the proposed system. Based on these results got from methods, we have structured the
requirements in the following way as functional and nonfunctional requirements.

3.1 Functional requirements

The functional requirements are the services that are provided by the system. They also describe
the interactions between the system and the user, and with any other external system. They

23 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

describe user tasks that the system needs to support. Generally, functional requirements are
expressed in the form system must do (requirement). The following are the functional
requirements of the system:-

1. Record prescription: the main function of the proposed or the new system is to develop a
mobile patient recording. There for the nurse can record his/her patient’s prescription
information using this system.
2. Record Vital sign: the user can record vital sign information easily like blood rate, pulse
rate, and heart rate. The proposed system helps to do this task easily.
3. Search patient: whenever nurse need to check their patient’s information they can search for
patients who are being treated by them. The system we are developing facilitates easy and
fast searching of patients who are already recorded.
4. Generate report: the nurse can keep track of generate report that shows the status of the
patient in simple graph or form.
5. Chat:-used facilitate the communication between nurse and medical director
6. User management
 Account management i.e. creates user account, update account and delete
account.
 The system enables Users/Nurse to change their password.

3.2 Nonfunctional Requirement

These are the requirements that are not directly related with system but still are important as
equal as functional requirements to the system. They describe user visible aspects of the system
that are not designed to the functional behavior of the system. It describes performance,
accessibility, maintainability, security, availability, accuracy, and reliability of proposed system.
It defines how a system is supposed to be. Non-functional requirements are often called qualities
of a system. The following are considered as the non-functional requirements for the project we
are going to develop.
1. Security

24 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

The system provides username and password to prevent the system from unauthorized access.
All users of the system have username and password with different privilege. The system
administrator has username and password with administrative privilege and all other users has
username and password with standard privilege. Therefore, the system administrator can do all
his activities on the system and can update and delete the required information.
Since, this system is going to be developed for mobile devices it considered to be physically
secure because the only person who is going to use the device is the one who is the owner of that
device.

2. Performance

The system response time for every instruction conducted by the user must be short as far
possible. The system should have high performance rate when executing user’s input and should
be able to provide response within a short time.

3. Usability

After the proposed system is implemented it will be usable by nurse, The system provides a help
and support form in all interfaces for the user to interact with the system.The user can use the
system by reading help and support.

4. Error Handling

When a user interacts with the system errors may occur. To control this kind of inaccuracies
system will generate different user friendly messages. The system should return error message
when the user enters wrong input. Or this can be done by generating different system responses
to the input of the user.
5. User Interface

25 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

The system we are going to develop will have a user friendly graphical user interface (GUI) this
allows users to interact with the system easily. The user is expected to have knowledge of using
mobiles and also navigating through mobile interfaces.

7. Efficiency The system should allow users to perform their tasks with a short period of time.

3.3 System Use-Case Diagram

In software and system engineering, a use case is defined as a list of steps, typically defining
interaction between a role (known in UML as an “actor”) and a system, to achieve a goal. The
actor can be a human or an external system. In system engineering, use case diagram describe
what a system does from the viewpoint of an external observer. Means that System use case
diagram is a detail diagram that describes how external entities will use the system. It emphasis
on what a system does rather than how. A use case describes a function provided by the system
that yields a visible result for an actor. An actor describes any entity that interacts with the
system (e.g., a user, another system, the system’s physical environment). Use Case Diagrams are
closely connected to scenarios. A scenario is an example of what happens when someone
interacts with the system.

3.3.1 Actors of the system

Actors are the internal users, external users or other systems that have direct relationship with the
system. The actors involved in NAMA are:

 Medical director
 Nurse

3.3.2 Use cases of the system

Use cases are the tasks that are performed by different actors of the system. The use cases that
are performed in NAMA are:

 Login
 Register employee
 Create user account
 Update user account

26 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

 Delete user account

 Record prescription
 Record vital sign
 Generate report
 Search patient
 View report
 Chat

3.3.3 Description and relationship of actors and use cases

1. Medical director: is the manager of the hospital who has all the privileges to perform
any task such as creating, updating and viewing user accounts.
2. Nurses : are normal users who have less privilege to tasks than the medical director and
can do tasks such as login, record vital signs, record prescription, search patients medical
record ,

Use case diagram for NAMA

27 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 3-3 Use case diagram for NAMA

28 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

3.3.1 Use case Description

Use case description for create user

Use case name Register employee

Primary actor Medical director
Use case ID Uc01
Precondition The Medical director must login on the system
in his account.
Basic Flow of event

1. Press register employee button.

2. Account registration form will come.
3. Medical director fill signup form.
4. Press Register button.
5. Use case end.
Alternative action A1- if account is already created the system
will notify that the user cannot create
additional account.

Post condition Register successfully.

Table 3-2 Use case description for create user

29 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Use case name Add account

Primary actor Medical director
Use case ID Uc02
Precondition The Medical director must login on the system
in his account.
Basic Flow of event

1. Press create user button.

2. Account registration form will come.
3. Medical director fill signup form.
4. Press Register button.
5. Use case end.
Alternative action A1- if account is already created the system
will notify that the user cannot create
additional account.

Post condition Account is successfully created.

30 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Use case description for Update account

Use case Name Update user account
Primary actor Medical director
Use case ID Uc03
Precondition The actor must have username and
password
Basic course of action 1. The actor send update account request
to the system.
2. System displays the form to update
account to the actor
3. The actor enters key identifier of the
entity to be updated, select the value to
be updated as well as new value.
4. The system performs the intended
task.
5. use case end
Alternative course of action

A. if actor enter invalid data or no

exist value
A1. The system display message
invalid data or data not exist.
A2. The system prompts actor to
reenter the data by going to step
3 of the basic course of action.
A3. Use case end
Post condition The system shows the actor that the
action is completed successfully.
Table 3-3 description for update account

31 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Use case description for Delete account

Use case Name Delete account
Primary actor Medical director
Use case ID Uc04
Precondition The actor must have username and password

Basic course of action 1. The actor send delete information request to

the system.
2. System displays the form to delete
information to the actor
3. The actor enters key identifier of the entity to
be deleted.
4. The system asks the actor whether he/she
surely wants to do deletion.
5. The actor clicks the button that shows
sureness.
6. The system performs the intended task.
7. use case end

Alternative course of action

A. If actor data which is not existed.

A1. The system display message data
that does not exist
A2. The system prompts actor to reenter
the data by going to step 3 of the basic
course of action.
A3. Use case end
Post condition The system shows the actor that the action is
completed successfully.
Table 3-4 description for delete account

32 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Use case description for login

Use case Name Login
Actor Medical director, nurse
Use case ID Uc05
Precondition The actors must have username and password
Basic course of action 1. The actor send login request to the system.
2. System displays the login form to the
customer.
3. The actor enters its username, password
4. The system authenticates customer’s
username and password.
5. use case end
Alternative course of action

A. if customer enter invalid username and

password
A1. The system display message
invalid username and password.
A2. The system prompts customer to
try to by retrieve password going to
forgot password option and enter
security number to recover password.
A3. The system prompts users to
recover password if password is lost
then go to step 3 of the basic course of
action.
A4. Use case end
Post condition Customer login in the system and perform the
action that he/she want.
Table 3-5 Use case description for login

Use case description for record prescription

33 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Use case name Record prescription

Primary user Nurse
Use case ID Uc06
Precondition The nurse must login first to record
prescription.
Basic flow of event

1. Nurse enters necessary information of a

patient like drug name, form, frequency
etc.
2. Click register button.
3. Use end.

Post condition System acknowledges successful registration.

Use case description for record vital sign

Use case name Record vital sign
Primary actor Nurse
Use case ID Uc07
Precondition The actors must have username and password

34 | P a g e
Table 3-6 Use case description for record prescription
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Basic flow of event

1. System displays vital sign form.

2. Enter the vital sign information.
3. System checks the information’s that are
entered.
4. Press save button to record the
information.
5. Use end.
Alternative action A1- if the username and password of the nurse
should re-enter the correct username.
A2 – if the vital sign has not been registered
correctly system display information’s are not
registered.
Post condition System will acknowledge successful recording
of vital sign.
Table 3-7 Use case description for record vital sign

Use case description for generate report

Use case name Generate report

Primary actor Nurse
Use case ID Uc08
Precondition The actor must have username and password
Basic flow of event

1. Nurse click generate report button.

2. The actor enters key identifier of the

35 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

entity to be searched
3. Report generation form will display.
4. Press generate report button.
5. Use end.
Alternative condition

A. If actor enter data which is not existed.

A1. The system display message data
that does not exist
A2. The system prompts actor to
reenter the data by going to step 3 of
the basic course of action.
A3. Use case end.
Post condition The system shows/generate the actor needed
information.
Table 3-8 Use case description for generate report

Use case description for Search patient

Use case Name Search patient

Actor Medical director, nurse
Use case ID Uc09
Precondition The actor must have username and password
Basic course of action 1. The actor send search information request to
the system.

36 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

2. System displays the form to search

information to the actor
3. The actor enters key identifier of the entity
to be searched.
4. The system performs the intended task.
5. use case end
Alternative course of action

B. If actor enter data which is not existed.

A1. The system display message data
that does not exist
A2. The system prompts actor to
reenter the data by going to step 3 of
the basic course of action.
A3. Use case end
Post condition The system shows the actor needed
information.
Table 3-9 Use case description for Search patient
3.4 Sequence diagrams
Sequence diagram graphically document the use case by showing the classes, the message and
timing of the message. It depicts the interaction of between object during a certain period of
time. It is a construct of a message sequence chart. A sequence diagram shows object
interactions arranged in time sequence. It depicts the objects and classes involved in the scenario
and sequence of messages exchanged between the objects needed to carry out the functionality of
the scenario.

Sequence diagram for login

37 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 3-4 sequence diagram for login

Sequence diagram for create account

Figure 3-5 use case diagram for create account

38 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Sequence diagram for record prescription

Figure 3-6 Sequence diagram for record prescription

Sequence diagram for record vital sign

Figure 3-7 Sequence diagram for record vital sign

39 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Sequence diagram for generate report

Figure 3-8 Sequence diagram for generate report

3.5 Activity Diagram

Activity diagram shows also the conditional logic for the sequence of system activities needed to
accomplish a business process of proposed system in a good way [ CITATION Dou04 \l 1033 ].

Activity diagrams are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration and concurrency. In the unified modeling language, activity
diagrams can be used to describe the business and operational step-by-step workflows of
components in a system. An activity diagram shows in overall flow of control. In its basic form
an activity diagram is a simple and intuitive illustration of what happens in a workflow, what
activities can be done in parallel, and whether there are alternative paths through the workflow.

40 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Activity diagram for create user account

Figure 3-9 Activity diagram for create account

User accounts are created by the administrator of the system/medical director and nurses’ have
no privilege to do so. The administrator is expected to log as admin and is required to register
first name, last name, username, password, security number and privilege while creating user
accounts.

Activity diagram for login

41 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 3-10 Figure Activity diagram for login

Login is aimed to limit the unauthorized usage of the system so that users with username and
password can only have right to access with their predefined username and password.

Activity diagram for record vital sign

Figure 3-11 Activity diagram for record vital sign

Activity diagram for record prescription

42 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 3-12 Activity diagram for recording prescription

Activity diagram for generate report

Figure 3-13 Activity diagram for generate report

Activity diagram for search patient

43 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 3-14 Activity diagram for search patient

3.7 Class Diagram

A class is a description a set of objects that share the same attributes, operations, relationships,
and semantics [ CITATION Ste051 \l 1033 ] . Class diagram shows the static structure of an object-
oriented model the object class, their internal structure, and the relationship in which they
participate. It represent a detailed view of a single use case, shows the classes that participate in
the use case. Class diagrams involve detail aspects such as the attributes and operations within a
class as well.

44 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 3-15 Class diagram of NAMA

3.8 User Interface Design

The proposed system provides a good and interactive user interface which is simple for user and
easy to use and learn. User interface design for showing system works in Android studio
(emulator) pages for this application is shown in the figures below shows the interface screenshot
for the Login feature on the screen of Java ME device (or emulator).

45 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 15 User Interface for Login figure below shows the interface screenshot.

User interface for Login Page

Figure 3-16 User interface for login

46 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

User interface for medical director and signup form

Figure 3-17 user interface for medical director and signup form
This page is visible only to medical director and when he/she is need to create user account must
login on the system on the built in username and password or admin user and he/she can do
operation for instance if the user came into the system the medical director create new user
account first he/she logged on system on press create user account button or signup button then
signup form will display automatically and he/she fills the information finally press register
button and the will store on the database users table.

47 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

User interface for Main menu for Nurse and record patient information

Figure 3-18 User interface for Nurse Main menu and record patient information

A user can see this interface if account is initially created and both password and username
prompted by the user are correct. And then user can select the specific operations. For example
if the nurse or user is needs to register patient first select record patient button for the main
menu then the form will display automatically and he/she fill the information properly finally
record or register on the NAMA database on vital sign table. But it is not like Clerk records
patient information like cardNo, name of patient, sex and disease which means in which type of
disease he/she is infected.

48 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 17 shows the interface screenshot for the record vital sign feature after the user select
record vital sign icon like Blood pressure, Respiration rate, Pulse rate, Temperature. And record
prescription such as drug name, dose (amount of drug), route, date and time of prescribe from the
Main Menu.
User interface for record vital sign and record prescription

49 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 3-19 User interface for record vital sign and record prescription

Figure 18 below shows the interface screenshot for the Search Patient feature after the user select
Search Patient icon of the Main Menu.
User interface for search patient

50 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 3-20 User interface for search patient

The Search Patient interface provides the page to see or view the list of all patients medical
records’ and Search option to search for the patient’s medical record with the specified card no.

3.9 User Interface prototyping

User interface (UI) prototyping is an iterative development technique in which users are actively
involved in the mocking-up of the UI for a system. UI prototypes have several purposes as an
analysis artifact that enables you to explore the problem space with your stakeholders. As a
design artifact that enables you to explore the solution space of your system. A potential
foundation from which to continue developing the system In order to capture all the user
interface requirements of the user the Team member made through analysis and identified the
following user interfaces

51 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 3-21 User interface prototyping

CHAPTER FOUR
4. System Design

52 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

4.1 Introduction

After the determination of the requirements, it is the design that follows. The design is all about
stating the design goals of the system, proposed software architecture, subdividing the system
into smaller parts so as to tackle the problem in a modular approach, component diagram, and
deployment diagram and database design. This phase includes description of each subsystems
and the deployment of the subsystems. Not only had these, the database related to the
normalization of the database. For database purpose, a class diagram is used instead of E_R
diagram in the object oriented approach. .

4.2 Purpose and Goals of Design

The purpose and design goal of the system is to provide a solution for problems that are listed on
the analysis phase. Design goals are specification which the system needs to achieve.

The design goals are derived from the non-functional requirements of the system. They describe
the qualities of the system. These goals consider the following designing considerations. The
following are mentioned as the design goals of “Developing a Nurse Aid mobile application
(NAMA) “.

1. Security: The system does not allow non-authorized users using a form based
authentication. I.e. Access limitation is the means of security for the system.
2. Availability: the system should be available every time the user needs to access and it
should always be active and functioning until the battery life end.
3. Usability: the system should have user friendly user interface to allow the user to interact
with the system easily. It can be seen in two ways.

 Effectiveness: the system should provide services which help the user to achieve
their goal.

 Efficiency: the users should spend minimum effort and resource to achieve their
goal.

53 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

4. Effectiveness: the system should provide services which help the user to achieve their
goal.
5. Error handle: The system should be able to give response (error message) when the user
enter incorrect input. This recommends the user to enter correct input.
6. Portability: the system should be able to run on any mobile that supports android
operating system (OS) mobile applications.
7. Performance: the main performance measure for a project is time, so the system should
give fast responses for user requests and it should not take much space to be installed on
users’ smart phones.
8. User-friendly: the system should be easy to learn, understand and operate. It should
provide interactive and easy interfaces which can allow unprofessional users to deal with
it.

4.3 Proposed Software Architecture

The system architecture is designed on the basis of the context of the system in accordance with
the principles of architectural design as well as domain knowledge [ CITATION Dou04 \l 1033 ]. It is
the architecture that determines the type of interactions that the components are going to have
interaction.

It is the architecture that determines the type of interactions that the components are going to
have interaction. It uses Client/Server architecture. In this type of architecture the server is
responsible to receive a request from the client and respond to the request; on the other hand the
client is responsible to interact with that of the users of the system.

The clients are expected to install the application on each mobile. While the clients want to get
data from and add data to the system, they send requests to the database server. The database
server then responds based on the needs of the clients. The database application will be installed
in a single PC that may be wapsever /SQLite.

54 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 4-22 proposed software architecture for NAMA

4.3.1 Hardware/Software Mapping

Software/operating system mapping hardware mapping

Source: Bass, Len, Paul Clements, and Rick Kazman. Software Architecture in Practice, 2nd
ed. Addison-Wesley Professional, 2003.

Figure 4-23 Hardware/software mapping

55 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

4.4 Subsystem Decomposition

Subsystem decomposition also known as factoring, refers to the process by which a complex
problem or system is broken down into parts for the ease of understanding, we have divided the
system into sub systems or sub components. The Nurse Aid Mobile Application System is
decomposed into seven sub systems. The major subsystems identified are Login subsystem,
Create user, Record vital sign, Record prescription, Register Patient, Generate report subsystem,
search patient.

Subsystem decomposition will help reduce the complexity of the system. The subsystems can be
considered as packages holding related classes or objects. The Nurse Aid Mobile Application is
decomposed into the following subsystems.

1. The Database Subsystem

Most of the permanent data involved under the patient information will be stored into the
database. In addition to this, different data can be retrieved for manipulation.

2. The Login Subsystem

Authenticates user in order to check whether the user is the actual user or not.

Figure 4-24 Subsystem decomposition for system

56 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

4.5 Component Diagram

The purpose of a component diagram is to show the relationship between different components
in a system. Component diagrams allow the planner to identify the different components so he
know how the whole system does, how they connect and what it’s supposed to do.

Figure 4-25 Component diagram for NAMA

4.6 Deployment Diagram

Deployment diagrams model the physical architecture of a system, and it shows the relationships
between the software and hardware components in the system and the physical distribution of the
processing [ CITATION Dou04 \l 1033 ].

A deployment diagram is used to represent a static view of the run time configuration of
processing nodes and component that run on those nodes. In other words deployment
diagram show the hard ware of our system, the software that is installed on the hardware and
the middleware used to connect the disparate machine to one another .

57 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Figure 4-26 Deployment diagram for NAMA

4.7 Database Design

Database design is a visual representation of different tables using agreements that describe how
these tables are related to each other on our proposed system [ CITATION Ste051 \l 1033 ]. Database
design is the methodology for developing the various objects that make up a database (tables,
indexes, views, constraints, procedures, functions, etc.) as well as the relationships between
tables and the business rules for maintaining the data within them. The 'front end' is basically the
interface between the end user and the database. The proposed inventory systems have the
following tables

4.7.1 Normalization
Database normalization is used to remove more than values in a single tuple, to remove
functional dependencies between table columns, to ensure full dependency of all columns on the
primary key. It can be first normal form, second normal form, third normal form or other high
level normalization forms. But for best convenience, we have done up to third normal.

58 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

A. First Normal (1NF)

First normal is used to ensure that only a single value is recorded on a single cell of the database
table. Here, our relational schema structure is well thought of not having such problems
.Therefore, it can be used as first normalized form except for the patient table.

PATIENT
CardNo PatientName Sex Disease
00123 Aster Eyasu F TB

The problem here is that name of the patient can be comprised of at least first name and middle
name and hence cannot be stored in a single cell (tuple). Therefore, we have to create to columns
for each attribute values as follows.

Normalized form
PATIENT
CardNo Fname Lname Sex

Disease

00123 Aster Eyasu F

TB

B. Second normal (2NF)

It is aimed to remove functional dependencies among different columns of the database table.
The tables that need 2NF are the following:

59 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

 All requirements for 1st NF must be met.

 Avoid partial dependency.

 PK and FK relationship.

Normalized form
USER
user-Id password Username FirstName MiddleName LastName Sex Ward

Other tables have no problem of functional dependencies. Therefore, No need of normalizing

these tables since they are already in 2NF.

C. Third normal form (3NF)

It is helpful to remove transitive dependencies that exist in database tables. X->Y, Y->Z, then, if
and only if X->Z, we can say there is transitive dependency between the attributes. But here in
our database tables there are no such problems. Therefore we can say they are in third normal
form.

 Avoid transitive property based on the above table no transitive, so it is 3rd normal form.

4.7.2 The General Database Table Structures

User table Patient table

Attribute Data type Length Constraint Attribute Data type Length Constraint
User_Id Integer Primary key
Username varchar 30 NOT NULL CardNo Integer Primary key
Password Varchar 30 NOT NULL FirstName Varchar 15 NOT NULL
Frist name Varchar 15 NOT NULL LastName Varchar 15 NOT NULL
Middle name varchar 15 NOT NULL Sex Varchar 10
Last name varchar 15 NOT NULL Disease varchar 50 NOT NULL
Ward varchar 20 NOT NULL

60 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Prescription table vital sign table

Attribute Data type Length Constraint

Attribute Data type Length Constraint Vital signNo Integer Primary key
Press-No Integer Primary key
BP Varchar 20 NOT NULL
DrugName Varchar 50 NOT NULL
RR Varchar 20 NOT NULL
Dose Varchar 20 NOT NULL
Route Varchar 30 NOT NULL PR Varchar 30 NOT NULL
Date Date
Temp Varchar 30 NOT NULL
Time Time
CardNo Integer 20 Foreign key Date Date

Time Time
4.8 Access control and security
The system we are developing will be deployed
cardNo Integer Foreign key
on Smart mobile phones which are owned by a
particular physician or nurse, hence as long as the user is the actual user authenticated user can
access whatever the functions provided by the system.

4.8.1 Security
Here are some security issues taken in the system

 The users of the system must first login to perform operation and get services.
 Users’ information will be placed on the persistent database.
 The user name and password of the users are encrypted and store in the database.

5.8.2 Access control matrix’s

Access control is intended to specify the tasks that a specified user can and cannot do or can and
cannot have access. These can be achieved by giving certain privilege restrictions by using
access limit/control mechanism through username and password.

61 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Tasks
USER

Record Record Generate Register Search Manage

vital sign prescription report patient patient account
Medical Read and
director(MD) Write
operations

Nurse Read Read and Read and Read and Read

and Write Write Write Write operations
operations operations operations operations

CHAPTER FIVE

5 Conclusion and Recommendation

5.1 Conclusion
The project is partitioned into chapters and each chapter has a specific deliverable which is
Table 4-10 Access control matrix
essential and base for the next chapter. The first chapter

62 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

is the Introduction, in this part the major parts are: describing about background where the new
system is intended to be built on, the problems in the system that have been identified, the
feasibility plan studies; building a new system is possible or not from different perspectives.
After the scope of the proposed system has been defined the selected programming tools and
methods are stated and finally the project’s phases with their respective deliverable are stated,
each phase and its perspective work is scheduled. The second chapter is conducted based on the
first chapter. The first part in this section is analyzing the different activities of the current
system, then the problems which encountered doing these activities are analyzed and also the
strengths which must be preserved in the new system are identified. Then the next step is
developing alternative options to address the problems, and after different alternative evaluations
the one which is NAMA system is selected based on the actual evaluation and the challenges of
the alternative. The third chapter deals with describing and modeling the proposed system. The
functional as well as the non-functional requirements of the system. In doing the study the team
has tried to follow object oriented system analysis and design methodology. Since the success
and failure of any system depends on gathering the right information through different fact-
finding techniques and user involvements, the team has made the best effort to gather
requirements. After a detail review and study of the existing system have been designed to reflect
the new systems that are supposed to solve problems. In order to solve different problems
existed, the team has tried to propose a solution that at least reduce the existed problems and
model the proposed system using different tools and methodologies. The team believe the
different tools and techniques has helped us a lot in capturing real user requirements and model
the right system for the users for their day to day transactions. Thus it should have the
precedence in know-how and experience in collecting, processing and utilizing information.

5.2 Recommendation

 Any interested person in this area can improve the system to be applicable for both
supporting inpatient and outpatient nurses’ tasks and includes some tutorials or tips.
 And also system is will being to record some complex information about patients like X-
RAY results, ultrasound results and also some complex diagrams, long text responses

63 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

Appendixes

64 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

We are final year students of the faculty of Informatics of Hawassa University. We are doing
industrial project/developing an information system on the developing nurse aid mobile
application. Therefore, we need your positive attitude towards giving us the general working of
the Hawassa university referral hospital and Hawassa Adare hospital for not more than 50
minutes. Any information regarding personal issue is not required and information of patient
medical record will be kept secret.

Interview Questions

1. What are the basic tasks that are performed in the hospital?
2. What are the basic tasks that inpatient nurses’ performed in the hospital?
3. How nurse treat inpatient in the hospital?
4. Can you tell us something about the current system in your hospital?
5. What are the actors of existing system?
6. Can you tell us something about the strength and weakness (limitation) of current system
in the hospital?
7. In what way nurses’ communicate each other and with senior doctors’?
8. Is there any mobile based system (mobile application) developed for the hospital before?
9. Do you think the mobile based system will be helpful for you?
10. Is there anything you think is better to be included in this project?
11. Finally, if you have something you want to say us?

Thank you for your cooperation’s!!

65 | P a g e
 DEVELOPING A NURSE AID MOBILE APPLICATION 2017/18

References

 Elmasri, Ramex.Fundamentals of database systems.2nd.ed.Redwood city, CA:

Benjamin Cummings publication.
 Jacobson, Ivar. Software Engineering. New York: Mc Graw-Hill (1992).

 Object-Oriented Systems Analysis and Design Joey F. George, Dines Bart, Joseph S.
Valacich, Jeffrey A. Hoofer.

 Parsons/OJA, New Perspectives on Computers, Technology, and Society.

 Christine zhenwei Qiang, Masatake yamamichi, Vicky Hausman and Daniel Altman,
Mobile applications for the health sector, ICT sector unit World Bank, 2011.
 The object primer, Third edition, by Scott W.Ambler.
 System Analysis and Design for Software Engineering, prentice Hall of India
 Top 15 free Android medical apps for healthcare professionals
 New trends in mobile computing Medical application and localization By Doctor
Solomon Atnafu
 OReilly Developing Android Applications with Adobe AIR (2011)
 S.Agarwal and A.I Wasserman, Mobile application Development: A Developer Survey,
submitted for publication, 2010,
 Martin Flower, UML – distilled - A brief – guide, 2004
 Scott Ambler, The element of UML style, 2003

66 | P a g e