HAWSSA UNIVERSITY

INSTITUTE OF TECHNOLOGY
FACULTY OF INFORMATICS COMPUTER
SCIENCE DEPARTMENT

INDUSTRIAL PROJECT ON
ANDROID BASED ANTENATAL CARE SYSTEM

Group Members
No. Name ID Number

1. Abenezer Leta CS/0012/08

2. Buzuneh Kenenisa CS/0065/08

3. Fasika Dessalegn CS/ 0092 /08

4. Betelhem Bassazinew CS/0050 /08

5. Silenat Birhanu CS/0184/08

Advisor: Ayele Sankura

Submitted to Faculty of Informatics

February 18 2019
Hawassa, Ethiopia

i
 Declaration

This is to certify that I have read this project and that in my opinion it is fully adequate, in scope
and quality, as a senior project for the degree of Bachelor of Science.
Ayele Sankura __________
Name of Advisor signature

Examining committee members’ name, signature and date

1. Chairman: Name _______________________ Signature _________ Date __________________

2. Examiner 1: Name _______________________ Signature _________ Date __________________

3. Examiner 2: Name _______________________ Signature _________ Date __________________

ii
 Table of content
DECLARATION ---------------------------------------------------------------------------------------------- II
TABLE OF CONTENT ------------------------------------------------------------------------------------- III
ACKNOWLEDGEMENT -----------------------------------------------------------------------------------V
LIST OF FIGURES ------------------------------------------------------------------------------------------VI
LIST OF ANONYMS AND ABBREVIATIONS -----------------------------------------------------VIII
ABSTRACT---------------------------------------------------------------------------------------------------IX
CHAPTER ONE---------------------------------------------------------------------------------------------- 10
1 INTRODUCTION -------------------------------------------------------------------------------------- 10
1.1 BACKGROUND OF THE STUDY ------------------------------------------------------------------------------------------------ 11
1.2 STATEMENT OF THE PROBLEM ----------------------------------------------------------------------------------------------- 12
1.3 OBJECTIVE OF THE PROJECT ------------------------------------------------------------------------------------------------- 12
1.3.1 General Objective --------------------------------------------------------------------------------------------------- 12
1.3.2 Specific Objective ---------------------------------------------------------------------------------------------------- 12
1.4 SIGNIFICANCE OF THE PROJECT --------------------------------------------------------------------------------------------- 13
1.5 SCOPE OF THE PROJECT -------------------------------------------------------------------------------------------------------- 14
1.6 LIMITATION OF THE STUDY --------------------------------------------------------------------------------------------------- 14
1.7 METHODOLOGY ------------------------------------------------------------------------------------------------------------------ 15
1.7.1 Data collection methodology -------------------------------------------------------------------------------------- 15
1.7.2 System analysis and Design methodology --------------------------------------------------------------------- 16
1.7.3 System implementation -------------------------------------------------------------------------------------------- 16
1.7.4 Testing and deployment methodology -------------------------------------------------------------------------- 17
1.8 DEVELOPMENT ENVIRONMENT ---------------------------------------------------------------------------------------------- 19
1.9 SYSTEM REQUIREMENT -------------------------------------------------------------------------------------------------------- 20
1.10 FEASIBILITY STUDY-------------------------------------------------------------------------------------------------------------- 20
1.10.1 Technical feasibility ------------------------------------------------------------------------------------------------- 20
1.10.2 Operational feasibility ---------------------------------------------------------------------------------------------- 20
1.10.3 Economic feasibility ------------------------------------------------------------------------------------------------- 21
1.11 TIME SCHEDULING --------------------------------------------------------------------------------------------------------------- 22

CHAPTER TWO --------------------------------------------------------------------------------------------- 23

2 DESCRIPTION OF EXISTING SYSTEM --------------------------------------------------------- 23
2.1 INTRODUCTION ------------------------------------------------------------------------------------------------------------------- 23
2.2 STRENGTH OF THE EXISTING SYSTEM-------------------------------------------------------------------------------------- 23
2.3 WEAKNESS OF THE EXISTING SYSTEM ------------------------------------------------------------------------------------- 24
2.4 PROPOSED SYSTEM DESCRIPTION ------------------------------------------------------------------------------------------- 24

CHAPTER THREE ------------------------------------------------------------------------------------------ 26

3 SYSTEM FEATURES --------------------------------------------------------------------------------- 26
3.1 INTRODUCTION ------------------------------------------------------------------------------------------------------------------- 26

iii
 3.2 FUNCTIONAL REQUIREMENTS ------------------------------------------------------------------------------------------------ 26
3.3 NON-FUNCTIONAL REQUIREMENTS ----------------------------------------------------------------------------------------- 28
3.4 ANALYSIS AND MODELING ----------------------------------------------------------------------------------------------------- 29
3.4.1 Introduction----------------------------------------------------------------------------------------------------------- 29
3.4.2 Use case model ------------------------------------------------------------------------------------------------------- 29
3.4.3 Use case diagram ---------------------------------------------------------------------------------------------------- 31
3.4.4 Use case descriptions------------------------------------------------------------------------------------------------ 32
3.4.6 Sequence diagram --------------------------------------------------------------------------------------------------- 47
3.4.7 Activity diagram ----------------------------------------------------------------------------------------------------- 53
3.4.8 Analysis level Class diagram -------------------------------------------------------------------------------------- 63

CHAPTER FOUR -------------------------------------------------------------------------------------------- 64

4 SYSTEM FEATURES --------------------------------------------------------------------------------- 64
4.1 INTRODUCTION ------------------------------------------------------------------------------------------------------------------- 64
4.1.1 Purpose of the system Design Document (SDD) -------------------------------------------------------------- 64
4.3 ARCHITECTURAL DESIGN ----------------------------------------------------------------------------------------------------- 65
4.3.1 Deployment View ---------------------------------------------------------------------------------------------------- 65
4.4 DATABASE DESIGN -------------------------------------------------------------------------------------------------------------- 67
4.4.1 ER Diagram----------------------------------------------------------------------------------------------------------- 67
4.4.2 Relational Mapping ------------------------------------------------------------------------------------------------- 68
4.4.3 Database Normalization ------------------------------------------------------------------------------------------- 70
4.4.5 Access control and security Access control -------------------------------------------------------------------- 73
4.5 USER INTERFACE PROTOTYPING -------------------------------------------------------------------------------------------- 74
4.5.1 Navigation Tree For web-based application ------------------------------------------------------------------ 74
4.5.2 Navigation Tree for mobile based application ---------------------------------------------------------------- 75
4.6 USER INTERFACE DESIGN ----------------------------------------------------------------------------------------------------- 76

CHAPTER FIVE --------------------------------------------------------------------------------------------- 81

5 CONCLUSION AND RECOMMENDATIONS -------------------------------------------------- 81
5.1 CONCLUSION ---------------------------------------------------------------------------------------------------------------------- 81
5.2 RECOMMENDATION ------------------------------------------------------------------------------------------------------------- 82
REFERENCES --------------------------------------------------------------------------------------------------------------------------------- 83
APPENDIX-------------------------------------------------------------------------------------------------------------------------------------- 84

iv
 Acknowledgement
First of all, we would like to thank our God for helping us in every step of our project and for
giving us wisdom and strength to do this project.

Next, we would like to thank our advisor Mr. Ayele Sankura for his advice and his help by
sharing his knowledge for us and his precious time. After that we would like to thank Dr.
Asnake and other health professional working in the health institution for giving valuable
information related to antenatal care system. We also would like to express our gratitude to Ato
Tesfaye who is the manager of Family Guidance Association of Ethiopia Southern Area Office
for accepting us to work and communicate with them and for his will to help us and to give an
information and facilitating the environment to get information.

v
 List of Figures
