Contents

ACKNOWLEDGEMENTS.........................................................................................................................2
SECTION A: Selection, Investigation and Analysis....................................................................................3
PROBLEM DEFINITION.......................................................................................................................3
Investigation of the current system..........................................................................................................3
Broad description of the system...............................................................................................................4
EVALUATION OF EXISTING SYSTEM.............................................................................................5
REQUIREMENTS SPECIFICATIONS..................................................................................................5
Aims and Objectives................................................................................................................................6
SECTION B: Consideration of alternative methods....................................................................................7
Consideration of alternative methods......................................................................................................7
Test Plan................................................................................................................................................12
Section C: Software Development.............................................................................................................14
Technical documentation.......................................................................................................................14
Pseudo codes.........................................................................................................................................14
Flowcharts.............................................................................................................................................15
Program Listing.....................................................................................................................................17
User Documentation..................................................................................................................................33
Running the system/ Navigation the system..............................................................................................36
Section D: Testing and Evaluation............................................................................................................42
Error Messages..........................................................................................................................................43
Ease of use testing.............................................................................................................................45
Functionally correct...........................................................................................................................45
Efficient to use...................................................................................................................................45
Easy to learn......................................................................................................................................45
Error tolerant.....................................................................................................................................45
Effectiveness.....................................................................................................................................46
Evaluation of the System...........................................................................................................................47
Achievements........................................................................................................................................47
Limitations................................................................................................................................................48
Opportunities for Future Developments....................................................................................................48
Appendix...................................................................................................................................................49
ACKNOWLEDGEMENTS
I would like to express my gratitude to my teacher Mr. Chapinduka for his great guidance when
challenges aroused. My parents for all the unconditional support they gave me. My colleagues
for installing the competence that encouraged hard word.
SECTION A: Selection, Investigation and Analysis
PROBLEM DEFINITION

St John’s School Chikwaka Report processing is a system that is currently running St John’s
High School Chikwaka which is a school situated in Goromonzi District 50km East of Harare. It
is 5km from Juru Growth point along the new Mutoko road. It is a private high school under the
Anglican Diocese of Harare. The school has about 900-1000 students and every end of term the
few teachers at this institution write the reports of every student and a lot of problems are
encountered during the process for example incorrect addition of marks due to limited processing
time. The school enrolls new students every year and writes their names on paper so this problem
of report processing started years back and it’s still existing. These reports are written by 52
teachers manually using the sharp calculator and therefore many problems are faced. The
teachers enter information about the student name, class, class position, percentage of
examination and comment. The reports are then kept at the administration block and then
distributed to the student at the end of the term.

Investigation of the current system

THE INTERVIEW QUESTIONS

1. Do you have any standing backup for the mark schedule?

2. Why don’t you have a standing backup for the mark schedule?
3. I heard that a student can temper with his/her mark on the mark schedule?
4. What will be done with those who does not submit their report books in time?
5. What other use do you take the login details for?
6. Do you think it is ideal to introduce a new computerized system that provides
summarized information for the admin?
7. I heard that when a teacher miscalculates a student’s marks nothing is done about it?
What do you suggest for a solution?
8. What do you do if the mark schedule is lost? Do you have any alternative?
THE QUESTIONNAIRE

I am Leslie M Sarai, a form four student who is conducting a project based on the Report
Processing at your school. I kindly ask you to assist me by answering truthfully for all the
questions that follow. Thank you in advance for your effort and time.

1. How long have you been using the existing system?

2. Who does the calculations of marks for the report?
3. Do you still use the pen and paper system?
4. Do you have the problem were by students loses their report books
Yes No
5. Do you find it ideal to replace with a new computerized system?
Yes No
6. Do you have a computer skill at any level?
Yes No
7. Are there any computers at your school?
Yes No

Broad description of the system

The information below describes how existing system the functions.

Inputs of the existing system

The teacher will enter the student’s details which include name, surname, gender and all the
student’s subject .The teacher will then record the marks of each student

Processes of the existing system

Calculating the averages, percentages, total mark and to calculate the total number of subjects
failed and passed

Output of the existing system

The student’s total marks, grade and number of subjects passed or failed then written report
Storage

Reports for the class are then stored in one big envelope.

They are kept in the administration bock.

Reports are then distributed by the class teachers.

EVALUATION OF EXISTING SYSTEM

Weakness of existing system

 Reports are calculated manually therefore they are they are more prone to errors.
 Takes long to process reports.
 Requires more human efforts therefore tiring causing errors.
 The reports can be stolen by students and may temper with their marks.
 If errors are made on report a new one is required and process is repeated.
 Records of the mark and grades can be also lost.

Strengths of existing system

 No alterations are made on report.

 It cannot be hacked since it is not electrical
 Does not require electricity for it to function Requirement specification

REQUIREMENTS SPECIFICATIONS
Software requirements

 Microsoft Access

To create database for each class to make it easy to search for student’s information

To be entered on report, it also works as the backup information.

 Antivirus
