SCHOOL OF TECHNOLOGY

BACHELOR OF BUSINESS INFORMATION TECHNOLOGY

UNIT: BBIT-03107

NAME: RUTH NJAGI

REG. NO. 18/01076

BUSINESS PROJECT

TITLE: EMBU LEVEL 5 MATERNAL HEATH PATIENT MANAGEMENT SYSTEM

SYSTEM TESTING AND IMPLEMENTATION

Email: [email protected]

SUPERVISOR: MR. Patrick Ogao

SEP- DEC 2022

1|Page
||2022 KCAU|SOT|OgaoPatrick|supervisor
1.0 SYSTEM TESTING
1.1 INTRODUCTION
Software testing determines when a software system can be released and used by the intended
user. The purpose of this test is to evaluate the system’s compliance with the specified
requirements.
One of the purposes of testing is to validate and verify the system. Verification
means checking the system to ensure that it is doing what the function is supposed
to do and validation means checking the system to ensure that the system is doing
what the user wants it to do.
No program or system design is perfect, communication between the user and the
designer is not always complete or clear, and time is usually short. The result is
errors and more errors.
Therefore, a newly designed system should have all the pieces in working order, but
in reality, each piece works independently.
The purpose of the system testing is to consider all the likely variations to which it
will be subjected and then push the system to its limits. If we implement the system
without proper testing then it might cause the problem.

1.2 Levels of testing

The different types of testing are as follows:
1.2.1 Unit testing
This is the smallest testable unit of a computer system and is normally tested using
the white box testing.
This is the test development process and ensures that each unique path of the project
performs accurately to the documented specifications and contains clearly defined
inputs and expected results.
1.2.2 Integration testing
Here, the different units of the system are integrated together to form the computer
system and this type of testing checks the system as a whole to ensure that it is
doing what it is expected to do.
The testing of an integrated system can be carried out top-bottom, bottom-up, or

2|Page
||2022 KCAU|SOT|OgaoPatrick|supervisor
big-bang. In this type of testing, some parts will be tested with white box testing and
some with black box testing techniques.
1.2.3 System testing
A part from testing the system to validate the functionality of software against the
requirement, it is also necessary to test the non-functional aspect of the system.
Some examples of non-functional tools include tests to check performance, data
security, usability, volume, load that have been used in our project to test the various
modules.

System testing consists of the following steps:

Program testing
String testing
System testing
System documentation
User acceptance testing

1.2.4 Field testing

Here, the system is tested in the actual operational surroundings. The interfaces with
other systems and the real world are checked. This type of testing is very rarely
used.

1.2.5 Acceptance testing

After the developer has completed all rounds of testing and he is satisfied with the
system, then the user takes over and re-tests the system form his point of view to
judge whether it is acceptable according to some previously identified criteria. This
is almost always a tricky situation in the project because of the inherent conflict
between the developer and the user.

Why system testing?

Testing is vital to the success of the success. System testing makes a logical

3|Page
||2022 KCAU|SOT|OgaoPatrick|supervisor
assumption that if all the parts of the system are correct, the goal will be
successfully achieved.
Inadequate testing results in two types of problems:
The time lag between the cause and the appearance of the problem.
The effect of system errors on the files and the records within the system.
Another reason for system is its utility as a user-oriented vehicle before
implementation.

2.0 TEST PLAN

The test plan entails the following activities:
Prepare test plan
Specify conditions for user acceptance testing.
Prepare test data for program testing
Prepare test data for transaction path testing
Plan user training
Compile /assemble programs
Prepare job performance aids
Prepare operational documents
Prepare test
A workable test plan must be prepared in accordance with established design specifications. It
includes the following items:
Outputs expected from the system
Criteria for evaluating outputs
A volume of test data
Procedure for using test data
Personnel and training requirements
Specify conditions for user acceptance testing
Planning for user acceptance testing calls for the analyst and the user to agree on conditions for
the test

Prepare test data for program testing

4|Page
||2022 KCAU|SOT|OgaoPatrick|supervisor
As each program is coded, test data are prepared and documented to ensure that all aspects of the
program are properly tested.

Prepare test data for transaction path testing

The activity develops the data required for testing every condition and transactions to be
introduced into the system. The path of each transaction from origin to destination is carefully
tested reliable results.

Plan user training