FIGURE 3. 1 REPRESENTATION OF ACTOR 29
FIGURE 3. 2 REPRESENTATION OF USE CASE 30
FIGURE 3. 3 REPRESENTATION OF SYSTEM BOUNDARY 30
FIGURE 3. 4 REPRESENTATION OF USE CASE DIAGRAM 31
FIGURE 3. 5 SEQUENCE DIAGRAM FOR LOGIN 47
FIGURE 3. 6 SEQUENCE DIAGRAM FOR SIGNUP 48
FIGURE 3. 7 SEQUENCE DIAGRAM FOR VIEW SYMPTOMS 48
FIGURE 3. 8 SEQUENCE DIAGRAM FOR VIEW ADVICE 49
FIGURE 3. 9 SEQUENCE DIAGRAM FOR REGISTER HP 49
FIGURE 3. 10 SEQUENCE DIAGRAM FOR SEARCH 50
FIGURE 3. 11 SEQUENCE DIAGRAM FOR MAKE APPOINTMENT 50
FIGURE 3. 12 SEQUENCE DIAGRAM FOR CHANGE PASSWORD 51
FIGURE 3. 13 SEQUENCE DIAGRAM FOR SEND MESSAGE 51
FIGURE 3. 14 SEQUENCE DIAGRAM VIEW HISTORY 52
FIGURE 3. 15 SEQUENCE DIAGRAM FOR UPDATE HP 52
FIGURE 3. 16 ACTIVITY DIAGRAM FOR LOGIN 53
FIGURE 3. 17 ACTIVITY DIAGRAM FOR SIGNUP 54
FIGURE 3. 18 ACTIVITY DIAGRAM FOR VIEW SYMPTOMS 55
FIGURE 3. 19 ACTIVITY DIAGRAM TO REGISTER HP 56
FIGURE 3. 20 ACTIVITY DIAGRAM FOR SEARCH 57
FIGURE 3. 21 ACTIVITY DIAGRAM FOR VIEW APPOINTMENT 58
FIGURE 3. 22 ACTIVITY DIAGRAM FOR VIEW MESSAGE 59
FIGURE 3. 23 ACTIVITY DIAGRAM FOR VIEW ADVICE 60
FIGURE 3. 24 ACTIVITY DIAGRAM FOR SEND MESSAGE 61
FIGURE 3. 25 ACTIVITY DIAGRAM FOR MAKE APPOINTMENT 61
FIGURE 3. 26 ACTIVITY DIAGRAM FOR UPDATE HP 62
FIGURE 3. 27 CLASS DIAGRAM 63

FIGURE 4. 1 DEPLOYMENT DIAGRAM ............................................................................................................66

FIGURE 4. 2 ER DIAGRAM ......................................................................................................................................67
FIGURE 4. 3 PROTOTYPING FOR ADMIN AND HP (WEB-BASED) ............................................................74
FIGURE 4. 4 PROTOTYPE OF PREGNANT WOMAN'S PAGE (MOBILE APPLICATION BASED) .......75
FIGURE 4. 5 USER INTERFACE DESIGN FROM PREGNANT WOMAN SIDE ..........................................77
FIGURE 4. 6 ADIM LOGIN PAGE .......................................................................................................................78
FIGURE 4. 7 ADMIN HOME PAGE ................................................................................................................................78
FIGURE 4. 8 REGISTRATION FOR HP ...........................................................................................................................79
FIGURE 4. 9 CHANGE PASSWORD UI ..........................................................................................................................79
FIGURE 4. 10 DELETE ACCOUNT FORM .........................................................................................................80

vi
 List of Tables
TABLE1. 1 HARDWARE TOOLS ..........................................................................................................................19
TABLE1. 2 SOFTWARE TOOLS ...........................................................................................................................19
TABLE1. 3 TANGIBLE COST ................................................................................................................................21
TABLE1. 4 TIME SCHEDULING .............................................................................................................................22

TABLE 3. 1 LOGIN USE CASE DESCRIPTION ....................................................................................................32

TABLE 3. 2 SIGNUP USE CASE DESCRIPTION ...................................................................................................33
TABLE 3. 3 CHOOSE LANGUAGE USE CASE DESCRIPTION .....................ERROR! BOOKMARK NOT DEFINED.
TABLE 3. 4 VIEW SYMPTOMS USE CASE DESCRIPTION.................................................................................34
TABLE 3. 5 VIEW ADVICE USE CASE DESCRIPTION .......................................................................................35
TABLE 3. 6 SEARCH USE CASE DESCRIPTION ..................................................................................................37
TABLE 3. 7 VIEW HISTORY USE CASE DESCRIPTION .....................................................................................38
TABLE 3. 8 VIEW APPOINTMENT USE CASE DESCRIPTION ..........................................................................39
TABLE 3. 9 VIEW MESSAGE USE CASE DESCRIPTION ....................................................................................40
TABLE 3. 10 MAKE APPOINTMENT USE CASE DESCRIPTION .......................................................................41
TABLE 3. 11 SEND MESSAGE USE CASE DESCRIPTION ..................................................................................42
TABLE 3. 12 DELETE HP USE CASE DESCRIPTION ...........................................................................................44
TABLE 3. 13 UPDATE HP USE CASE DESCRIPTION ..........................................................................................45

TABLE 4. 1 ACCESS CONTROL AND SECURITY CONTROL ......................................................................73

vii
 List of Anonyms and Abbreviations
1. GUI --------------------------------------------------------- Graphical User Interface
2. HP ----------------------------------------------------------- Health Professional
3. PW ---------------------------------------------------------- Pregnant Woman
4. PWs ---------------------------------------------------------- Pregnant Women
5. ABACS -------------------------------------------------- Android Based Antenatal Care System
6. OOP --------------------------------------------------------- Object Oriented Programming
7. HC ----------------------------------------------------------- Health Centers
8. DB ----------------------------------------------------------- Data Base

viii
 Abstract
This project Mobile phone usage for maternal mother has proliferated in recent years. Few
places worldwide people are enjoying speedy utilization mobile phone. Women appear to be
taking the lead when it comes to smart phone technology, phone use when compared with men.
Mobile phones apps make participation possible for women to access the health care they need,
including family planning, birth, child care, and survival. Our documentation begins with
handling the data of pregnant woman in the health institution and the usage of smart phone apps
and its role in the everyday life of the pregnant women. The overall result of the study reveals
that, any maternal mother has to see her health status every weeks of her pregnancy life.

ix
 CHAPTER ONE

1 Introduction
Today in health institutions, Antenatal Care system requires keeping of data for pregnant
women. And these data are very vital information needed by the institutions for efficient and
effective work.

An Antenatal care system works on treating maternal mothers in a safe way and taking an
information from them, recording laboratory examinations, and making medical decisions in
health institutions, and this helps to take care of risk that occurs during and after giving birth.
This helps the women to have full confidence in her and her baby’s health status.

Our project works with design and implementation of a computerized Antenatal care system. The
system is expected to treat pregnant woman, provide necessary information for mothers using
their own smart phones and for health professionals using a computer. The information that will
be provided to maternal mother is her weakly status that she had to get it by going to health
institution. In general, the aim of this project is producing software that matches a client-side an
android based mobile application for maternal mother and in server-side a web-based application
for health professional in health institution.

The system that we are going to develop also helps the health professionals by providing an
information based on the submitted data that the pregnant woman will submit. This leads the
health profession to think in a best way, because the system gives him every possibility that may
occurs on baby or mother, because of the data that the pregnant woman submitted. With this both
the health professions and the maternal mother will be benefited during pregnancy time and
giving birth time. Therefore, we think that our system is very useful for the Health institution as
well as for the pregnant woman.

10
1.1 Background of the study

Today, mobile phones are familiar with our day today life. We don’t only use them for simply
calling or texting but in many other aspects. This document is the report of software requirement
specification for android based antenatal care system for maternal mother and doctors.

Technology has been a core player in helping to improving healthcare, by reducing costs,
improving patient safety and satisfaction, saving time and effort for both patients and clinics, and
reducing potential errors. In recent years, mobile technology in particular has greatly evolved
and become a mature platform, and according to CBS (Columbia Broadcasting System) News,
there are around 4.6 billion mobile phones worldwide. Because of this, many health
organizations such as the World Health Organization and experts from across the healthcare
industry are looking to tap into the potential of mobile technology to revolutionize healthcare
management and delivery[1]

Worldwide, concerted efforts are made to stimulate the use of information and communication
technology (ICT) in health care[2]. Healthcare systems are increasingly using technologies to
provide better services with less financial and human resources. The use of mobile technologies
for health has been less documented so far. In this article we are discussing this issue by
assessing the current state of knowledge on how maternal mothers use mobile based Antenatal
care system in Ethiopia.

