Scribd
Upload
3 views7 pages

System Implementation

This document outlines the structure and content required for the System Implementation chapter of a project. It includes sections on implemented features, system testing, changeover methods, and documentation, detailing the necessary explanations and examples for each feature and testing results. The chapter aims to provide a comprehensive overview of the system's functionality and the processes involved in its implementation and testing.

Uploaded by

wangarirahab03
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
3 views7 pages

System Implementation

This document outlines the structure and content required for the System Implementation chapter of a project. It includes sections on implemented features, system testing, changeover methods, and documentation, detailing the necessary explanations and examples for each feature and testing results. The chapter aims to provide a comprehensive overview of the system's functionality and the processes involved in its implementation and testing.

Uploaded by

wangarirahab03
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

By the end of this lesson you should be able to:

Write the system implementation Chapter

6.1 Overview

6.2 Implemented Features

6.3 System Testing

6.4 System Change Over

6.5 System Documentation

6.6. Summary

CHAPTER SIX

SYSTEM IMPLEMENTATION

6.1 Overview

6.2 Implemented Features

Discuss each of the features implemented within your system. (The choice of
features discussed should be based on the objectives that were defined in
chapter one.)

You are required to explain 4 to 6 implementation features

Example

6.2.1. Payment Feature

The payment feature allows a customer to input their credit card details and
make payment. Once they’ve made the payment, the system automatically
notify the customer and proceed the customer to the next level. This
decision gives the system a more organized and refine feel as well as
increasing efficiency and ease of use. Below is figure 6.1 that shows a view
of the code syntax of the payment feature.
Figure 6.1: code syntax of the payment feature.

6.2.2 Receive notification feature

The receive notification feature allows a job applicant who has applied for a
job to know that the application has been successfully made. Below is code
syntax of the receive notification feature.
Figure 6.2: code syntax for the receive notification feature.

6.3 System Testing

Define what system testing is and cite

Briefly explain the importance of testing your system. Highlight the features
to be tested

Explain the field tested, test data used and the testing results obtained

This should be done for 4 to 6 features (the choice should be based on the
features identified in 6.1 above)
The following aspects of the system were focused on during the testing of
the system;

6.3.1 Customer log in

The system should allow a customer to log into the system by using a valid
username and password. The feature was tested on the ability of the
module to function as expected and data validation. Table 6.1 shows the test
results

Table 6.1: Test results for customer log in feature

Test data Test type Test Result

Userna Passw
me ord

1111 •••••• Test validity of the username which Pass


should not be numbers rather than
character

Morris • Test the strength of the password, it Pass


should not be less than 8 characters
must contain at least a special
character and a number

6.3.2 Student Unit registration

The system should allow a student to register for all the units online. This
feature was tested on the ability to allow input into the form, submit the
input data, validate the input data and store the data in the database. Table
6.2 show the results

Table 6.2: student unit registration

Test Field Test data Test Results

Data validation Data Storage into the


database

Student Name Morris Pass Pass

Morris 1

12345

Student CT201/001/ Pass Pass


Registration 20
Number
Units

6.3.3 Module to calculate the shill score of each vendor

As a measure to encourage a vendor to acquire as manty binders as possible


one of the objective of the system is to be able to calculate the shill score for
each vendor. This is automatically done by the system and it is based on the
number of products the vendor has sold. This feature was tested based on
the parameters shown in table 6.3

Table 6.3: Shill score calculation module

Score Test data Test Results


0-100 award 30 0,45,100 Pass
points
Negative value, generate an
error

101- 200 award 101,150,200 Pass


40 points

Above 200 award 201, 1,000,000 Pass


50 points

Others

Customer payment module

Report Generation Module

6.4 System Changeover

Define what is meant by system change over and cite

Briefly explain each type of change over (you need to cite.)

Discuss in great detail the changeover method you applied . Explain how the
changeover method took place e.g if it is phased change over, explain what
was implemented in the different phases.

6.5 Documentation

Define documentation and cite.

Explain the internal documentation and external documentation and cite.

Show internal documentation by taking a snap shot of part of your code


where comments have been made
Explain the content of external documentation (for both the user and the
developer)

Attach an appendix for the user manual

6.6 Summary

You might also like