To clear out viruses in the computer or laptop to make it work more efficiently.
 Microsoft word

To design the report card and also enter some information.

Hardware Requirements

 Printer
- To print out the report cards.
 Hard Disc
To store the data

Aims and Objectives

Aims

 To reduce financial resources

 To create a good reputation for the school

Objectives

 Can enter students marks into the database

 To search student’s details and enter students marks for the term.
 To automatically calculate students total marks.
 To state number of subjects passed
 To validate the marks

Evidence of Research

(see appendix)

SECTION B: Consideration of alternative methods

In this section the systems analyst will be looking for a solution that can be used to overcome the
problems currently faced in the existing system.
Consideration of alternative methods
Alternative method 1: Tailor-Made software

This involves inviting a System Analyst/ Developer to produce an Enrolment System that is
specifically for St John’s High School which will be user friendly.

 The software is designed exactly to suit the St John’s High School Report processing System.
 The software can be written to run on hardware that the institution, St John’s High School
already having or is flexible in using.
 The user, St John’s High School has direct control over the program as the software was
produced “in-house.”
 All features found in the software are useful as it is written for specific use
 The software built can be integrated with the existing system at the institution

Alternative method 2: Using Ready-Made software

This involves purchasing of off-the-shelf software from Software shops, so that they help to
increase speed and efficiency on the current system.

 It is less expensive compared to tailor- made since it is designed for general use
 Readily available
 Reliable as it is mostly bug-free
 It takes a lot of time for the user to be able to operate the system smoothly, due to
presence of many general features
 May contain some features which are not important for the required system since it is
designed for general purposes

Justification of method of solution

Although there were a variety of choices to choose, which solution to implement in order to
overcome problems and limitations which are associated with the current system the system
Analyst chose Tailor Made because?
 1. It is relatively cheaper for St John’s High School because there are no huge development
costs to be shared.
2. All features found in the tailor-made software are useful as it is designed for specific use
rather than purchasing a Package which comprises of many features which are not needed
in the Enrolment System.
3. The software built can be integrated with the existing system at the institution meaning
that it will be an aided advantage to St John’s High School.

Input Design
Login Form

Field Name Data Type Field Size Description

Username Short text 15 Characters Username of user

Password Short text 15 Characters Password of user

Access Short text 6 Characters Level of the user

Eg admin

The log in form

Register Students into the system

Field Name Data Type Field Size Description

Name Short text 15 Characters Name of user the

students

Surname Short text 15 Characters Surname of the

Students

Level Short text 6 Characters Level of the Student

Eg A-level

Sex Short text 6 Characters Male or Female

The Student Registry the Form

A level Update reports Form

Output
Statistics

A level View Form

Test Plan
White Box text plan
The white box testing also identifies errors not identified by the black box testing. It verifies and
validates the quality as well as accuracy of the testing data. It helps identify the line of code that
is being executed. It also validates quality of a software’s product internal structures.

The system was taken through the White box test plan and the outcomes came out as illustrated
in the tables below. All the data is verified, checked for validation on both; the device
specifications and informational formats and the ability to search and give correct result or use a
system of message boxes for any error.

Test Case Test Data Expected Results Pass / Fail

Validation To check whether the Display error reporting Pass

validation is executed message
when the required field is
blank or wrong format

Verify To check whether the Error report display if Pass

entered details match the the data does not match
required information

Search To check whether system Display all the required Pass

can search a device in details
the database

Login
NAME CASE DESCRIPTION EXPECTED OUTCOME OUTCOME
 PASS/FAIL

LOGIN A -user forgets to enter Message window pops Pass

username/password
“enter all credentials”

B -user enters wrong Message window pops Pass

password/user type
“wrong password/username

C -use enter correct Message window pops Pass

username/password and
“login successful”
user type

Section C: Software Development

Technical documentation
In this section the analyst showed the steps and instructions that he gave to the program in order
for it to manage to handle the problems faced by the existing manual system.
Pseudo codes
The following are a set of English like statements used by the analyst to feed the program with
instructions that are followed when executing a task

Add New User

1. Start
2. Enter username, password
3. Select department
4. If password length is less than 4 characters, Then
5. Display message “password too short”
6. Else If password length is more than 4 characters Then Add record to database
7. Else If any required field is empty Then Display error message “enter user credentials”
8. Create a record in database
9. Save progress
10. Stop

Calculating the Statistics

1. Start
2. Initialize All level=0,Allzjc=0,Allalevel=0
3. For n= 1 to number of students in the database
4. If data reader for level=”A level” then All level=Allalevel+1
5. Elseif data reader for level=”O level” then All level=Allolevel+1
6. Elseif data reader for level=”ZJC” then Allzjc=Allzjc+1
7. Display Allolevel,Allzjc,Allalevel
8. stop

Flowcharts
This section shows the flow of data within the system during the execution of a task
Deleting student

Start

Select a record

Connection to the database

established

Erase the record

Refresh the database

Start