In most area of Ethiopia, since it is not learned to use mobile phone for checking their health
status and simplifying ways for health care system, we get that preparing such flexible
application is very useful. In our case, we are going to do for all pregnant women to use their
smart phone for check their and their baby’s health status online. In Ethiopia the levels of
maternal and infant mortality are among the highest in the world. [3] This is due to most of
health centers did not use modern antenatal care system. Therefore, the objective of this project
is to reduce the death and the health problem that happens during pregnancy time in our country
Ethiopia. Currently in developing countries; Hospital, Health Center and family doctor are not
near to patient and pregnant women; because of this, especially pregnant women will face
bleeding, breech presentation; blood pressure, premature birth, death of children and mother.

11
1.2 Statement of the problem

In the existing system there are a lot of problem that faces the pregnant women, health
professional and health institutions. Most of the time because of high number of patients and
pregnant women in health institutions, PWs may fail to be visited by health professional; this
leads them to feel like they are violated or ignored by health professional and this make them to
be hearted psychologically. Therefor most pregnant women, to protect themselves from being
hearted psychologically they leave their home early and they will spend their time in health
institution. This affects their day today activities. Even those maternal mothers, who have
potential to pay too much many and wants to be checked their and their baby’s health status may
face financial problem.

The other problem that face maternal mothers is because of their home’s is very away from the
health centers, they may not get service on time and this leads for death of mothers and child’s.
also because of lack of knowledge of some specific symptoms and measures that have to be
taken for that they will face difficulties that may lead up to abortion. Missing appointment day
are some are the problems that will face during pregnancy time.

Also, there are problems that will face the health institution in recent time, one of this problem
is: - record is placed in paper and knowing the exact place of the paper is also difficult and time
killing.

In the existing systems there are ready questions that the health professionals has to ask his
patient when she comes to health institution, but sometimes because of time or tiredness, the
health professional may not be able to ask every detail not even necessary question and this led
to imperfect treatment of the patient.

1.3 Objective of the project

1.3.1 General Objective
The main objective of this project is to design and implement an Android Based
Antenatal Care System

1.3.2 Specific Objective

The specific objective of this project is achieving the general objective. We listed the
following aspects as specific objective

12
Objective 1: - Generating weekly symptoms for pregnant woman

Objective 2: -Generating an advice for pregnant woman to take care of her and her baby’s
. health status.

Objective 3: - To generate help reference (recommendation) for the HP, when any PWs submits
. her weekly health status

Objective 4: - To allow communication between PWs and HPs at any time without limitation.

Objective 5: - To give brief advice about symptoms

Objective 6: -Studying the background of the organization of antenatal care system

Objective 7: -Identifying the high-risk problem in the existing system

Objective 8: -Propose a solution for the problem in the existing system

Objective 9: -Develop an online database system for ABACS.

Objective 10: -To develop an interactive (GUI) android based mobile application for maternal
. mother in which they will communicate their weekly health status.

Objective 11: -Helping the health institute by preparing online control mechanism for the health
. professional specifically for those who works on maternal mother care (i.e. maternal
. case specialists, doctors, midwifery, receptionist, nurse)

1.4 Significance of the project

Generally, the result expected after implementation of these project are the following:
❖ Best and appropriate care and follow up for pregnant women.
❖ Minimizing the death and lifelong health problem resulted because of pregnancy
❖ Avoiding stress and worries of mothers that comes during pregnancy time and
giving birth time
❖ Giving simplified and easy maternal mothers information record system.
❖ Giving equal treatment for all maternal mothers
❖ To decrease infant mortality and death of mothers and baby
❖ To teach and give an advice for mothers about child care, nutrition, sanitation and
hygiene
13
 ❖ Supporting health professional for better decision making

1.5 Scope of the project

This project is about using a mobile phone in the case of pregnancy for maternal mother
to communicating with HPs about their daily health status. The communication is
expected to be very simple using a single android-based mobile application consisting of
checklist with symptom names that is separated with weekly progresses, that may occur
at a specific time in the prenatal period. This page is generated by the system according
to the prenatal period of the women. Each pregnant woman checks her status of sign and
symptoms based on the checkbox listed followed by symptom names and after checking
she will submit the data online. The submitted data will be available at the health
institution side with analysis made by the system.
The responsible health professional at the health institution side makes decision based on
the checklist submitted and the analysis provided by the system. The decision includes
• Making an appointment
• Telling her to go to the nearby health institution for vital sign check-up
• An emergency message for a fast reaction
The women will receive an information specific to her status using a instant message, for
advice or an appointment and a call for an emergency case.
In the health institution when a pregnant woman goes for her first visitation she will be
registered to the system. Then after registration the system enables communication
between health professional and pregnant women. The process starts when a woman is
identified to be pregnancy and ends after delivery.
The main motto of this project is “Underdeveloped should not be excuse for maternal
death and health problem”.

1.6 Limitation of the study

Limitations in our projects are as follows: -

✓ Users must have smart phone to use the system because the system only works
on android platform.
✓ Users must have knowledge of how to use smart phones.

14
 ✓ System needs internet accessibility therefore users of the system must be in the
network area.
✓ Do not take direct laboratory examination such as ultrasound and Blood
Pressure.

1.7 Methodology
Methodology refers to a standard process followed by the development team to conduct all the
steps necessary to planning, analyze, design, implement, and maintain the proposed system.

We are going to use agile system development Approach for this purpose. This approach divides
the entire project into small projects and assign time for divided projects. we have selected Agile
method for the following advantages.[4]

➢ High product quality

➢ Higher customer satisfaction
➢ Increased project control
➢ Reduced risks
➢ Faster ROI (return on investment)

1.7.1 Data collection methodology

As we know gathering information and collecting data is an essential thing in order to

develop a good system or a project. Therefore, we used the best methods that make our
project very nice. And relevant methods that we used are as follows: -
Interview: - we used this to get the basic background information about the existing
system and problems that occurs in the existing system. As well as futures that has to
be done on the system in order to make it very nice and easy for both the pregnant
women and health profession. To do this the team members has been interviewing the
health professional and pregnant women.
Observation: We have got information by going to the health center physically
and by observing how the health professional treat the pregnant women.
Observation allows us to collect data in real time where activities are being
performed
Online: - -it is our major source to gather information for our project. Also, we
have been watching tutorials online about how the android system works.

15
 Document and records: - We have gotten relevant information and collected
data from different written documents to develop our project.
Focus group: - Our team member raises an idea and discusses issues that were
raised during our meeting time.

1.7.2 System analysis and Design methodology

For our project we used Unified Modeling language (UML). The primary goals in the
design of the UML is as follows[5]:
✓ Provide users with a ready-to-use, expressive visual modeling language so they
can develop and exchange meaningful models.
✓ Provide extensibility and specialization mechanisms to extend the core concepts.
✓ Be independent of particular programming languages and development
processes.
✓ Provide a formal basis for understanding the modeling language.
✓ Encourage the growth of the object-oriented tools market.
✓ Support higher-level development concepts such as collaborations, frameworks,
patterns and components.
✓ Integrate best practices.
✓ It enables to reduce the communication gap between user and designer.
✓ In case of our project we have used about four UML diagrams (i.e. Class
diagram, Use case diagram, sequence diagram, and activity diagram).

1.7.3 System implementation

Now a days there are two most commonly used coding approaches these are: - Object
Oriented Programming and Procedural Programming approach. From these two
approaches our team chooses to use object-oriented programming (OOP) approach. The
reasons that we choose this approach are as follows[6]: -
1. Encapsulation: - Objects created in OOPs are able to hide certain parts of code from
programmer. This prevents unintentional modification in the code which may cause
unwanted outcomes.
2. Code Reuse: - Objects created in OOPs can easily be reused in other programs.
3. Software Maintenance: - Code written in OOPs is easy to debug and maintain.

16
 4. Design Benefits: - OOPs needs extensive design planning which certainly provide
design benefits over traditional style.

1.7.4 Testing and deployment methodology

