PROJECT TITLE: CHILDREN’S IMMUNIZATION

TRACKING SYSTEM
STUDENT NAME: MURIITHI KELVIN GITHAE
REGISTRATION NUMBER: BITC01/0040/2018
 CHAPTER 4
SYSTEM ANALYSIS.

4.1ANALYSIS OF THE CURRENT SYSTEMS

In this chapter, the architecture of the whole project is analysed. System analysis is the
process of defining the architecture, components, and data of a system to satisfy specified
requirements. Design is a method of studying a system by examining its component parts and
their interactions. Before implementation began the system is analyzed and designed. In this
section, use cases, requirement analysis, and other part are described in details. The system
requirements provide the functional and Non-functional requirements of the system. Design
of the system is carried out according to the features and operations of the system which
includes the user interface, UML diagrams and other documentation. Designing of the system
mainly focuses on the user and ensuring the system will be user friendly and interactive. The
system analysis for the development of Children’s immunization tracking System is
presented below. It shows the current state of the system to be worked on. The order of
events is adopted from the traditional Software Development Lifecycle (SLDC).
4.2 SYSTEM REQUIREMENTS

This section clearly identifies the environment setup for the proper working of the Children’s
immunization tracking. It states both the hardware and software required for the proper
deployment and use of the software system.

4.2.1FUCTIONAL REQUIREMENTS.
The parents will be able to record immunization details of their child. Once the user is
registered the details are saved to the database. The user will also be able to set a reminder for
next immunization dates and receive a pop -up notification when the desired set time come

4.2.2NON-FUNCTIONAL RECQUIREMENTS.

Security
The system will be very secure as all the data will be stored in a hosted relational database and

allow user authentication.

Effectiveness
The system will be much reliable and efficient with minimum failures.
Size
The system will require reasonable amount of online server memory as the databases will be
hosted online.

User friendly
The system will have a very nice user interface which will be easy to use with direct menu and

minimized overlaying layout

CHAPTER FIVE

SYSTEM DESIGN

INTRODUCTION
The system design development is presented to provide a detailed description of the design
environment and the system components giving the detailed design of the proposed system
using tools like ERDs, DFDs, UML etc.

5.1 ARCHITECTURAL DESIGN

This section is concerned with understanding how the software system is organized and the
design of the overall structure of the system. This section yields the architectural model that
describes how the system is organized as a set of communicating components.
SEQUENCE DIAGRAM

Sequence diagram is a graphical representation of the whole system, that how the parent and
the Admin will log in. How the parent will add the child, and how the Admin will add and
allocate vaccines and allocate them

ACTIVITY DIAGRAM

Activity diagram is another important behavioral diagram in UML diagram to describe

dynamic aspects of the system. Activity diagram is essentially an advanced version of flow
chart that modelling the flow from one activity to another activity.
5.2 DATABASE DESIGN

USE CASE MODEL

This represents a simple scenario that describe what the users expect from the system. It
represents users and other systems as actors, class of interactions and link between them
using some symbols.

Figure 12 use case diagram

5.3 USER INTERFACE DESIGN

Registration page
Login page
CHILD REGISTER PROFILE, DISPLAY CHILD INTERFACES AND VACCINES REMINDER
CHAPTER SIX
TESTING AND IMPLEMENTATION.
INTRODUCTION.
Software testing is used to identify the defects in the system and also to help judge whether or
not the system is usable and practical. Thus, software testing is used for validation and
verification, which ensure that the software is aligned to its specification and meets all needs
of the end User. Alpha testing was practiced this case, Alpha testing usually comes after the
basic design of the program has been completed. The project scientist will look over the
program and give suggestions and ideas to improve or correct the design and working. They
also report and give ideas to the developer to get rid of any major problems. There is bound
to be a number of bugs after a program have been created.

ALPHA TESTING STEPS

Types of testing are done using various test cases to test the various aspects of our
application.

(i)Unit Testing- This ensures that each component is working independently of one
another. It includes ensuring successful log in for authorized users, Display immunization
timetable and allow for reminder to be set.

(ii)Integration Testing- This testing is paramount in meeting the systems

functionality objectives. In this testing, once the user has registered into the system, he/she
can log in and be able to register his/her child and be able to see an immunization timetable.
Also set reminder for upcoming vaccines.

(iii)System Testing- This was done after integrating all modules and running the whole
system to verify if it meets the functional and non-functional

requirements. It ensures the system can work fully such that the user can be able to view
received vaccines and upcoming vaccines.

(iv)Acceptance Testing- This is done prior to deploying the system to a live

environment. It is done using specified inputs into the system and verifies that

the resulting outputs are correct, without knowing the internal workings of the

system.

6.1 DEVELOPMENT ENVIRONMENT

A development environment is a workplace with a set of processes and programming tools

used to develop the source code for an application. The development environment for this
system has roots in traditional development environment where IDE was the most preferable
used environment because it minimizes the developer’s productivity and efficiency. CASE
tools are used to facilitate the management of the software development project.
6.2 SYSTEM COMPONENTS
Here, the system components that are part of the auction system are described. They refer to a
process, program, utility or another part of a computer’s operating system that helps to
manage different areas of the computer.
Here, the system components that are part of the this system are described. They refer to a
process, program, utility or another part of a computer’s operating system that helps to
manage different areas of the computer.
Summary of modules
In modular programming, the entire software is sub-divided into various modules that are
individually programmed to make up the whole system. As such, while developing the
proposed system, various functionalities of the system were sub-divided into small and
simple modules that were independently programmed. Thereafter, the coded modules were
linked together to form the whole functioning project.
This are the summary of the modules:
Registration module
In this module, both the parent and admin are required to register to the system. The parent is
needed to insert his first name and last name, city, email address and password. No one can
get access to the account without creating their account