Searching a student

Start
 Enter name of student

Connection to the database

established

Create a query using the

student name

Is query
Msgbox ”No results”
empty

Display results

Stop

Program Listing
The following are the codes that were used by the analyst to instruct the computer on some of the
modules.
The log in codes

Imports System.Data.OleDb
Imports System.IO
Public Class login
'the connection string
Dim conn As New OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" &
Application.StartupPath & "\Report.mdb")
Dim dr As OleDbDataReader
Dim i As Integer
Private Sub btnshow_CheckedChanged(sender As Object, e As EventArgs) Handles btnshow.CheckedChanged
'if the radio button is checked then the password is hidden
If btnshow.Checked = True Then
txtpass.UseSystemPasswordChar = False
'if the radio button is not checked then the password is shown
ElseIf btnshow.Checked = False Then
txtpass.UseSystemPasswordChar = True
End If
End Sub
Private Sub btnlogin_Click(sender As Object, e As EventArgs) Handles btnlogin.Click
'when the login button is clicked the following will happen
Authorization()
'All textboxes will be cleared
txtpass.Clear()
txtuser.Clear()
End Sub
' this is where the authorisation is taking place
Sub Authorization()
Try
conn.Open()
'selecting from the login table the credentials
Dim cmd As New OleDb.OleDbCommand("select*from Login where Username=@Username and
Password=@Password", conn)
cmd.Parameters.Clear()
cmd.Parameters.AddWithValue("@username", txtuser.Text)
cmd.Parameters.AddWithValue("@password", txtpass.Text)

Dim username As String = ""

 Dim password As String = ""

dr = cmd.ExecuteReader
'if credentials entered are correct
If (dr.Read() = True) Then
username = dr("username")
password = dr("password")
GunaLabel1.Text = "Authentication"
' your level is Admin you will go to the admin form
If dr.Item("Access") = "Admin" Then
Form1.Show()
' your level is Teacher you will go to the Teacher form
ElseIf dr.Item("Access") = "Teacher" Then
ClassTeacher.Show()
End If
Me.Hide()

ElseIf txtpass.Text = "" And txtpass.Text = "" Then

MsgBox("enter username and password", MsgBoxStyle.Exclamation, "")
Else
MsgBox("Wrong password!", vbCritical)
txtpass.Clear()
txtuser.Clear()
txtpass.Clear()
lblcreate.Visible = True
lblforgot.Visible = True
End If
Catch ex As Exception
MsgBox(ex.Message)
End Try
conn.Close()
End Sub
Private Sub login_Load(sender As Object, e As EventArgs) Handles MyBase.Load
'hiding the password
txtpass.UseSystemPasswordChar = True
End Sub
Private Sub txtpass_Click(sender As Object, e As EventArgs) Handles txtpass.Click
 If txtpass.Focused = True Then
txtpass.Clear()
End If
End Sub

Private Sub btnexit_Click(sender As Object, e As EventArgs) Handles btnexit.Click

Application.Exit()
End Sub

Private Sub lblforgot_LinkClicked(sender As Object, e As LinkLabelLinkClickedEventArgs) Handles

lblforgot.LinkClicked
Forgot_Account.Show()
End Sub

Private Sub lblcreate_LinkClicked(sender As Object, e As LinkLabelLinkClickedEventArgs) Handles

lblcreate.LinkClicked
Create.Show()
End Sub
End Class

The codes for registering a student

Imports System.Data.OleDb
Imports System.IO
Public Class Form1
Dim conn As New OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" &
Application.StartupPath & "\Report.mdb")
Dim dr As OleDbDataReader
Dim i As Integer
Dim AllZJC, AllOlevel, AllAlevel, Female, Male As Integer
Private Sub Form1_Load(sender As Object, e As EventArgs) Handles MyBase.Load
dataload()
Try
conn.Open()
lblstatus.Text = "Connected"
lblstatus.ForeColor = Color.DodgerBlue
Catch ex As Exception
lblstatus.Text = "Not connected"
 lblstatus.ForeColor = Color.Red
End Try
conn.Close()
End Sub
'loading the data into the databases
Sub dataload()
'Selecting from the O-level Table
Try
Female = 0
Male = 0
AllOlevel = 0

GunaDataGridView1.Rows.Clear()
conn.Open()
Dim cmd As New OleDb.OleDbCommand("select * from Olevel", conn)
dr = cmd.ExecuteReader
While dr.Read
GunaDataGridView1.Rows.Add(dr.Item("Name"), dr.Item("Surname"), dr.Item("Level"), dr.Item("Sex"))
If dr.Item("Sex") = "Female" Then
Female = Female + 1
ElseIf dr.Item("Sex") = "Male" Then
Male = Male + 1
End If
AllOlevel = AllOlevel + 1