• Testing methodology: - System testing uses to measure the overall performance of the
system. From the different types of testing, we use unit testing, integration testing, and
functional testing.
֎ Unit testing: - uses in order to test the design that validate the internal program logic is
functioning properly or not. It is done by a developer. And in our project, we are going
to use this type of testing in order to test the following functionalities.
1. Check if the receptionist that help the pregnant woman, or the pregnant woman
herself: -
▪ Enters valid or invalid HCs password to sing up
▪ The signup password field is empty or not before entering to the system
for new mothers.
▪ The “Registration” button is clicked or not
2. Check if the pregnant woman clicks the “not new” button or not
3. Check if the maternal mothers
▪ In Loin page
o Enters valid user name and password
o If login fields are empty or not
o If “login” button is clicked or not
o If “Forgot Password” button is clicked or not
▪ In Registration Form
o Check if the maternal mother fills valid input of every requirement
of the fields
o Check if the fields are filled or not
o Check if the registration button is clicked or not
4. Check if the HPs enter valid inputs during login, search for a maternal mother, give
appointment and such like this requirement

17
 5. In an Admin side we are also going to use this type of testing, when an admin needs:
- to search for HP, register HP and for some other requirements that need to be
checked by unit testing.
֎ Integration testing: - After unit testing is done then integration testing will be
continued or integration testing takes place after unit testing and before validation
tasting is takes place [7]. In our case after the integration testing is done by the system
before the specific HCs takes the developed system it will be checked by testers. And we
are going to use integration testing in the following cases: -
1. After successful insertion of HCs password, did the pregnant woman pass to
the Registration form or if she enters “not new” button, can she proceed to the
logging page?
2. After successful insertion of user name and password of the PW, HP or Admin,
can they pass to the Home page successfully?
3. In case of maternal mother can she proceed from: -
✓ Home page to view symptom page successfully
✓ Home page to view appointment page successfully
✓ Home page to view symptom page successfully
✓ Home page to view advice page successfully
✓ Home page to search symptom page successfully
4. After submitting the symptoms will the data be saved to DB
5. Are the search buttons are working correctly for PW, HP and Admin?
֎ Data sets: -uses in order to test our systems fields are entirely work properly, validates
user account, make system to response on time, and controls error.
• Deployment methodology: - after testing is done our system will be first deployed as
an additional feature to the manual system, which means everything that the current
system is using will be as it is (i.e. PWs or health professionals will use the manual
system). After a certain period of time or when the health professionals and the
receptionist learn the new system, they will proceed using the new system. When the
development team feels comfort about the new system, they can fully replace the manual
system. Then our system will be fully deployed.

18
1.8 Development environment

Hardware and Software tools that we have been using for our project are listed below
with their respective significance.

Table1. 1 hardware tools

No. Hardware Tools Description

1. Personal Computer We used this for keeping backup and recovery of all
data that we have been using during developing time.

2. USB Flash (8GB) We use this to send and receive documents from one
computer to another computer.

3. External Hard Disk 1000 GB We use this to store our data and for backup

4. Paper We used this to take notes during data collection

Table1. 2 software tools

NO. Software tools Description

1. Microsoft office we used this to write documentation of our project
2010

2. Edraw Max We used this to draw diagram such as class, sequence, activity,
collaboration, use case and state chart diagram

3. Windows Operating Windows 10 operating system

System

4. XAMPP server we used this as a database engine for creating and manipulating
data.

5. GenyMotion We used this application to test the product.

6. Microsoft Visio We used this to draw Gantt chart

2016

7. Android studio 3.2.1 We used this write and run the code

19
 8. SDK This software enables us to create application for the Android
platform. The android SDK include sample projects with source
code, development tools, an emulator, and required libraries to
build Android applications.

9. Mendeley Desktop We used Mendeley desktop application to show the references

1.9 System requirement

System requirement that our system need is: -
✓ For Pregnant Woman it is needed only to be smart phone.
✓ For Admin and Health professions any Computer that can run internet browser
(i.e. Laptop or desktop)

1.10 Feasibility study

1.10.1 Technical feasibility

Almost all of the required hardware and software for developing our project is available
in our university, and all our group members performed their own duties perfectly
therefore we can say our project is technically feasible. The newly developed system
performs each and every activity easily and technically. Especially in server side using
the system did not require being a doctor or maternal case specialist, simply any health
professional can work efficiently. Also, in client side any pregnant women can submit her
data with a short training. Since all health professionals and pregnant women use the
system simply without confusion, we can say the system is technically feasible.

1.10.2 Operational feasibility

We can say our project is operationally feasible because: - Operational feasibility

identifies whether the current work practices and procedures are adequate to support new
system. The existed system works traditionally by papers and exercise books but the new
system works using an android based smart phones in which almost all people can handle
it every time and everywhere they move. Also, it can be easily operated and accessed by
the users who are familiar with the usage of smart phone. It contains Graphical User
Interface (GUI) which leads users to interact with the system interfaces.

20
1.10.3 Economic feasibility

The system to be developed is economically feasible and the benefit is outweighing the
cost because this project computerizes the existing system. Also, it works on reduction of
cost that is played for manual operations such as paper and pens.
Generally, the system that we developed brought a number of tangible and intangible
benefits.
Tangible benefits:
1. Time and Cost Reduction
2. Error Reduction
3. Increase Speed of activity
4. Lowering payment processing

Intangible benefits: -
1. Accurate and faster access data for timely decision
2. Improved customer response
3. Makes the customer more satisfied
4. Increase speed service for the customer
5. Knowledge gained by project developer
Tangible cost
Tangible cost is a cost that is seen instantly such as in purchasing products. The tangible
costs to be acquired in developing the system are: -
❖ Software development cost
❖ Hardware development cost

Table1. 3 Tangible cost

Potential cost Quantity Unit price (in Total

NO. birr) price
Transportation - 150 150
1.
Pen 5 6 30
2.
Paper 1 packet 160 160
3.

21
 Note Books 2 15 30
4.
External Hard Disk 1 2700 2700
5.
USB Flash 8GB 1 250 250
6.
Total cost - - 3,320
7.

1.11 Time scheduling

The below figure (Gantt chart) illustrates the word break down tentative initial project
schedule to as follows.

Table1. 4 Time scheduling

22
 CHAPTER TWO

2 DESCRIPTION OF EXISTING SYSTEM

2.1 Introduction
The existing system, that currently the health centers using is manual system. Which means on
paper-based manner? In the current system when a new maternal mother comes to the health
institution, first she will go to reception office and be registered by the receptionist, then she will
wait until her queue. The information of the previous and new coming customers is recorded on
the paper and placed on the shelf. If the health professional needs to know any information about
specific pregnant woman he/she has to ask the receptionist and the receptionist has to refer all the
papers that are placed on the shelf and give to the health professional. And in case of registration
when pregnant woman’s goes to specific health institution for the first time, she has to be
registered by going to reception room and told to the receptionist all her data. Then after
registration takes place the pregnant woman’s data will go to store and putted on the shelf. after
that when the health professional starts to visit pregnant women one of reception class workers
give data of pregnant woman that are registered, after that the health professional starts visiting
every pregnant woman. Also, if any appointment, registration or scheduling time is needed for
the customers, this is also done by papers. Since all of these steps are done manually and any
pregnant woman needs to visit the particular health institution to take an appointment and to
know about her current health status, she must have to go to the health institution in order to
know about all the decisions made by the doctor or if there is any further appointment that she
needs to follow.

Also, every pregnant woman will get any treatment by waiting the doctor until he/ she finishes
treating another woman, which means every pregnant woman waste their time or couple of days
to get the service.

2.2 Strength of the existing system

As we known the existing system is not good or satisfiable therefore almost it has very small
strength. These strengths are: -

✓ The health professional visit or check the pregnant women physically

23
 ✓ No need of knowing technologies (i.e. knowledge of how to use android based
mobiles or smartphones) to be visited
✓ The pregnant woman may describe her feelings without limited words
✓ It is applicable without internet connection because communication between the
health professional and the pregnant woman undergoes not between instruments but
physically.
✓ It is accessible for both who lives in the area of network coverage and for those who
are not living in an internet connection area.

2.3 Weakness of the existing system

The main weakness of the existing system is: -
Cost: -
✓ Cost that pregnant women will pay for transport
✓ Cost that she will pay for fast food when she waits for a service for a long period
of time, she may need to eat so pay for that.
Time: -
✓ Time wasted because of waiting the health professional until finishes giving
service to another women,
✓ Time wasted because of searching previous records of pregnant woman

Labor: -

✓ During searching for customers information from shelf or another place.

Loose of data: -
✓ data may be lost because of many reasons: - such as suddenly fires, putting data on
paper for long period of time, forgetting files where they are putted and so on …

2.4 Proposed system description

