Chap 5 - D and I of Account Holders Info System For Microfinance Bank (PHP)

CHAPTER FIVE
SYSTEM IMPLEMENTATION
5.1 Introduction
System implementation is a process of ensuring that the information system is
operational. Implementation allows the users to take over its operation for use and
evaluation. It involves training the users to handle the system and plan for a smooth
conversion.[ CITATION imp181 \l 1033 ]
This chapter will include Coding phase, Test system implementation, development
testing, release testing, user testing, developing user manuals and chapter summary.
5.1 Coding Phase

The coding phase of the software life-cycle is concerned with the development of code
that will implement the design. This code is written is a formal language called a
programming language. Programming languages have evolved over time from
sequences of ones and zeros directly interpretable by a computer, through symbolic
machine code, assembly languages, and finally to higher-level languages that are more
understandable to humans.[ CITATION INN09 \l 1033 ]
This Phase is devoted to providing access to most of the computer programs that the
researcher used to prepare the data and apply the programming is techniques,
instructions on how to construct this application project using the software available on
the attached compact disk (CD).
5.2 Test system implementation

The testing phase involves some modification to the pervious design phase and system
testing has been done to minimize the programming errors.
Testing the system is a very important stage to ensure that all system requirements have
been developed without errors. System testing can be done through some stages. These
include.
1
1. Developing test
2. Release test
3. User test
5.2.1 Development testing

Development testing is a software development process that involves synchronized
application of a broad spectrum of defect prevention and detection strategies in order to
reduce software development risks, time, and costs. Development testing is always done
by the developer who is responsible programming stage.
This testing shows as if wrong username and password is entered can’t allowed to
access the system.
Figure 5. 1 Login failed
5.2.2 Release testing

Prior to making a software system available for public consumption, a series of tests
should be conducted to ensure the software runs as intended. Flaws are fixed and
inefficiencies removed to come up with a program that runs seamlessly. A battery of
tests is conducted with a view towards identifying and fixing bugs, which are a
precursor for system failure. It is an essential part of the Software Development Life
Cycle (SDLC), and may perhaps be considered the most important aspect, aside from
2
design and coding. Indeed, the quality of the product plays a huge part in setting the
stage for the acceptance and success of subsequent ones in the market. With this in mind
testing hitherto release of software should not be taken for granted. [ CITATION Bro161 \l
1033 ]
The ability to evaluate and ensure the quality of in-process and/or final product based on
process data, which typically include a valid combination of measured material
attributes and process controls. A release is the distribution of the final version of an
application. A software release may be either public or private and generally constitutes
the initial generation of a new or upgraded application.
Figure 5. 2 Dashboard
5.2.3 User testing

User testing refers to a technique used in the design process to evaluate a product,
feature or prototype with real users. There are several reasons why you might want to
undergo usability testing, the most common is that it allows the design team to identify
friction in a user experience they are designing, so that it can be addressed before being
built or deployed. Identifying any issues early reduces the long-term cost. [ CITATION
use18 \l 1033 ]
This system has been tested by the user (alpha testing), the developer and the user (beta
testing), and the user only in his work location (Acceptance testing).
Alpha Test: An alpha test is a preliminary software field test carried out by a team of
users in order to find bugs that were not found previously through other tests. The main
3
purpose of alpha testing is to refine the software product by finding (and fixing) the
bugs that were not discovered through previous tests.[ CITATION alp17 \l 1033 ]
Beta Test: Beta testing is also sometimes referred to as user acceptance testing (UAT) or
end user testing. In this phase of software development, applications are subjected to
real world testing by the intended audience for the software. The experiences of the
early users are forwarded back to the developers who make final changes before
releasing the software commercially.[ CITATION Rou15 \l 1033 ]
5.3 Developing User manuals
In computer software product development, documentation is the information that

describes the product to its users. It consists of the product technical manuals and online
information (including online versions of the technical manuals and help facility
descriptions). The term is also sometimes used to mean the source information about
the product contained in design documents, white papers, and blackboard session notes.
Also, is a general term for a multiplicity of documents in a chosen mix of media and
with a certain collection. Purpose of documentation is the use to support a tool or a
process. Classical documentation is a set of documents printed on paper.
Figure 5. 3 Customer page
Step 1: Fill the form and insert data
Step 2: Click Save/Insert
4
Step 3: To update or delete search fill the Form
Step 4: Click update or delete
Figure 5. 4 Witness
Figure 5. 5 Responsible
5
Figure 5. 6 Address page
Figure 5. 7 Contract page
6
5.4 Chapter Summary

This chapter discusses about the implementation and testing of the system. Developing
the system requires a server, host to access the portal. The purpose of the Testing is to
check the errors and analyze the problem in order to develop a successful System that
meets the users’ requirements. In this I have discussed important points on the system
Development starting form introduction of the chapter then the Coding step of system,
Types of testing, User Documentation, and the last Implementation although I have
covered majority of the project now I am going to Conclude and Summarize this
research and for recommendations of the project.

Chap 5 - D and I of Account Holders Info System For Microfinance Bank (PHP)

Uploaded by

Copyright:

Available Formats

Chap 5 - D and I of Account Holders Info System For Microfinance Bank (PHP)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chap 5 - D and I of Account Holders Info System For Microfinance Bank (PHP)

Uploaded by

Copyright:

Available Formats

CHAPTER FIVE

5.1 Coding Phase

5.2 Test system implementation

5.2.1 Development testing

Figure 5. 1 Login failed

5.2.2 Release testing

5.2.3 User testing

In computer software product development, documentation is the information that

Figure 5. 3 Customer page

Step 1: Fill the form and insert data

Step 2: Click Save/Insert

Step 4: Click update or delete

Step 1: Fill the form and insert data

Step 2: Click Save/Insert

Step 3: To update or delete search fill the Form

Step 4: Click update or delete

Step 1: Fill the form and insert data

Step 2: Click Save/Insert

Step 4: Click update or delete

Figure 5. 6 Address page

Step 1: Fill the form and insert data

Step 2: Click Save/Insert

Step 3: To update or delete search fill the Form

Step 4: Click update or delete

Figure 5. 7 Contract page

Step 1: Fill the form and insert data

Step 2: Click Save/Insert

Step 4: Click update or delete

5.4 Chapter Summary

You might also like