End While
dr.Close()
Catch ex As Exception
MsgBox(ex.Message)
End Try
'Selecting from the ZJC Table
Try
AllZJC = 0
Dim cmd As New OleDb.OleDbCommand("select * from ZJC", conn)
dr = cmd.ExecuteReader
While dr.Read
GunaDataGridView1.Rows.Add(dr.Item("Name"), dr.Item("Surname"), dr.Item("Level"), dr.Item("Sex"))
 If dr.Item("Sex") = "Female" Then
Female = Female + 1
ElseIf dr.Item("Sex") = "Male" Then
Male = Male + 1
End If
AllZJC = AllZJC + 1
End While
dr.Close()
Catch ex As Exception
MsgBox(ex.Message)
End Try

'Selecting from the A-level Table

Try
AllAlevel = 0
Dim cmd As New OleDb.OleDbCommand("select * from Alevel", conn)
dr = cmd.ExecuteReader
While dr.Read
GunaDataGridView1.Rows.Add(dr.Item("Name"), dr.Item("Surname"), dr.Item("Level"), dr.Item("Sex"))
If dr.Item("Sex") = "Female" Then
Female = Female + 1
ElseIf dr.Item("Sex") = "Male" Then
Male = Male + 1
End If
AllAlevel = AllAlevel + 1
End While
dr.Close()
Catch ex As Exception
MsgBox(ex.Message)
End Try
conn.Close()
Statistics.lblallfemale.Text = Female
Statistics.lblallmale.Text = Male
Statistics.btnallalevel.Text = AllAlevel
Statistics.btnallolevel.Text = AllOlevel
Statistics.btnallzjc.Text = AllZJC
End Sub
 'Saving into O-Level
Sub Olevel()
conn.Open()
Try
If MsgBox("do you want to save", vbYesNo) = vbYes Then
Dim cmd As New OleDb.OleDbCommand("insert into
Olevel(`Name`,`Surname`,`Sex`,`Level`,`Maths`,`English`,`Geography`,`Shona`,`Accounts`,`Combined`,`Computer
`,`Biology`,`Chemistry`,`Physics`,`History`,`FRS`)values(@Name,@Surname,@Sex,@Level,@Maths,@English,@
Geography,@Shona,@Accounts,@Combined,@Computer,@Biology,@Chemistry,@Physics,@History,@FRS)",
conn)
cmd.Parameters.Clear()
cmd.Parameters.AddWithValue("@Surname", txtsur.Text)
cmd.Parameters.AddWithValue("@Name", txtstuname.Text)
cmd.Parameters.AddWithValue("@Sex", sex)
cmd.Parameters.AddWithValue("@Level", cbolevel.Text)
cmd.Parameters.AddWithValue("@Maths", "N/A")
cmd.Parameters.AddWithValue("@English", "N/A")
cmd.Parameters.AddWithValue("@Geography", "N/A")
cmd.Parameters.AddWithValue("@Shona", "N/A")
cmd.Parameters.AddWithValue("@Accounts", "N/A")
cmd.Parameters.AddWithValue("@Combined", "N/A")
cmd.Parameters.AddWithValue("@Computer", "N/A")
cmd.Parameters.AddWithValue("@Biology", "N/A")
cmd.Parameters.AddWithValue("@Chemistry", "N/A")
cmd.Parameters.AddWithValue("@Physics", "N/A")
cmd.Parameters.AddWithValue("@History", "N/A")
cmd.Parameters.AddWithValue("@Shona", "N/A")
cmd.Parameters.AddWithValue("@FRS", "N/A")

i = cmd.ExecuteNonQuery
If i > 0 Then

Else
MsgBox("error", vbCritical)
End If
 End If
Catch ex As Exception
MsgBox(ex.Message)

End Try
conn.Close()
dataload()
clear()
End Sub
'Saving into A-Level
Sub Alevel()
conn.Open()
Try

If MsgBox("do you want to save", vbYesNo) = vbYes Then