The proposed system that we are going to develop is an android based application which will
perform every activity in a computerized way. Activities that will be performed by the new
systems are registration, taking information or data of the pregnant woman, writing laboratory
examination results on secured database, fast responses for emergency cases, pre-knowledge
about the woman for health professional.

Also, the main aim of the proposed application is:

24
❖ To reduce human errors by providing user-friendly input and output capabilities and
record keeping.
❖ To store data into database so, it can be easily accessed and used at any time.
❖ To provide security of data.
❖ To store data for years, decades or above because it is stored in database rather than
on the paper.

25
 CHAPTER THREE

3 SYSTEM FEATURES
3.1 Introduction
In this section we are going to explain the functional and non-functional requirements of the proposed
system, because in system analysis phase the document that stated describes the functionalities of
the system in terms of use case from the user’s point of view and how the analysis models are
designed by health professional and by the system to develop an android based Antenatal Care
System. But also, in the design phase those functionalities of the system are decomposed into
smaller sub systems to easily handle by the developer.

3.2 Functional requirements

These requirements are basic for the new system or simply the system must satisfy functions that
we are going to describe below. This requirements stress functionality that the system should
support for all of the users of this system such as direct or indirect relationship between the
system and users, the environment of the system. So, the system is able to do many things in
pregnant side, health professional side and admin side. These functions include: -
For the pregnant women

➢ Signup: - pregnant women must be registered by the help of receptionist, when she visits
the Health centers for the first time.
➢ Login: - in order to use the application every pregnant woman must have to login into the
system.
➢ View Appointment: - she has to see an appointment that had been decided by the health
profession.
➢ View Message: - when the health professional sends a message for the woman, she has to
read a message using the application.
➢ View symptoms: - the application should give the required weekly symptoms when the
woman is in need of getting information.
➢ View advice: - when the pregnant women submit the data, the system should provide an
advice based on the data that she had submitted. Then the woman should get that advice
from the application.

26
➢ Search symptoms: - sometimes when she is in need of specific information about specific
symptoms, she can search by inserting the name of the symptom, so she will get detailed
information about the symptom.

For Health professional

➢ Login: - the health professionals, after registered by the admin he/ she must have to login to
the system to perform their activities.
➢ Search Pregnant Woman by ID: - to get specific data of the woman first he/ she have to
search the woman by using their ID.
➢ View History: - after he gets the data of specific woman the system must provide all of the
detailed information about the woman from database. Then he/ she can view history of the
pregnant woman.
➢ Send message: - after viewing the data of the pregnant woman the he/ she can send a
message to the specific pregnant woman if it is necessary.
➢ Make an Appointment: - when it is necessary, he/ she should have to make an appointment
to the woman’s depending on the information that he/ she get from the database.
➢ Update Appointment: -when there is need of making an appointment for second or third
time or above, then he/ she have to update the previous appointment.
➢ Change Password: - if the HP needs to change his/ her password he/ she can easily change
the old password with the new one.
For Admin
➢ Register HP: - the system will allow for admin to register the health professional in order to
be an employee of particular health centers.
➢ Update HP: - when there is need of changing the status of health professionals (for example
if the health professional forgets either username or password) the admin will update health
professional’s account.
➢ Delete HP: - when the health professional leaves the health center the admin will delete
him/her account from data base.
➢ Change Password: - if the admin needs to change his/ her password he/ she can easily
change the old password with the new one.

27
3.3 Non-functional requirements
These requirements are supporters of the main functional requirements of the system listed
above. The new system that we are going to develop includes those requirements to reflect the
quality of the system such as GUI, reliability, performance, portability, error handling, integrity,
maintenance, security, simplicity, backup and recovery.
➢ GUI: - by including readable and simply viewable check box, labels, text area and
different buttons, the users of the system will get service friendly pages which are very
simple to work.
➢ Reliability: -we can say that the newly developed system is reliable because its data are
stored in a database and the system pass the data that submitted by the pregnant woman
to the HP exactly as she submitted.
➢ Performance: - The designed system can process and retrieve the required information
from the database. Also, the utilization of resources in terms of time is minimized.
➢ Portability: - we can say the system is portable. Because after developing the
application it will work in any smart mobile phones so when anybody needs to get the
application, they can simply get by using Bluetooth, xender or any wireless sharing
applications.
➢ Error Handling: - when the user registers, login, search for specific pregnant woman in
case of HP or searches for specific symptoms in case of PWs, there may be resulted an
error due to an incorrect input. So that the system will handle the error and it will display
different error messages that tells about the error.
➢ Integrity: Only the admin can delete, update or modify health professional’s account.
Access is denied for all other users of the system.
➢ Maintenance: when the users wants additional functionalities from the system
throughout time, there may be need of changes to the system. When the administrator of
the system identifies that features depending on the organization’s needs, he/she may
modify it.
➢ Security: - only the authenticated users have a privilege to access the system. and all
users of the system have their own user name and password so they must enter correct
username and password. Therefore, the proposed system is secured. [8]
✓ Java Authentication and Authorization Service (JAAS): - is a set of APIs that
enable services to authenticate and enforce access controls upon user

28
 ✓ Encryption: - is the process of encoding a message or information in such a way
that only authorized parties can access it and those who are not authorized cannot.

➢ Simplicity: - we can say that the proposed system applies simplicity because it
simplifies the work of health professionals as well as well as the admin. Also, it
simplifies time for the pregnant woman that she was wasting to get the service and to be
visited by HP, she must go physically.
➢ Backup and Recovery: - since all of user’s data are recorded in a database and the
recorded data are stored online, bad conditions that happen will not destroy any data like
fire, and earthquake. Therefore, we can say that the newly developed system has a
protected backup and recovery.

3.4 Analysis and modeling

3.4.1 Introduction
A system use case model is composed of a use case diagram and the accompanying documentation
describing the use cases, actors, and associations. System use cases reflect analysis decisions and,
arguably, even design decisions.

3.4.2 Use case model

The use case model for the proposed system will have the following components: -
➢ Actor: in our systems there three actors, these are the pregnant woman, the health
professional and the admin. We selected actors according to the following definition it is
a person, external system that play one or more role in interacting with the system. And it
represents with stick figures

Pregnant Woman

Health Professional

Admin

Figure 3. 1 representation of actor

Use case: - in newly developed system there are many use cases such as view symptoms, make
decision, register HP … and we find all of the use cases from the definition of use case which
says - it describes a sequence of action that provides a measurable value to an actor and draw as a
horizontal ellipse. [9]

29
 Figure 3. 2 representation of use case
➢ System boundary: indicates the scope of the system project, anything within the
system boundary that represents functionality of the system.

Figure 3. 3 representation of system boundary

Actor Identification: actor of our systems are as follows: -

➢ Pregnant women
➢ Health Professional
➢ Admin

Use case identification: use case of our system are as follows.

1. Login
2. Signup
3. View Symptoms
4. View Advice
5. View Message
6. Search Symptoms
7. Logout
8. Search Pregnant Women by Id
9. View History
10. View Appointment
11. View Advice
12. Make Appointment
13. Update Appointment

30
 14. Send Message
15. Change password
16. Register HP and receptionist
17. Delete HP and receptionist
18. Update HP and receptionist

3.4.3 Use case diagram

Figure 3. 4 representation of use case diagram

31
 3.4.4 Use case descriptions
Use case name: Login

Table 3. 1 login use case description

Use case name Login

Use case Id SCU-001

Actor Pregnant Women, Health Professional, Admin

Description This use case is to authenticate the user

Precondition First the user must be registered on the system, then he/she must have
a username and password.

Post condition A home page is opened for the user

Basic Course of action Actor action System response

Step 1: the user loads the Step 2: the system displays login
system. page to the user.

Step 3: the user enters username Step 5: The system checks if the
and password username and password is
available, then verifies the user is
Step 4: user click login button. authenticated and authorized.

Step 6: the system displays home

page.

Step 7: end use case

Alternative course of (If the username and password are incorrect)

action 1, The system displays a message “incorrect username and password”
to the user.

2, The system redirect goes to step 3 i.e. to enter username and

password

32
Use case name: Signup

Table 3. 2 signup use case description

Use case name Signup

Use case Id SUC-002

Actor Pregnant Women, Admin

Description Creates a new account for the user of the system.

Pre-condition The user must be either an Admin or a pregnant woman and he/she
must have an internet access (WIFI or cellular data).