Login module
In this module, all the users access the same login Module. The user has to use the similar
details used during registration. After a successful login, the system dynamically loads to the
user’s dashboard based on the user role to the system.

6.3 TEST CASES.

During the system development, tests were carried out to determine the work-ability of the

system. Some of these tests include:

Test Case 1 Creating Account.
Input: Name, Password And Email City Date And The Kind Of User Priveledges You Have
Whether A Normal User Or Admin User E.G., Name=’Victor’, Password= ‘112212’ And
Email =’Victor@Gmail.Com’.

Expected result: This function should save the new user details to Firebase database

Test result: If incorrect email format used toast message ‘incorrect email’, when

some fields are left empty it says “field required”

Status: Test passed.

Test Case 2 Login.
Input: username, password.

Expected results: This function should fetch correct details of user accounts as created

in the database and match them with user input to authenticate access to the application.

Test result: When try to log in without filling the required input toast message with

error is displayed “fields Required!” and when incorrect details of user account are

entered toast message displayed “incorrect email or password”

Status: Test passed.

TEST CASE REGISTER

1.1.1 Test Case 3 Registering a child.
Input: Child Name, Child Date of Birth, child Gender, city height weight, age and vaccines

Expected results: This function should insert date into database, if left blank

user is promoted “field Required”

Test results: When data is successfully typed and user submits it a toast message is displayed

“Child Registered Successfully”

Status: Test passed.

1.1.2 Test Case 6
Action: click on a certain vaccine on the Vaccine View Activity.

Expected results: This function should load and fetch vaccines and display

them for the admin user to add the vaccines.

Test results: once the vaccines have been added they are displayed on the parent side

Status: Test passed.

FIGURE 1 REMINDER TEST CASE
CHAPTER 7

CONCLUSION AND RECOMMENDATION.

Children’s Immunization tracking system is a great easy to use utility web application. The

application allows real time tracking of children immunization . The application offers the
advantage of having combined ability to save children’s information and have reminders of
upcoming vaccines. Each user has an account which can be easily accessed from other
devices whenever needed hence proper track of planned activities.

7.1 LESSONS LEARNT

➢ How to define and manage requirements and scope for a software project

➢ How to develop and control schedule in a project

➢ How to develop a software project

LIMITATIONS
The various challenges faced include;

1. Due to android security levels notification channels in some devices need

authorization
from google.

2. Bulky code as the application is customed to independently operate from client’s

devices.

3. Challenge on obtaining information - During fact finding, not everyone was willing to
disclose some crucial information and even some were not confident enough while giving

their responses.

7.2 CONCLUSION
Working on this project has been a sweet challenge to put into practice knowledge acquired
over the course of my study. My programming skill especially to a language that I had not
majored in like PHP which sharpened to intermediate level. Great regards to the
To the cooperative university school of mathematics and Computer science that has given
nothing but the best to ensure that I have a competitive edge in my field. The application that
I have developed I hope will be of great help to parents.

7.3 RECOMMENDATION

To resolve the above problems and realize improvements in the near future the following

recommendations should at least be taken into consideration-

1. Developers should lean towards open-source development to ensure good integration

of their system to maximize potential.
2. Use of Kotlin and API’S that will be less bulky and cut on memory and high system
specification requirements.

3. Longer test case period before implementation to prevent future hanging and crushing
of standalone systems.

REFERENCES.
Young, D. (2013). Software Development Methodologies. White paper.

Elsobeihi, Mohammed & Abu-Naser, Samy. (2017). Effects of Mobile Technology on

Human

Relationships. 1. 110-125.

Daenzer, B. J. (1970). Fact-finding techniques in risk analysis. New York: American

Management Association, 978-0814421390.

 POJECT SCHEDULE
3-
15-Ma 3-Apr 23-Apr 13-May- 23-Jun 13-july 3-Aug 23-
Aug 02-sept
June

Gathering requirements

Analysis

System Design

Coding & Implementation

Testing

Maintenance

APPENDICES.
APPENDIX A: GANTT CHART.

- -
APPENDIX B: BUDGET.

BUDGET
BUDGET
ITEMS
COST

HARDWARE

Laptop
40,000

Smartphone
15,000

Stationery
1,000

SOFTWARE

ESTIMATE.
APPENDIX C: QUESTIONNAIRE.

NAME ID/TEL
1. Do you know any other immunization YES NO
tracking apart from pen and paper?
2. Is it easy to use the method mentioned YES NO
above?
3. Is it easy to access immunization records? YES NO
4. How Reliable is the pen and paper method? YES NO
5. Is there any digital immunization tracking YES NO
method you have heard of?
6. Would a notification on your device push YES NO
you to do something or take specific action
7. Did you find this helpful if above YES NO
challenges were to
be addressed?

SIGNATURE
QUESTIONNAIRE.