Dim cmd As New OleDb.OleDbCommand("insert into
Alevel(`Name`,`Surname`,`Sex`,`Level`,`Maths`,`English`,`Geography`,`Shona`,`Accounts`,`Computer`,`Biology`,`
Chemistry`,`Physics`,`History`,`FRS`)values(@Name,@Surname,@Sex,@Level,@Maths,@English,@Geography,
@Shona,@Accounts,@Computer,@Biology,@Chemistry,@Physics,@History,@FRS)", conn)
cmd.Parameters.Clear()
cmd.Parameters.AddWithValue("@Surname", txtsur.Text)
cmd.Parameters.AddWithValue("@Name", txtstuname.Text)
cmd.Parameters.AddWithValue("@Sex", sex)
cmd.Parameters.AddWithValue("@Level", cbolevel.Text)
cmd.Parameters.AddWithValue("@Maths", "N/A")
cmd.Parameters.AddWithValue("@English", "N/A")
cmd.Parameters.AddWithValue("@Geography", "N/A")
cmd.Parameters.AddWithValue("@Shona", "N/A")
cmd.Parameters.AddWithValue("@Accounts", "N/A")
cmd.Parameters.AddWithValue("@Computer", "N/A")
cmd.Parameters.AddWithValue("@Biology", "N/A")
cmd.Parameters.AddWithValue("@Chemistry", "N/A")
cmd.Parameters.AddWithValue("@Physics", "N/A")
cmd.Parameters.AddWithValue("@History", "N/A")
cmd.Parameters.AddWithValue("@FRS", "N/A")

i = cmd.ExecuteNonQuery
 If i > 0 Then
MsgBox("welldone", vbInformation)
Else
MsgBox("error", vbCritical)
End If
End If
Catch ex As Exception
MsgBox(ex.Message)

End Try
conn.Close()
dataload()
clear()
End Sub
'Saving into ZJC
Sub ZJC()
conn.Open()
Try
If MsgBox("do you want to save", vbYesNo) = vbYes Then
Dim cmd As New OleDb.OleDbCommand("insert into
ZJC(`Name`,`Surname`,`Sex`,`Level`,`Maths`,`English`,`Geography`,`Shona`,`Computer`,`History`,`FRS`,`Combin
ed`)values(@Name,@Surname,@Sex,@Level,@Maths,@English,@Geography,@Shona,@Computer,@History,@
FRS,@Combined)", conn)
cmd.Parameters.Clear()
cmd.Parameters.AddWithValue("@Surname", txtsur.Text)
cmd.Parameters.AddWithValue("@Name", txtstuname.Text)
cmd.Parameters.AddWithValue("@Sex", sex)
cmd.Parameters.AddWithValue("@Level", cbolevel.Text)
cmd.Parameters.AddWithValue("@Maths", "N/A")
cmd.Parameters.AddWithValue("@English", "N/A")
cmd.Parameters.AddWithValue("@Geography", "N/A")
cmd.Parameters.AddWithValue("@Shona", "N/A")
cmd.Parameters.AddWithValue("@Combined", "N/A")
cmd.Parameters.AddWithValue("@Computer", "N/A")
cmd.Parameters.AddWithValue("@History", "N/A")
cmd.Parameters.AddWithValue("@FRS", "N/A")
i = cmd.ExecuteNonQuery
 If i > 0 Then
MsgBox("welldone", vbInformation)
Else
MsgBox("error", vbCritical)
End If
End If
Catch ex As Exception
MsgBox(ex.Message)

End Try
conn.Close()
dataload()
clear()
End Sub

Private Sub btnadd_Click(sender As Object, e As EventArgs) Handles btnadd.Click

If txtstuname.Text = "" Then
MsgBox("enter name", vbInformation)
ElseIf txtsur.Text = "" Then
MsgBox("enter surname", vbInformation)
ElseIf cbolevel.Text = "" Then
MsgBox("enter level", vbInformation)
End If
If cbolevel.Text = "O-level" Then
Olevel()

ElseIf cbolevel.Text = "A-level" Then

Alevel()
ElseIf cbolevel.Text = "ZJC" Then
ZJC()

End If
End Sub

Private Sub txtstuname_MouseHover(sender As Object, e As EventArgs) Handles txtstuname.MouseHover

 txtstuname.Clear()
End Sub

Sub delete()
'if the level is ZJC it will delete from the ZJC table
If cbolevel.Text = "ZJC" Then
Try
conn.Open()
If MsgBox("do you want to delete", vbYesNo) = vbYes Then
Dim cmd As New OleDb.OleDbCommand("delete from ZJC where Name=@Name", conn)
cmd.Parameters.Clear()
cmd.Parameters.AddWithValue("@Name", txtstuname.Text)
i = cmd.ExecuteNonQuery
If i > 0 Then
MsgBox("welldone", vbInformation)
Else
MsgBox("error", vbCritical)
End If
End If
Catch ex As Exception
MsgBox(ex.Message)

End Try
clear()
'if the level is Olevel it will delete from the Olevel table
ElseIf cbolevel.Text = "O-level" Then
Try
conn.Open()
If MsgBox("do you want to delete", vbYesNo) = vbYes Then
Dim cmd As New OleDb.OleDbCommand("delete from Olevel where Name=@Name", conn)
cmd.Parameters.Clear()
cmd.Parameters.AddWithValue("@Name", txtstuname.Text)
i = cmd.ExecuteNonQuery
If i > 0 Then
MsgBox("welldone", vbInformation)
Else
MsgBox("error", vbCritical)
 End If
End If
Catch ex As Exception
MsgBox(ex.Message)

End Try
clear()
'if the level is Alevel it will delete from the Alevel table
ElseIf cbolevel.Text = "A-level" Then
Try
conn.Open()
If MsgBox("do you want to delete", vbYesNo) = vbYes Then
Dim cmd As New OleDb.OleDbCommand("delete from Alevel where Name=@Name", conn)
cmd.Parameters.Clear()
cmd.Parameters.AddWithValue("@Name", txtstuname.Text)

i = cmd.ExecuteNonQuery
If i > 0 Then
MsgBox("welldone", vbInformation)
Else
MsgBox("error", vbCritical)
End If
End If
Catch ex As Exception
MsgBox(ex.Message)

End Try
clear()
End If
conn.Close()
dataload()
End Sub
Private Sub txtsur_MouseHover(sender As Object, e As EventArgs) Handles txtsur.MouseHover
txtsur.Clear()
End Sub

'codes for the buttons

Private Sub btnAlevel_Click(sender As Object, e As EventArgs) Handles btnAlevel.Click
With Alevell
.TopLevel = False
GunaGradientPanel3.Controls.Add(Alevell)
.BringToFront()
.Show()
End With
GunaLabel1.Text = "A-level"
Alevell.dataload()
GunaGradientPanel3.Controls.Remove(Statistics)
GunaGradientPanel3.Controls.Remove(view)
GunaGradientPanel3.Controls.Remove(ZJCForm)
End Sub

Private Sub btnolevel_Click(sender As Object, e As EventArgs) Handles btnolevel.Click

With view
.TopLevel = False
GunaGradientPanel3.Controls.Add(view)
.BringToFront()
.Show()
End With
GunaLabel1.Text = "O-Level"
GunaGradientPanel3.Controls.Remove(Alevell)
GunaGradientPanel3.Controls.Remove(ZJCForm)
GunaGradientPanel3.Controls.Remove(Statistics)
view.dataload()
End Sub

Private Sub btnstatistics_Click(sender As Object, e As EventArgs) Handles btnstatistics.Click

dataload()
With Statistics
.TopLevel = False
GunaGradientPanel3.Controls.Add(Statistics)
.BringToFront()
.Show()
End With
GunaLabel1.Text = "Statistics"
 GunaGradientPanel3.Controls.Remove(view)
GunaGradientPanel3.Controls.Remove(ZJCForm)
GunaGradientPanel3.Controls.Remove(AlevelEdit)
End Sub

Private Sub btnstudents_Click(sender As Object, e As EventArgs) Handles btnstudents.Click

dataload()
GunaGradientPanel3.Controls.Remove(Alevell)
GunaGradientPanel3.Controls.Remove(Statistics)
GunaGradientPanel3.Controls.Remove(view)
GunaGradientPanel3.Controls.Remove(ZJCForm)
End Sub
'back nutton
Private Sub GunaCirclePictureBox2_Click(sender As Object, e As EventArgs)
Me.Hide()
login.Show()
End Sub
Private Sub btnexit_Click(sender As Object, e As EventArgs)
Application.Exit()
End Sub
Sub clear()
txtstuname.Clear()
txtsur.Clear()
End Sub
Private Sub btndel_Click(sender As Object, e As EventArgs) Handles btndel.Click
delete()
End Sub

Private Sub btnzjc_Click(sender As Object, e As EventArgs) Handles btnzjc.Click

With ZJCForm
.TopLevel = False
GunaGradientPanel3.Controls.Add(ZJCForm)
.BringToFront()
.Show()
End With
GunaLabel1.Text = "ZJC"
GunaGradientPanel3.Controls.Remove(view)
 ZJCForm.dataload()
GunaGradientPanel3.Controls.Remove(Statistics)
GunaGradientPanel3.Controls.Remove(AlevelEdit)
End Sub
Private Sub GunaDataGridView1_CellContentClick(sender As Object, e As DataGridViewCellEventArgs)
Handles GunaDataGridView1.CellContentClick
txtstuname.Text = GunaDataGridView1.CurrentRow.Cells(0).Value
txtsur.Text = GunaDataGridView1.CurrentRow.Cells(1).Value
cbolevel.Text = GunaDataGridView1.CurrentRow.Cells(2).Value
End Sub
Private Sub btnaccount_Click(sender As Object, e As EventArgs) Handles btnaccount.Click
Create.Label1.Text = "form1"
Create.Show()
Create.active()
Create.gbox.Visible = False
End Sub
Private Sub GunaCircleButton1_Click(sender As Object, e As EventArgs) Handles GunaCircleButton1.Click
Me.Hide()
login.Show()
End Sub
Private Sub btnexit_Click_1(sender As Object, e As EventArgs) Handles btnexit.Click
Application.Exit()
End Sub
Private Sub btnacc_Click(sender As Object, e As EventArgs) Handles btnacc.Click
View_Accounts.Show()
End Sub
Dim sex As String
Private Sub rbtnFemale_CheckedChanged(sender As Object, e As EventArgs) Handles
rbtnFemale.CheckedChanged
If rbtnFemale.Checked = True Then
sex = "Female"
Else
End If
End Sub
Private Sub rbtnmale_CheckedChanged(sender As Object, e As EventArgs) Handles rbtnmale.CheckedChanged
If rbtnmale.Checked = True Then
sex = "Male"
 Else
End If
End Sub
'searching from the Alevel table
Sub search()
Try
conn.Open()
GunaDataGridView1.Rows.Clear()
Dim cmd As New OleDbCommand("select * from Alevel where `Name` like `search` or `Surname` like
`search` ", conn)
cmd.Parameters.Clear()
cmd.Parameters.AddWithValue("search", txtsearch.Text)
dr = cmd.ExecuteReader
While dr.Read
GunaDataGridView1.Rows.Add(dr.Item("Name"), dr.Item("Surname"), dr.Item("Level"), dr.Item("Sex"))
End While
dr.Close()
Catch ex As Exception
MsgBox(ex.Message)
End Try
conn.Close()
End Sub
Private Sub txtsearch_TextChanged(sender As Object, e As EventArgs) Handles txtsearch.TextChanged
search()
search2()
search3()
End Sub
Private Sub GunaCircleButton2_Click(sender As Object, e As EventArgs) Handles GunaCircleButton2.Click
search()
search2()
search3()
End Sub
'searching from the Olevel table
Sub search2()
Try
conn.Open()
GunaDataGridView1.Rows.Clear()
 Dim cmd As New OleDbCommand("select * from Olevel where `Name` like `search` or `Surname` like
`search` ", conn)
cmd.Parameters.Clear()
cmd.Parameters.AddWithValue("search", txtsearch.Text)
dr = cmd.ExecuteReader
While dr.Read
GunaDataGridView1.Rows.Add(dr.Item("Name"), dr.Item("Surname"), dr.Item("Level"), dr.Item("Sex"))
End While
dr.Close()
Catch ex As Exception
MsgBox(ex.Message)
End Try
conn.Close()
End Sub
Sub search3()
Try
conn.Open()
GunaDataGridView1.Rows.Clear()
Dim cmd As New OleDbCommand("select * from ZJC where `Name` like `search` or `Surname` like
`search` ", conn)
cmd.Parameters.Clear()
cmd.Parameters.AddWithValue("search", txtsearch.Text)
dr = cmd.ExecuteReader
While dr.Read
GunaDataGridView1.Rows.Add(dr.Item("Name"), dr.Item("Surname"), dr.Item("Level"), dr.Item("Sex"))
End While
dr.Close()
Catch ex As Exception
MsgBox(ex.Message)
End Try
conn.Close()
End Sub
End Class

User Documentation
Installing the system
Select the folder entitled, “Application Files” double click to open it

If folder is opened, click on setup in the folder as shown below:

When it is run it shows the installation process, so that the user starts to uses the system and it is
shown below:

Click on install to start the installation process .it will show a progress bar as shown below:

Automatically a desktop icon will appear

The system automatically creates a desktop icon for ease of use, to save time compared to
searching around the whole computer. And if you click it you would have opened the system.

Running the system/ Navigation the system

If you an admin
Click O
level

Click A
level
If you a teacher
Click
Statistics

Click O
level
Click A
level

Click ZJC
Section D: Testing and Evaluation
User Testing

Testing for standard extreme and abnormal/invalid data

This test was executed to check weather then system’s information validation was effective and
fortunately it provided positive results. This implies that if one enters in correct user credentials
the system will display error messages as follows:

Testing for abnormal data

Test Test Data Expected Results Pass/

Case Fail

LOG To check whether the system - Display error reporting Pass

IN can login when a wrong message notifying that the
username or password is user’s credentials are incorrect
entered

To see if system continues - Display error message Pass

with an empty field that in notifying the user to fill in the
supposed to be filled empty field

To check whether system can - Display all the required Pass

search a device in the details
database

To check whether the system Error message stating that the Pass
can accept data that in beyond entered data is not with the
the limit of the input field range of expected length
length
Error Messages
When a user tries to login without typing in some or any credentials the above message will be
displayed giving him / her another chance to try again.

Test for invalid/ abnormal data

If a user enters a password that is less than 4 characters on creating a new account
Ease of use testing
Usability is defined as the degree to which people (users) can perform a set of required tasks. It
is the product of several, sometimes conflicting, design goal.

Functionally correct
The primary criterion for usability is that the Report processing System correctly performs the
functions that the users need, entering marks, calculating marks, printing a report and keeping
record of the marks. If the system does not allow the users to do this, it would be rendered
useless.

Efficient to use
Efficiency can be measured by the time or actions required to perform a task, for example
transaction time with regards to user details retrieval from the database via the web interface
should be reasonable. This is one of the reasons it has been decided that Microsoft Access
database would be the choice of database to be used as procedures that are faster tend to be more
efficient.

Easy to learn
ease of learning determines how quickly new users can learn to accurately perform a task
procedure, for example the steps taken for a particular user to open the system should be kept to
an absolute minimum as research evidence suggests that the fewer steps a procedure contains,
the easier it is to learn. The layout of the controls in the system is provided in such a way that it
accommodates a user with less experience and even a novice user. The system provides guide to
the user in form of notification and error reporting message which makes it easy to the user to
learn and understand the system.

Error tolerant
Error tolerance is determined by how well errors are prevented, how easily they are detected and
identified when they occur, and how easily they are corrected once they are identified. The
Report processing system and the school’s record keeping process would be automated and
minimize the number of manual entries when doing the student’s inspection process in order to
reduce input errors, extensive input validations will be performed within the browser at runtime
without even accessing the database in the server.
Effectiveness
The effectiveness and learnability of the system, is important as it should be more effective than
the previous manual paper based system. This was assessed by asking the user to perform some
tasks. The user was given some sample data to perform the tasks on the data. Results indicate
that the user is able to navigate and perform the tasks relatively easily. For example, registering
inventory. It is also shown that the user is able to generate reports and extract required
information using queries.

However, issues which arose include that the times are not exceptionally quick, however this
does not suggest that the system is not effective, on observing it can be seen that the user is not
particularly a speedy computer user. The user became familiar with the system fairly quickly
which does suggest sufficient levels of learnability.
Evaluation of the System
Achievements
The analyst achieved the create system responsible for ensuring that the student marks are more
accurately when issued to the student or parents. Makes it easy to recognize a student whose
report hasn’t been processed yet rather than the old style of announcing if one hasn’t received
their reports yet. The analyst achieved termination procedures which is responsible for deleting
the Student from the system when he/she is no longer part of the institution. This seeks to meet
the objective of maintaining an updated database that shows the current information by adding
newly received students and deleting outgoing students. Security objectives have been met by
using log in username and password for each and every user. This security measure prevents
unauthorized users from logging-into the system. The system also promotes security through the
use of the back-up facility in case of corruption or accidental loss of data.

The system analyst achieved user-friendliness. Consistent user interfaces enable the application
to be easy to use, look tidy and indirectly it will increase user satisfaction on using the system.
Manual input is only required on the reception of new Student. Effort free navigation was
achieved which is one of the key requests to ensure that the system is relatively easy to use. The
user should easily be able to go back to the previous screen and there should be easy access to
the main menu from anywhere in the system to avoid confusion. The objective of developing a
usable and user friendly is achieved.

The objective of providing a full range of reports that will satisfy informational requirements at a
more reinforced speed is achieved. The system offers a reinforced response to time. Less time is
consumed in all the processes to be done in the new Report Processing System. A lot of time was
being taken in searching a student when a request is made. With the new system it is very fast to
compile reports, search and update all the records quickly.

The performance of the system has reinforced at is considered to be good as the response time of
user request is definitely instant.

In achieving the objective of capturing all the details of Student Marks, validation techniques
have been embedded in the system. System design provides validation features to minimize the
invalid input such as percentages if they are less than or greater than 100 an error will appear.
Error rates had been reduced because there are various validations being done to ensure that the
information entered is correct and matches the database attributes data type.

Limitations
The system can only execute on Microsoft Windows operating system therefore it is
incompatible with any other operating system so far. A considerable manual effort is required
especially during data capture when new Students are received at the school.

Opportunities for Future Developments

If only the opportunity is granted in the future, the system analyst needs to develop the system
using other software like Linux. Mackintosh, Microsoft suite2007- 2016 and Vb.net and which
also execute on newer OS such as latest versions of Microsoft Windows which windows 11.

If given more time, the analyst will improve the networking capacity of the system to enable
many users to use the system concurrently. Therefore, the network usage provides a capability to
cater for a larger organization.

Security measures will be reinforced; the system will also incorporate an activity log monitoring
for the administrator. This is usually applicable when each department gets at least a computer
for checking in its staff to reduce the queuing at the reception idea. This security measure will
help the admin to track who did not attend to what and when the absenteeism was made.

Furthermore, other possible enhancements which could be made, is to complete development of

the administrative feature. It will be an easier way to handle check in or check out activities done
by a security tag than those of typing since some people are naturally lazy.
Appendix
Interview Question and Answers
1. Do you have any standing backup for the mark schedule?
Answer: No
2. Why don’t you have a standing backup for the mark schedule?
Answer: It laborious because we use the pen and paper system
3. I heard that a student can temper with his/her mark on the mark schedule?
Answer: Yes it rarely happens
4. What will be done with those who does not submit their report books in time?
Answer: We do not write their reports
5. What other use do you take the login details for?
Answer: We do not have any use for them
6. Do you think it is ideal to introduce a new computerized system that provides
summarized information for the admin?
Answer: I don’t think so the system is easy
7. I heard that when a teacher miscalculates a student’s marks nothing is done about it?
What do you suggest for a solution?
Answer: Being more precautious
8. What do you do if the mark schedule is lost? Do you have any alternative?
Answer: We redo the calculations

Questionnaire Question and Answers

1. How long have you been using the existing system?
Answer: Since the school was founded
2. Who does the calculations of marks for the report?
Answer: Class teacher
3. Do you still use the pen and paper system?
Answer: Yes
4. Do you have the problem were by students loses their report books
Yes No
5. Do you find it ideal to replace with a new computerized system?
Yes No
6. Do you have a computer skill at any level?
Yes No
7. Are there any computers at your school?
Yes No