Post condition The user login into the system.

Basic course of action Actor action system response

Step 1: the user loads to the Step 2: the system displays login page
system. with Signup button to the user.

Step 3: the user clicks the Step 4: the system displays registration
Signup button. page to the user.

Step 5: The user fills the Step 6: The system checks whether the
necessary form and click form filled are filled correctly or not.
submit button.
Step 7: the system display message
“registration successfully” to the user.

Step 8: end use case.

Alternative course of 1, If the registered user exists in the database, the system displays

33
action message “user name and password already exist” to the user.

2, if the input data has errored the system display error message and
allow the user to try again.

3, Then, the system redirects to go to step 5

Use case name: View Symptoms

Table 3. 3 View Symptoms use case description

Use case name View Symptoms

Use case Id SUC-004

Actor Pregnant Women

Description The user views symptoms that are generated from a database using
checklist.

Pre-condition First the user must be login into the system and she should have to
open the home page of the system.

Post condition The user will access or view symptoms that contain weakly
categorizing different button option such as weak 4, weak
5…………weak41.

Basic course of action Actor action System response

Step 1: the user loads to the Step 3: the system displays home page
system to the user.

Step 2: the user login into Step 5: the system displays weakly
the system. status menu item options to the user.

34
 Step 4: the user selects or Step 7: the system displays different
click view symptoms menu checklist with the name of symptoms
item. and one text area to write another
symptom that is not presented in the
Step 6: the user selects one
checklist.
among different weakly
status menu item option, i.e. Step 9: the system saves the submitted
depending on the prenatal data to the database. then the system
period of the women. display message “data submitted
successfully” to the user.
Step 8: the user selects or
tick checkbox if the Step 10: end of use case
symptoms in front of the
check box are matched with
the user feeling, or writes
the name of symptom that is
not inside of the checklist,
then she clicks submit
button.

Use case name: View Advice

Table 3. 4 View Advice use case description

Use case name View Advice

Use case Id SUS-005

Actor Pregnant women, health professional

Description The pregnant women will see advice which is generated by the system
based on the submitted information. This is done after the she submitted
the data.

35
Pre-condition The pregnant women must submit data into the system.

Post condition The pregnant women will see an advice. Such as go to nearby health
institution, eat special kind foods, call to the doctor.

Basic course of Actor action System response

action

Step 1: the user loads to the system. Step 3: the system display Home
Page to the user.
Step 2: the user login into the system.
Step 5: the system displays
Step 4: the user selects or clicks View
different weakly status menu
symptoms menu item.
item option to the user.
Step 6: the user selects one among
Step 7: the system displays
different weakly status option button.
checklists that is clicked by the
Step 8: the user selects or tick user.
checkbox if the symptoms in front of
Step 9: the system saves the
the check box are matched with the
submitted data to the database;
user feeling, or writes the name of
then the system display message
symptom that is not inside of the
“data submitted successfully” to
checklist; then she clicks submit
the user.
button.
Step 10: the system gives an
Step 11: the user will see an advice that
advice to the women based on
is generated by the system.
the information she submitted.

Step 12: use case end

36
Use case name: Search Symptoms

Table 3. 5 Search use case description

Use name Search

Use case Id SUC-006

Actor Pregnant Women, health professional

Description The pregnant women will search every symptom that she is feeling at
the time of searching, by using either symptoms name or ID. And the
health professional will search pregnant women, those who started
visiting in the institution.

Pre-condition The must login into the system.

Post condition The pregnant women should get information about the symptom. And
in health professional side they should get history of the pregnant
women.

Basic course of action Actor action System response

Step 1: the user loads to the Step 3: the system displays the home
system. page to the user.

Step 2: he/she will login to the Step 5: The system checks if the
system. entries are presented or not in the
database
Step 4: The pregnant women
enters the name of the Step 6: The system displays the
symptoms and the health result that it gets from the database.
professional enters the ID of
Step 8: end use case
the women.

Step 7: the user will get

information that he/she was

37
 searching for.

Alternative course of If the entries are not found in the database.

action
1, the system tells to the user the result is not found.

Use case name: View History

Table 3. 6 view history use case description

Use case name View History

Use case Id SUC-007

Actor Health Professional

Description The Health professionals will view the previous information about
the pregnant woman.

Pre-condition The user must login to the system.

Post conduction He /She will see the previous history of the pregnant woman.

Basic course of action Actor action System response

Step 1: The user loads the Step 3: the system displays

system Database of the pregnant woman.

Step 2: He/ She login to the Step 5: end use case.

system.

Step 4: He /She will see

detailed history of the woman.

38
Use case name: View Appointment

Table 3. 7 View Appointment use case description

Use case name View Appointment

Use case Id SUC-008

Actor Pregnant Women

Description The pregnant women see an appointment when she clicks ‘check
an appointment’ button

Pre-condition First the health professional has to send an appointment to her

then she has to login to the system.

Post condition The pregnant women will see her appointment.

Basic course of action Actor action System response

Step 1: the user loads to the Step 3: the system displays

system. Home Page.

Step 2: the user login into the Step 5: the system check
system. whether or not she has an
appointment.
Step 4: the user selects or
click the Check Appointment Step 6: the system shows the
button. appointment date if it exists or
displays “No Appointment” if
Step 7: the user can view the
not exist for the pregnant
appointment that the health
women.
professional sends for the
pregnant women.

39
Use case name: View Message

Table 3. 8 View Message use case description

Use case name View Message

Use case Id SUC-009

Actor Pregnant Women

Description The pregnant women see a message when she clicks ‘check a
message’ button

Pre-condition First the health professional has to send message to her then she
has to login to the system.

Post condition The pregnant women will see her message.

Basic course of action Actor action System response

Step 1: the user loads to the Step 3: the system displays

system. Home Page.

Step 2: the user login into the Step 5: the system check
system. whether or not she has message.

Step 4: the user selects or Step 6: the system shows the

click the view message message if it exists or displays
button. “No message” for the pregnant
women if not exist.
Step 7: the user can view the
message that the health

40
 professional sends for the
pregnant women.

Use case name: Make Appointment

Table 3. 9 Make Appointment use case description

Use case name Make Appointment

Use case Id SUC-010

Actor Health Professional

Description The health professional will make an appointment.

Pre-condition The Health Professional must login into the system and see
information from a database that stored during submission of the
symptoms.

Post condition The Health Professional will make appointment for the pregnant
women.

Basic course of action Actor action System response

41
 Step 1: The Health Step :3 the system displays
Professional loads the system. database.

Step 2: He/ She login into the Step 5: the system checks if the
system. inserted id is correct and present

Step 4: He/ She searches for a Step 6: The system displays the
Pregnant woman search result to the Health
Professional.
Step 7: He/ She click on
specific name of the pregnant Step 8: The system displays data of
woman. pregnant woman and three buttons
(i.e. Send Message, Make
Step 9: He/ She selects on
Appointment, Make Decision).
‘make appointment’ button
Step 10: The system displays popup
window which contain a text area
Step 11: He/ She will make and send button
an appointment for specific
Step 12: the system sends an
woman depending on the
appointment to the woman.
result displayed.
Step 13: end use case.

Alternative course of If the Health Professional did not input correct ID of the woman
action
1. The system displays “you inserted Incorrect ID” to the
Health Professional
2. And it redirects to step 4

Use case name: Send Message

Table 3. 10 Send Message use case description

Use case name Send Message

42
Use case Id SUC-011

Actor Health Professional

Description The health professional will send message.

Pre-condition The Health Professional must login into the system and see
information from a database that stored during submission of the
symptoms.

Post condition The Health Professional will send message for the pregnant women.

Basic course of action Actor action System response

Step 1: The Health Step 3: the system displays

Professional loads the system. database.

Step 2: He/ She login into the Step 5: the system checks if the
system. inserted id is correct and present

Step 4: He/ She searches for a Step 6: The system displays the
Pregnant woman by id. search result to the Health
Professional.
Step 7: He/ She click on
specific name of the pregnant Step 8: The system displays data of
woman. pregnant woman and three buttons
(i.e. Send Message, Make
Step 9: He/ She selects on
Appointment, Make Decision).
‘send message’ button
Step 10: The system displays popup
window which contain a text area
Step 11: He/ She will send and send button
message for specific woman
Step 12: the system sends message
depending on the result
to the woman.
displayed.