Is designed to prepare the user for testing and converting the system.
User involvement and training takes place parallel with programming for three reasons:
The system group has time available to spend on training while the programs are being written.
Initiating a user-training program gives the systems group a career image of the user’s interest in
the new system.
A trained user participates more effectively in system testing.

Compile/assemble programs
All programs have to be compiled/ assembled for testing.

Prepare job performance aids

Here, the materials to be used by personnel to run the system are specified and scheduled. This
includes display of materials.

Prepare operational documents

During the test plan stage, all operational documents are finalized including copies of the
operational formats required by the candidate system.

System testing

5|Page
||2022 KCAU|SOT|OgaoPatrick|supervisor
The computer department to ensure that the system functions as specified does this testing. This
testing is important to ensure that a working system is handed over to the user for acceptance
testing.

Acceptance testing
The suer to ensure that the system functions, as the suer actually wanted performs this testing.
With prototyping techniques, this stage becomes very much a formality to check the accuracy
and completeness of processing. The screen layouts and outputs should already have been tested
during the prototyping phase.
The error in the program code can remain undetected indefinitely. To prevent this from
happening the code was tested at various levels. To successfully test a system, each condition,
and combination had to be tested. Each program was tested and linked to other programs. This
unit of programs I tested and linked to other units and so on until the complete system has been
tested.
The program of testing is to ensure that each program is fully tested. To do so a test plan had to
be created.

3.0 Verification and validation

The objectives of verification, validity activities are to assess and improve the quality of the
work products generated during development and modification of the software.
Quality depends upon the various attributes like correctness, completeness, consistency,
reliability, usefulness, usability, efficiency and conformance to standards.

4.0 SYSTEM IMPLEMENTATION.

4.1 System implementation, maintenance and review
As we know, creating software is one thing and the implementation of the created software is
another. The process of implementing software is much difficult as compared to the task of
creating a project. First we have to implement the software on a small scale for removing the
bugs and other errors in the project and after removing them we can implement the software on a
large scale. Before we think in terms of implementing the software on a large basis, we must
consider the hardware requirements.

6|Page
||2022 KCAU|SOT|OgaoPatrick|supervisor
Whether we develop software or project a certain hardware and software is being used by the
programmer for developing the programmer for developing the project. The hardware and
software to be used by the programmer for developing the project should be such that it would
result in the development of a project, which would satisfy all the basic needs for which project
has been created by the programmer. The hardware should be such that cost constraints of the
client should also be taken into account without affecting the performance.

4.2 Hardware evaluation factors

Performance
Cost
Reliability
Availability
Compatibility
Modularity
Technology
Ergonomics
Connectivity
Environmental requirements
Software
Support

4.3 Software evaluation factors

Software can be evaluated according to many factors similar to the hardware evaluation.
However, the software evaluation factors are summarized below:
Efficiency- is the system a well-written system of computer instructions that does not use much
memory capacity or CPU time.
Flexibility- can it handle its processing assignments easily without major modifications?
Security- does it provide control procedures for errors, malfunctions and improper use?
Language- do our computer programmers and users write it in a programming language that is
used?
Documentation- is the system well documented? Does it include helpful user instructions?

7|Page
||2022 KCAU|SOT|OgaoPatrick|supervisor
Hardware- does existing hardware have the features required to best use this software?

4.4 Security measures

Security performed in Embu Level 5 maternal health management system.
User name & password security implemented so that no unauthorized person can handle any
operation without username and password.
Only authorized person can log on to the system
Only authorized person can update the records
Only authorized person can handle the reservation
Only authorized person can print the report
It has two kinds of users:
Administrator- he has completed authority (read, add and modify) of operating the software.
User- when this user logs onto system, he can only view information and other reports. He can
generate different reports.

5.0 RECOMMENDATION & CONCLUSION

5.1 Recommendation
After my research and my conclusion of this project, I highly recommend that the Embu level 5
management system serves as a vital platform to use especially in the 21st century health care
centers where human beings are embracing human beings are embracing technology and where
the manual system of data collection in hospital is becoming strenuous and unreliable.

5.2 Conclusion
This project has been a rewarding experience in many ways. The entire project work has
enlightened me in the following areas.
I have gained an insight into the working of the hospital. The represents a typical real word
situation.
My understanding of database design has been strengthened this is because in order to generate
the final reports of database designed has to be properly followed.
Scheduling a project and adhering to that schedule creates a strong sense of time management

8|Page
||2022 KCAU|SOT|OgaoPatrick|supervisor