43
 . Step 13: end use case.

Alternative course of If the Health Professional did not input correct ID of the woman
action
3. The system displays “you inserted Incorrect ID” to the
Health Professional
4. And it redirects to step 4

Use case name: Delete HP

Table 3. 11 Delete HP use case description

Use name Delete user

Use case Id SUC-012

Actor Admin

Description This use case describes remove unwanted user.

Pre-condition The admin must login in to the system.

Post condition The user must available in the database.

Basic course of action Actor action System response

Step 1: Admin login to the Step 2: the system display home to

system the admin.

Step 3: The Admin click on Step 4: the system displays the

manage account menu item. manage page.

Step 5: admin select and click Step 6: the system displays the
on delete account menu. delete account form.

Step 7: Admin fill the deleted Step 8: the system will check the
account user and click delete input.
button.
Step 9: the system display message

44
 “the selected account is
successfully deleted”

Alternative course of (If the information is not valid the system will display the error
action message)

1, It redirects to step 7

Use case name: Update HP

Table 3. 12 Update HP use case description

Use name Update HP

Use case Id SUC-013

Actor Admin

Description This use case allows the Administrator to update user account when
the account is needed to update.

Pre-condition The admin must login in to the system.

Post condition If this use case ends successfully, the user account is successfully
updated.

Basic course of action Actor action System response

Step 1: Admin login to the Step 2: the system display home to

system the admin.

Step 3: The Admin click on Step 4: the system displays the user
manage account menu item. account.

Step 5: admin select and click Step 6: the system displays the
on update account menu. update account form.

Step 7: Admin fill the required Step 8: the system will check the
field and click update account form element.
button.
Step 9: the system display message
“the select account is successfully

45
 updated”.

Alternative course of (If the information is not valid the system will display the error
action message)

1, It redirects to step 7

46
3.4.6 Sequence diagram
Sequence diagrams are used to formalize the behavior of the system and to visualize the
communication among objects. They are useful for identifying additional objects that participate
in the use cases. We call objects involved in a use case participating object. It represents the
interactions that take place among these objects

Figure 3. 5 Sequence Diagram for login

47
 Figure 3. 6 Sequence Diagram for Signup

Figure 3. 7 Sequence Diagram for View Symptoms

48
Figure 3. 8 Sequence diagram for View Advice

Figure 3. 9 Sequence diagram for Register HP

49
 Figure 3. 10 Sequence diagram for search

Figure 3. 11 Sequence diagram for make appointment

50
Figure 3. 12 sequence diagram for Change Password

Figure 3. 13 Sequence diagram for Send Message

51
Figure 3. 14 Sequence diagram View History

Figure 3. 15 Sequence diagram for Update HP

52
3.4.7 Activity diagram
• Activity diagram describes a system in terms of activities. These activities represent the
execution of a set of operations in this system. The completion of one activity operations
triggers a transition to another activity. Activity diagrams are similar to flowchart
diagrams which means that they can be used to represent control flow.

Figure 3. 16 Activity diagram for login

53
Figure 3. 17 Activity diagram for Signup

54
Figure 3. 18 Activity diagram for View Symptoms

55
Figure 3. 19 Activity diagram to Register HP

56
Figure 3. 20 Activity diagram for Search

57
Figure 3. 21 Activity diagram for View Appointment

58
Figure 3. 22 Activity diagram for View Message

59
Figure 3. 23 Activity diagram for View Advice

60
 Figure 3. 24 Activity Diagram for Send Message

Figure 3. 25 Activity diagram for Make Appointment

61
Figure 3. 26 Activity diagram for Update HP

62
 3.4.8 Analysis level Class diagram
Class diagrams show the static structure of the model, in particular, the things that exist (such as classes
and types), their internal structure, and their relationships to other things.

Figure 3. 27 class diagram

63
 CHAPTER FOUR

4 System Features
4.1 Introduction
In this section the application is described by defining the design goals of the project, by
decomposing the system into smaller subsystems that can be easily realized (proposed
application architecture) and by selecting strategies for building the application, such as the
hardware/software platform on which the application will run, the persistent data management
strategy and the handling of boundary conditions. The result of system design is a clear
description of each of these strategies, subsystem decomposition, and a deployment diagram
representing the hardware/software mapping of the system.
4.1.1 Purpose of the system Design Document (SDD)
The design goals represent the desired qualities the system should have and provide a consistent
set of criteria that would be taken into consideration when making design decisions. The
following are mentioned as the design goals of “Android based antenatal care system “
Security: the system should be secure to maintain data confidentiality. The system should
authenticate it’s users by prompting them to enter user name and password in order to get access
to the system.
Extensibility: the system should allow any additional services easily if needed, in other words it
should not be difficult to extend the system if additions are necessary
Availability: the system should be available every time the user needs to access it.
Usability: the system should have user friendly user interface to allow the user to interact with
the system easily.
Portability: the system should be able to run on any mobile that supports android mobile
applications.
Performance: the main performance measure for a project is time, so the system should give fast
responses for user requests.

64
4.3 Architectural Design
The proposed software has three- tier architecture.

• The presentation tier: is the top most level of the application. It is the one the clients
directly interacted. It provides GUI to allow the client gaining access of the system.

• Logical tier/ middle tier: It accepts inputs from the client and performs detailed
processing. It is a bridge between data access tier and presentation tier.

• Data access tier: provides data persistence mechanism and storage to the data. It consists
of a mechanism to access the database without installing data base dependent drivers and
libraries on the client device

4.3.1
Deployment View
Deployment diagrams show the configuration of run-time processing elements and the software
components, processes, and objects that live on them. Software component instances represent

65
run-time manifestations of code units.

Figure 4. 1 Deployment Diagram

66
4.4 Database Design
4.4.1 ER Diagram

Figure 4. 2 ER diagram

67
 HP _ID
Admin _ID
Pregnant _Woman _ID

➢
Admin
First _Name First _Name
First _Name
Last _Name Last _Name
Last _Name

Pregnant women
Health Professional
Educational _Status Educational
Email _Address
_Status
Phone _No
4.4.2 Relational Mapping

Position
Position
Address
Phone _No

Age Phone _No

Email _Address
Marital_Status Email

68
ANC_Reg_No _Address
Address

Reg_Date Address
➢ Admin_ID: primary key references the Admin entity

Gender
Medical_Record_No
Add Photograph Gender

➢ HP_ID: primary key references the Health Professional entity.

Number_of_Children
Experience of Work User _Name
DOB

User _Name ➢ Admin_ID: foreign key references the primary key of admin’s entity. User _Name
Password
Password Password
Confirm
Confirm _Password Confirm _Password
_Password

➢ Pregnant_Women_ID: primary key references the primary key Pregnant women entity.
Adin_ID
Appointment

Appointment_ID Appointment Appointment Appointment HP_ID Pregnant_Women_I

_Time _Date _Description D

➢ Appointment_ID: primary key references the primary key of Appointment entity.

➢ Pregnant_Women_ID: foreign key references the primary key Pregnant women entity.
➢ HP_ID: foreign key references the primary key Health Professional entity.

Message

Message_I Message Appointment Appointment HP_ID Pregnant_Women_ID

D _No _Date _Description

➢ Message_ID: primary key references the primary key of Appointment entity.

➢ Pregnant_Women_ID: foreign key references the primary key pregnant women entity.
➢ HP_ID: foreign key references the primary key Health Professional entity.

Symptoms

Symptom_ID Symptom_ Name Symptom Advice_For_Symptom Pregnant_Women_ID

_Description

Symptoms _ID: primary key references the Symptoms

➢ Pregnant_Women_ID: foreign key references the primary key pregnant women entity.

69
 History

Current_date_First_
Treatment_She_is_t

First_visiting_Date
Medicine_She_is_t

Last_visiting_Date

Appointment_ID
Name_of_nurse

Status_of_PW
Name_of_PW

Name_of_HP

Visiting_date

PW_ID

HP_ID
aking

aking
➢ PW_ID: foreign key references the primary key Pregnant women entity.
➢ HP_ID: foreign key references the primary key Health Professional entity.
➢ Appointment_ID: foreign key references the primary key Appointment entity.

4.4.3 Database Normalization

The main goal of Database Normalization is to restructure the logical data model of a database
to:
❖ Eliminate redundancy
❖ Organize data efficiently
❖ Reduce the potential for data anomalies.
First Normal Form (1NF)
❖ Eliminate duplicative columns from the same table.
❖ Create separate tables for each group of related data and identify each row with a unique
column or set of columns (the primary key).
❖ The information stored in relational a database and each column contain atomic value, and
there are no repeating group of columns.

Second Normal Form (2NF)

The requirements to satisfy the 2nd NF:
➢ All requirements for 1st NF must be met.
➢ Redundant data across multiple rows of a table must be moved to a separate
table.
➢ The resulting tables must be related to each other by use of foreign key
➢ The table of the second normal form and the entire column depend on the
table primary key. composite key or partial dependence

70
 Third Normal Form (3NF)
Third normal form (3NF) goes one large step further:

✓ Meet all the requirements of the second normal form.

✓ Remove columns that are not dependent upon the primary key.
✓ Remove Transitive Dependency
Admin Table
1FN

Admin _ID First Last Educationa Position Phone Email Address

_Name _Name l _Status _No _Address

➢ Each column of admin table atomic value and no rows may be duplicated, so that it full
fill 1NF.
➢ It also full fill the 2NF and 3NF, because of there is no partial dependence and transitive
dependence.

Pregnant Women Table

1NF

PW _ID First Last Email Phone Address Age Marital ANC_Reg

_Name _Name _Address _No Status _No

➢ Each column of pregnant women table atomic value and no rows may be duplicated, so
that it full fills 1NF.
➢ It also full fills the 2NF and 3NF, because of there is no partial dependence and transitive
dependence.

Appointment Table

1NF

71
Appointment_ID Appointment Appointment Appointment HP_ID Pregnant_Women_ID
_Time _Date _Description

➢ Each column of appointment table atomic value and no rows may be duplicated, so that it
full-fills 1NF.
➢ It also full fills the 2NF and 3NF, because of there is no partial dependence and transitive
dependence.

Health professional Table

1NF

HP First Last Educational Position Phone Email Address Adin

_ID _Name _Name _Status _No _Address _ID

➢ Each column of health professional table atomic value and no rows may be duplicated, so
that it full-fill 1NF.
➢ It also full-fill the 2NF and 3NF, because of there is no partial dependence and transitive
dependence.
➢ And all other tables are full fill 1NF, 2NF and 3NF.

72
4.4.5 Access control and security Access control
Here we will describe the privileges or authorities of actors over the functionalities. In
this system there are three Four actors Administrator, Health Professionals, the Pregnant
woman and the system. Each has their own privileges to gain access of the system.

Table 4. 1 Access control and security control

Pregnant Health Administrator The System
Woman Professional

Login ✓ ✓ ✓

Logout ✓ ✓ ✓

Signup ✓

View symptom ✓

View advice ✓

View message ✓

Search ✓ ✓ ✓

View appointment ✓

View history ✓

Make appointment ✓

Update appointment ✓

Send message ✓

Register ✓

Delete ✓

Update ✓

Change password ✓ ✓ ✓

Send advice ✓

73
4.5 User Interface Prototyping
In our system there are two interfaces, the mobile based application user interface and
web-based application user interface

4.5.1 Navigation Tree For web-based application

Figure 4. 3 Prototyping for Admin and HP (web-based)

74
4.5.2 Navigation Tree for mobile based application

Figure 4. 4 Prototype of pregnant woman's page (mobile application based)

75
4.6 User Interface Design

76
 Figure 4. 5 User interface design from pregnant woman side
When the web application is browsed the login page displayed

77
 Figure 4. 6 Adim login page
After the admin successfully login the home page will be displayed

Figure 4. 7 Admin home page

78
When admin clicks the register menu item, then the registration form is displayed

Figure 4. 8 registration for HP

When admin clicks change Manage account menu item, then the submenus will be displayed then when
he/ she clicks change password sub menu item the change password form will be displayed.

Figure 4. 9 change password UI

79
When admin clicks change Manage account menu item, then the submenus will be displayed then when
he/ she clicks Delete Account sub menu item the Delete account form will be displayed.

Figure 4. 10 Delete account form

80
 Chapter Five

5 Conclusion and Recommendations

5.1 Conclusion
This project is intended to develop an android based antenatal care system to help maternal
mother’s, health professionals and health institutions. The system contains two parts, these are
mobile application and web application, both within the same database. The mobile application
is used for the pregnant woman whereas the web application intends for the HPs and Health
institutions. Mobile application let for the pregnant woman to see her and her baby’s weekly
health status, to receive appointment and message from the health professionals. The web
application concerns the health professional and an Admin. HP performs his duties like
sending a message and making or updating an appointment. Admin performs duties like
registering and managing HP and controlling the overall systems performance.

Concerning the system, we tried to explain every detail explanation of the system with five
chapters. and each chapter has a specific deliverable which is essential and base for the next
chapter.

In the first chapter we tried to talk about introduction of the system, this part’s major infuses
are: describing about background where the new system is intended to be built on, the
problems in the system that have been identified, the benefit and significance of the project, the
feasibility part that studies about building a new system, the scope of the proposed system that
has been defined , the methodology part which describes about the selected programming tools
and methods and finally, each phase and its perspective work is scheduled.

The second chapter is conducted for the existing system. This section concerns about analyzing
the different activities of the current antenatal care system in Ethiopia, and then the weakness
and the strength which is encountered during doing these activities are analyzed. It also deals
with describing about the proposed system.

The third and the fourth chapters describe about analysis model which contains the functional
and non- functional requirements, use case, sequence, activity diagram, conceptual modeling of
classes and user interface prototypes. And also contains design model which consists deployment

81
diagram, system architecture design, Database table design, Schema design, and normalization
and access control.

5.2 Recommendation
In the system the system there are too many limitations that we cannot fulfilled because of time
and shortage of some software’s. And for the future we recommend that this limitation should be
done when there is chance of getting software or enough time. these limitations are: -

֎ Taking ultrasound
֎ Check blood pressure
֎ laboratory checkup’s such as blood

Finally, the team will recommend that further work should done on the system because in the
future if our system starts performing its job fully any pregnant woman may visit her doctor
physically only for one time (i.e. during delivery).

82
References
[1] J. R. Pichandy C, “Usage of Smartphone Apps by Women on their Maternal Life,” J. Mass
Commun. Journal., vol. 05, no. 07, pp. 1–6, Jul. 2015.

[2] J. Kaewkungwal, P. Singhasivanon, A. Khamsiriwatchara, S. Sawang, P. Meankaew, and A.

Wechsart, “Application of smart phone in "Better Border Healthcare Program": A
module for mother and child care,” BMC Med. Inform. Decis. Mak., vol. 10, no. 1, p. 69, Dec.
2010.

[3] “List of countries by maternal mortality rate,” pp. 1–7, 2019.

[4] “The Benefits of Agile Software Development.” [Online]. Available:

https://resources.collab.net/agile-101/agile-software-development-benefits. [Accessed: 18-Feb-
2019].

[5] “UML basics: An introduction to the Unified Modeling Language.” [Online]. Available:
https://www.ibm.com/developerworks/rational/library/769.html. [Accessed: 14-Feb-2019].

[6] “6 OOP Concepts in Java with examples [2019] · Raygun Blog.” [Online]. Available:
https://raygun.com/blog/oop-concepts-java/. [Accessed: 14-Feb-2019].

[7] “Integration Testing - Software Testing Fundamentals.” [Online]. Available:

http://softwaretestingfundamentals.com/integration-testing/. [Accessed: 18-Feb-2019].

[8] “Security Mechanisms.” [Online]. Available: https://javaee.github.io/tutorial/security-

intro002.html. [Accessed: 18-Feb-2019].

[9] A. Gemino and D. Parker, “Use Case Diagrams in Support of Use Case Modeling,” J. Database
Manag., vol. 20, no. 1, pp. 1–24, 2009.

83
Appendix

Questionnaires we used during interview.

✓ Some of the questions that we were asking in questionnaire time were: -

1. what are the methods that the institution is currently using?
2. what are the responsibilities of each professionals that are working in the
institution specially around pregnancy?
3. what are problems that are facing the institution during visiting time?
4. what are problems that are facing the health profession during visiting time?
5. what are problems that facing the pregnant women during visiting time?
6. what should be done in the future to solve problems that are facing in the current
system?

84