CERTIFICATION

I declare that the work in this project titled “ACADEMIC RECORD SYSTEM (ARS)” that
based at secondary school is submitted to Department of Computer Science Studies under
Faculty of Science and Technology for the development of Academic record management
system as the requirement for award of the diploma of information technology

Major Supervisor Internal Examiner

Name: …………………… Name ……………………..

Signature ………………….... Signature………………….

Date……………………………… Date ………………………

 DECLARATION
I am, Aloisi Lusenge declare that this is my own original work and that has not been presented
and will not be presented to any other university for a similar or any other diploma award.

Signature: ……………… Date………………….

SUPERVISOR: DR, ENG.MORICE DAUD

Signature: …………………………. Date: ………………….

 ACKNOWLEDGEMENT
I thank more to Almighty God who give power and ability to prepare this project final year
report. Preparation of this project it is not easy but because of GOD is completed and delivers the
intended objective of the project. This report is the product of full cooperation, assistance and
encouragement from a number of people without them it could not have been made successfully.
For sure they are many and it difficult to mention them all but some deserved to be mentioned. I
wish to acknowledge many colleagues, friends who helped me to make this report successful.
First, I thank my Supervisor Dr, Eng, and Morice Daud for all the guidance, expertise and
encouragement that he has provided during the process of defining statement of the problem,
during implementation of the system and preparation of the report.

Finally, I thanks to my friends, Yohana Asheri, Sharifu Jamal, and Vicent Joshua. Their valuable
contributions are remains in the memory and also thanks to them.
 LIST OF ABBREVIATIONS

AR Academic Records

SS-AR Secondary School-Academic Records

ARS Academic Record System

CSS Cascading Style Sheet

DBMS Database Management System

HTML Hypertext markup language

PHP Hypertext Preprocessor

SDLC System Development Life Cycle

UML Unified Modeling Language

 ABSTRACT
In developing the Secondary School - Academic records, agile methodology used as technique
for accomplishing this system. The reasons to why I decided to develop this system is because
most of the Tanzanian secondary schools don’t have the system that enable the student’s parent
to get academic record of their student especially through normal message.
And the aim of the system is to ensure the student to be familiar with the technology and the
parent to get the accurate academic report of their student.

UML diagrams used in system design such as use case, class diagram, activity diagram and
sequence diagram.
 TABLE OF CONTENTS

CERTIFICATION............................................................................................................................i
DECLARATION.............................................................................................................................ii
ACKNOWLEDGEMENT..............................................................................................................iii
LIST OF ABBREVIATIONS........................................................................................................iv
ABSTRACT....................................................................................................................................v
TABLE OF CONTENTS...............................................................................................................vi
LIST OF TABLE............................................................................................................................ix
LIST OF FIGURE...........................................................................................................................x
CHAPTER ONE..............................................................................................................................1
INTRODUCTION AND PROBLEM DESCRIPTION...................................................................1
1.1 Introduction................................................................................................................................1
1.2 Background................................................................................................................................1
1.3 Problem statement.....................................................................................................................1
1.4 Project objective........................................................................................................................2
1.5 Specific objective.......................................................................................................................2
1.6 Project scope..............................................................................................................................2
CHAPTER TWO.............................................................................................................................3
LITERATURE REVIEW................................................................................................................3
2.1 Topic review..............................................................................................................................3
2.2 Domain Review.........................................................................................................................3
2.3 Problem Conclusion...................................................................................................................3
CHAPTER THREE.........................................................................................................................4
REQUIREMENT ELICITATION AND SYSTEM ANALYSIS...................................................4
3.1 Introduction to requirement and elicitation...............................................................................4
3.2 Fundamental approaches to requirements elicitation:...............................................................4
3.2.1 Observation.............................................................................................................................4
3.2.2 Interview.................................................................................................................................4
3.2 System functionalities................................................................................................................5
3.4 Non-Functional Requirements...................................................................................................6
3.5 System analysis:.........................................................................................................................7
3.5.1 Use case diagram....................................................................................................................7
CHAPTER FOUR.........................................................................................................................10
SYSTEM DESIGN........................................................................................................................10
4.0 Introduction to System Design................................................................................................10
4.1 Methodology............................................................................................................................10
4.2 Database design.......................................................................................................................11
4.3 User interface design...............................................................................................................12
CHAPTER FIVE...........................................................................................................................13
SYSTEM IMPLEMENTATION...................................................................................................13
5.1 Introduction to Implementation...............................................................................................13
5.1.1 System assumption...............................................................................................................13
5.2 Development tools...................................................................................................................14
5.2.1 HTML 5................................................................................................................................14
5.2.2 CSS 3....................................................................................................................................14
5.2.3 Bootstrap...............................................................................................................................14
5.2.4 Hyper Text processor (PHP).................................................................................................15
5.2.5 MySQL database..................................................................................................................15
5.2.6 XAMPP.................................................................................................................................15
5.2.7 JavaScript..............................................................................................................................15
5.3 Development Platform.............................................................................................................15
5.4 Database Management System................................................................................................15
5.5 Implementation of security services........................................................................................16
5.6 Back end and database implementation...................................................................................16
5.6.1 Database implementation......................................................................................................16
5.6.2 Back-end implementation.....................................................................................................16
5.7 Front end and User Interface implementation.........................................................................17
5.8 System Testing and Evaluation...............................................................................................18
5.8.1 Unit testing............................................................................................................................18
5.8.2 Component testing................................................................................................................18
5.8.3 System design.......................................................................................................................19
5.8.4 Test case................................................................................................................................19
CHAPTER SIX..............................................................................................................................20
CONCLUSION AND RECOMMENDATIONS..........................................................................20
6.0 Introduction..............................................................................................................................20
6.1 Achievements of research objectives.......................................................................................20
6.2 Future work..............................................................................................................................20
6.3 Conclusion and recommendations...........................................................................................20
REFERENCES..............................................................................................................................21
 LIST OF TABLE
Table 1.3: Describe the use case of Academic Record System (ARS)...........................................8
Table 2.5: Hardware requirements................................................................................................13
Table 3.5: Software requirements..................................................................................................14
 LIST OF FIGURE
Figure 1.3: Academic record system...............................................................................................9
Figure 2.4: Agile Lifecycle Model...............................................................................................11
Figure 3.4: Entity-Relationship Diagram......................................................................................12
Figure 4.4: Front interface design of the system...........................................................................12
Figure 5.5: Database implementation tables..................................................................................16
Figure 6.5:After Academic Officer Login.....................................................................................17
Figure 7.5: Students after Login....................................................................................................17
Figure 8.5: Teachers after Login...................................................................................................18
 CHAPTER ONE
INTRODUCTION AND PROBLEM DESCRIPTION
1.1 Introduction
Secondary School-Academic Records (SS-AR) this is system that is used to manage and monitor
student academic issue, aim of this system is to manage students result and able to send result to
parent through normal message.
Secondary School-Academic Records (SS-AR) is the system that having the phase that enables
teachers(staff) to upload student subject results to the system, and the student can login to the
system after being registered by admin and access his/her results if and only if the results have
been verify by academic officer
After that system offer the service that enable academic officer to send the result of the student to
his/her parent in form of normal message, this will need availability of the internet for academic
officer to send student academic report to his/her parent.
Academic officer will be able to manage and monitors all activities done to the system, our
system having ability to provide information where needed at all times.
1.2 Background
Due to the lack of a formal system to most of Tanzanian secondary school that manage student
result and manage their academic issue and also end to send student report to their parent. I have
come up with secondary school - academic records system for managing this challenge.
The system has four levels of users which are academic officer, staff (teacher), parent and
student. Academic officer in the system can register student, register staff (teacher), verify
student result, check list of registered student and is only one who send the student report to the
parent.
Staff (teachers) is the one who is responsible for uploading student’s subject result to the system
and also can edit the student result. Student login to the system and access their result and access
only if academic officer has already verify student result uploaded by staff (teachers).
1.3 Problem statement
At most secondary’s school in Tanzania the students gets results manually .The students gets
results through papers and asked to deliver their results to their parents. Because of this most of
the student takes it as an advantage to them to liar their parents if have scored badly or to do not
report any information to the parent.
Due to manual system lead of the following problems
i. Time wastage (It is performed manually and takes a considerable amount of time and
manpower
ii. Not accurate information
iii. Low safety (Vulnerable of forgery)
iv. Unreliable, since paper records might get lost.
v. Some parent not get feedback of their student results(fails to know performance their
student at school)
1.4 Project objective
1.4.1 Main objective
i. The main aim of developing this web base application is that to have academic system
at secondary school that make a link between school and student’s parent in case of
academic issue through normal message, so that the parent to be familiar with correct
academic record of their student’s at school.
ii. Organization (school) to keep student academic information.
iii. Student to be familiar with technology.
1.5 Specific objective
i. To save student parent to get accurate academic record of their student at school.
ii. This system is designed to save the time and reduce the paper work.
iii. Proposed system is used to reduce confusion at the time of processing feedback.
1.6 Project scope
System will store student results and academic information system will work in any Tanzania
secondary school.
1.7 Limitation of the system
i. Security Limitations (student should login if and only is already have username and
password that is given after registered by system academic officer)
ii. If teacher forget password, he supposed to contact system academic officer.
iii. Any registration done by system academic officer.
iv.
 CHAPTER TWO
LITERATURE REVIEW
2.1 Topic review
Currently many secondary schools in Tanzania use manual/local system in case of academic
issue supervision. This local system of academic issue is very challenging because it incurs
problems that may be solved if the system would be changed to be online/computer based.
Introducing secondary school academic record system will large extent as a suitable solution to
the problems. We introduce the idea of secondary school academic record system to schools in
Tanzania which will allow student’s parent to have a link with the school that enable parent to
get accurate academic information of their students at school.
2.2 Domain Review
The academic record system is developed to the Tanzania secondary school but there some
secondary that have already have the system like this but the most exist system based to the
school does not ensure the parent get the record of academic record of their student at school.
And the system of academic record offer that the student’s parent get result of their children at
school through normal message, and the parent read that normal message which include result of
his/her student without using bundle.
Also this system make link between school and parent, and makes to get correct academic
information of their student.
2.3 Problem Conclusion
Problem of the most Tanzania secondary school don’t have the system that simplify work
academically because of this and other factors like this cause academic of most Tanzania
secondary school to be poor .Teacher become more tired in case of keeping student record.
Through presence of academic record system enable to reduce some kind of activities to teacher
and ensure academic improvement.
 CHAPTER THREE
REQUIREMENT ELICITATION AND SYSTEM ANALYSIS
3.1 Introduction to requirement and elicitation
Requirement elicitation is the process of discovering, reviewing, documenting, and
understanding the user's needs and constraints for the system [Somerville and Sawyer, 1997].
Requirement elicitation is the most important part in software development according to
[Leffingwel, 2000] we need requirement elicitation due to many reasons such as knowing what
problems to be solved and recognizing system boundaries, identifying who are the stakeholders
also to recognizing the goal of system is targeted to be achieved.
3.2 Fundamental approaches to requirements elicitation:
To take this project to its accomplishment, two methods for data collection may be used. One is
observation. This is looking and watching at where, what and how people do their tasks related
to examinations. Another is an interview. This is a face to face conversation aimed at collecting
some information from stakeholders (Sommerville, 2016).
3.2.1 Observation
Observation is a method of data collection used to get data through sight and sensing where the
observer actually stays in everyday life of the subject of study or informant. The observer can
engage in active and inactive manner. The observation technique that can be used to understand
operational processes and help derive requirements for system to support these processes.
(Sommerville, 2016). This method is used to acquire system requirements by observing
operations and activities where there is the need of a solution to a specific problem. By
observation we discover that, Tanzania secondary school has no system that enables the school
to store academic record and make a link with the parent.
3.2.2 Interview
Interview is an activity performed to directly obtain information by asking the software designer
and interviewees (Ramdhani, 2018). According to Scott and others, “an interview is a purposeful
exchange of ideas, the answering of questions and communication between two or more
persons”. Bingham and others define an interview as a ‘conversation with a purpose.” The
success of the interview depends on the skills the software designer has in gaining the trust of
interviewees. Data are collected from the interview by asking some set of question based on what
one want to know from the problem. In this project, the main interviewees are stakeholders that
are students, teachers, and parent, the questions are based on the experience of the local
examination systems, the difficulties that they face and how they might interact with the new
system. The questions are
i. Is it possible to develop a system that can make a link with parent in case of academic
issues?
ii. To what extend does the developed system be user friendly and enable applicant to use it
smoothly?
iii. How does the system be able to input, process and gives output information without any
technical problem?
3.2 System functionalities
The purpose of this chapter is to define the requirements gathering process used to elicit
requirements from the system’s stakeholders, to define the overall vision and goals of this new
product, and to list those functional and non-functional requirements that are essential to the
success of this system. The requirements included in this chapter are categorized in two groups
namely, User requirements and System requirements.
These are the requirement that the system is expected to perform to meet the users’ expectation.
These requirements include functions that user wants the system to perform and how the system
is going to be and the constraints on respected services to be offered by the system. These
requirements can be grouped into two categories; Functional requirements and Non-Functional
requirements
The system defines four levels of users who are responsible in interacting the Secondary School
Academic Record System. These levels are derived from requirement specification. These users
are; the Academic officer, staff (teachers), parent and the Student.
The academic officer
The academic officer will have to login by the correct credentials. He/she will be able to.
i. Login
ii. Register students
iii. Check registered students
iv. Register Staff (teacher)
v. Verify student results
vi. Send student result report to their parents
Student
i. The student will have to login by the correct credentials after registered by academic
officer and can login if and only if the academic officer has already verify his/her result
otherwise can’t login to the system.
ii. logout in the system is another function
Staff (teacher)
Teacher will be able to Login, Upload student subject result, Edit score, Update score, Logout
Functional requirements
Functional requirements deal with what the system should do or provide for users. The
functional requirements of Secondary School - Academic Record System are.
i. Allow student to be registered by academic officer
ii. Allow student to login to the system and check his/her result, this done after academic
officer has already verify that result.
iii. Allow academic officer to login in system and register new student ,register
staff(teacher),verify student result, check list of registered student and is only one who
system offer service to him to send student result report to parents .
iv. System allows staff (teacher) to login in system and upload student subject result.
v. Systems enable parents to receive the result of their children through mobile phone by
using normal messages.
3.4 Non-Functional Requirements
This non-functional requirement is a general because all system must have. According to book of
information technology project (IT project) and the book of software engineering fourth edition
(2008).
Secondary School Academic Record (SSAR) system will be on a server with high-speed internet
capability. This system developed assumes that the use of tools such Mozilla fire, opera mini,
internet explorer for displaying the web pages and the speed to which the web page will display
depends on the hardware used rather than the characteristic of this system and will be run on user
PC contains database. We look on this constraint on the development process, standards,
reliability, and response time and storage requirements.
Usability
The system will be user friendly, that, it will easy for user to interact. Also, the system will be
designed in such a way that it is able to accommodate changes. The system also responsive with
different device and browser platforms in market.
User interface and Human factors
Considering the fact that the system is to be used with both literate and illiterate computer users,
hence it is designed with very interactive interface to enhance all types of users. The system is
composed by responsive interfaces that enable users with different devices such as computers,
tablets and mobile phones to have good interface without losing any details from the system.
Security
Secondary School Academic Record System uses Authentication as one of security measure so
that no unauthorized user should be able to login into the system. Only users having a password
and username are able to view and manage system’s operations.
Availability
Secondary School Academic Record System is developed and designed as a Web system, which
operate in networking (Internet) environment during academic officer want to send result to
parent otherwise the system offer service even if no internet.
3.5 System analysis:
These are the requirements that should be met for the system to operate since they may be
supporting application or infrastructures that are required for the system to be adopted. The
following are the system requirements for Academic Record System;
i. Network – To enable system academic officer to send student academic report to his/her
parent and improve availability aspects around the organization compound where system
needed to be accessed.
ii. Web browser – Hosting Platform for handling user interfaces for the system, inputs and
outputs of the system from and to user respectively.
iii. Web server – For processing and responding to user request from the system.
iv. Database server – For hosting the database and its contained data to accessed.
3.5.1 Use case diagram
Use case describes sequence of events for the users who use system functionality to complete
various processes (Sommerville, 2016). Use case diagrams, which show the interactions between
a system and its environment. Use case is used in order to demonstrate the system’s behavior and
how the user will interact with the system. There are four actors which interact with the
Academic Record System (ARS) which are system academic officer, Staff (teacher), parent and
student.
Table 1.3: Describe the use case of Academic Record System (ARS)

ACTORS DESCRIPTION
System academic officer Login
Register students
Check registered students
Register Staff (teacher)
Verify student results
Send student result report to their parents
Change password
Student Login
Logout
View result
Staff (teacher) Login
Upload student subject result
Edit score
Update score
Logout
Figure 1.3: Academic record system
 CHAPTER FOUR
SYSTEM DESIGN
4.0 Introduction to System Design
System design is the practice of defining the basics of a system such as the architecture, modules
and components, the different interfaces and the information that goes through that system. It is
meant to fulfill specific needs and requirements of a business through the engineering of a
coherent and well-running system.
Systems design involves systematic approach to the design of a system. It can be a bottom-up or
top-down approach, but either way the process is systematic where in it takes into account all
related variables of the system that needs to be created from the architecture.
4.1 Methodology
System development methodology is a framework that is used to structure, plan, and control the
process of developing an information system. It also is a methodology for systematically
organizing the best ways to develop systems efficiently. It includes, for example, descriptions of
work to be performed at each stage of the development process and drafted documents. To get to
the design and implement an information system, there is a need to have methodological
approach in order to meet the time against physical and human constraints. The Agile Lifecycle
Model approach for software development was employed in the development of this system.
Agile methodology is a type of project management process, mainly used for software
development, where demands and solutions evolve through the collaborative effort of self-
organizing and cross-functional teams and their customers. Agile SDLC model is a combination
of iterative and incremental process models with focus on process adaptability and customer
satisfaction by rapid delivery of working software product. Agile Methods break the product into
small incremental builds. These builds are provided in iterations. Each iteration typically lasts
from about one to three weeks. Iteration involves cross functional teams working simultaneously
on various areas.
The following stages are included the Agile project methodology.
i. Planning
ii. Requirements Analysis
iii. Design
iv. Coding
 v. Unit Testing and
vi. Acceptance Testing

Figure 2.4: Agile Lifecycle Model

4.2 Database design
Is the organization of data according to a database model, the designer determines what data
must be stored and how the data elements interrelate. With this information, they can begin to fit
the data to the database model. (Teorey, T.J., Light stone, S.S., et al., (2009).)
The designing of the database reflects the functional requirements collected in requirement
elicitation. Thus, the system requires various entities such as student, staff (teacher), academic
officer and parent.
 Fig
ure 3.4: Entity-Relationship Diagram
4.3 User interface design
The designing of user interface comprises of the pages and activities which enable the user to
interact with the system. Thus, the user interface must be simple and well designed to make sure
the user does not get difficulties when interacting with the system or to perform some tasks on
the system. The following are sample interfaces adapted in system design.

Figure 4.4: Front interface design of the system

 CHAPTER FIVE
SYSTEM IMPLEMENTATION
5.1 Introduction to Implementation
This chapter describes the implementation and evaluation processes towards the system
development. In terms of implementation, the development environment, tools, development
platform, database used and levels of system users are also discussed. The designs are translated
into code. Computer programs are written using a conventional programming language or an
application generator. Based on the system designed the programming language is chosen.
System implementation is the development, installation and testing of system components and
delivery of that system components and delivery of that system into production (Jianget al.,
1996). The implementation of the system requires various tools upon completion and testing.
During implementation of the project different scenarios are made into assumption in order to
meet system objective.
5.1.1 System assumption
i. System will have a database for storing various user accounts details including sample
images and documents.
ii. The student details or information submitted will be used to identify student or a user.

Table 2.5: Hardware requirements

Hardwar Description
e
Processor Intel Centrino 1.5 Ghz Processor or higher or other equivalent
processors
Memory At least 512 MB Recommended: 1GB or more
Hard disc At least 80GB (Does not affect system performance)
Other Organization network
 Table 3.5: Software requirements

Software Description
Operating System At least Microsoft Windows 7
Web Server At least 2.4.29
Relational Database Management System At least MySQL 5.0.45
Internet Browser Firefox, chrome, internet explorer and others
Programming languages PHP and SQL
Web design and Development tool Xampp and visual studio code
Graphical User Interface (GUI) HTML and Bootstrap
5.2 Development tools.
Refers to different tools used in the development of the System upon completion and testing.
5.2.1 HTML 5
HTML, acronym for Hypertext Markup Language, is a markup language used to describe the
formatting of text in a document. It is useful in the sense that it allows text to be structured
according to its purpose, namely as a heading, paragraph and so on. This is accomplished by
writing the HTML in ‘tags’ that describes to the web browser how the text is to be displayed. A
scripting language such as PHP and JavaScript can be easily embedded in HTML to enhance the
functionality of HTML.
5.2.2 CSS 3
It is a style sheet language used for describing the presentation of a document written in
a markup language. Along with HTML and JavaScript, CSS is a basis technology used by most
system to create visually engaging pages, user interfaces for web applications, and user
interfaces for many mobile and desktop applications. CSS is designed primarily to enable the
separation of document content from document presentation, including aspects such as
the layout, colors, and fonts.
5.2.3 Bootstrap
Bootstrap is a pre-defined CSS platform for developing responsive web designs. It is
customizable platform which enables creations of own classes depending on the preferences
apart from what have already pre-defined by bootstrap itself. This used on creating hover able
table which display data.
5.2.4 Hyper Text processor (PHP)
This is a server-side scripting language which used to develop the connections between the
presentation view or html page and database where users will be able to send data into a database
also to fetch the data that are available in the database.
5.2.5 MySQL database
This is an open source relational database management system, it is used to create and
maintaining data of the system, the purpose is to store the data of the system. This system uses
Marian DB which is among of the packages of xampp software which support databases
operations. MySQL is a relational database management system (also known as an SQL
Database Server), which is widely used around the globe since it is being open-sourced. Most
SQL servers provide reliability but not ease of use unlike MySQL. When using JSP to develop a
system, only supports a MySQL database connection as both JSP and MySQL are strongly
connected using JDBC Drivers.
5.2.6 XAMPP
This is a free software and open-source cross-platform web server solution package developed
by Apache HTTP server, Marian DB and database. It interprets for scripts written in the PHP and
Perl programming languages. This software is used to execute PHP as a server scripting
language basically is a running environment for PHP.
5.2.7 JavaScript
Java Script is the customer side scripting dialect utilized amid the improvement stage. In specific
circumstances, JavaScript must be utilized rather than PHP. JavaScript used in my system in alert
and popup in different actions on the system.
5.3 Development Platform
The system was developed on windows 10 professional 64bits operating system where sublime
used on coding implementation process to ensure that the system development is conducted well
under support of other tools in system development.
5.4 Database Management System
MySQL is a relational database management system which is widely used around the globe and
it is an open-source. This system uses Marian DB which is MySQL database supported by
xampp, one of its packages which interacts with the user interfaces through PHP server scripting
language to perform the system functionalities.
5.5 Implementation of security services.
i. The system has assurance of security to ensure that unauthorized users cannot access the
system and only authorized users can access the system by using username and password.
The use of SHA1 function has been implemented to ensure that there is an encryption of
user sensitive data.
ii. Authentication: All users of the system have to register and then login by using
usernames and passwords they created.
iii. Confidentiality: Sensitive data are encrypted (such as password encrypted by using SHA5
algorithm).
iv. Data integrity: Ensuring that the only user of the system can have an access to change the
content on the system otherwise cannot be done depending on their user role.
v. Availability: The availability of the system is a key requirement; the system is accessible
at a time which is need of performing organizational tasks based on visitor information.
5.6 Back end and database implementation
This section discusses about the backend implementations with respect to Database
implementations. This will further include a brief introduction to Programming Languages and
Database management system used.
5.6.1 Database implementation
Database system is the storage place of information in the system and where system records are
managed using queries. The system contains three (3) tables which stores information about the
system. The tables are Staff, Student, Student_ results.

Figure 5.5: Database implementation tables.

5.6.2 Back-end implementation
The system is implemented using Hyper Text processor (PHP) as a server scripting language
which serves as a bridge between the database and user interfaces to manipulate and perform
system functionalities.
5.7 Front end and User Interface implementation
The system interfaces are well designed by using HTML, Bootstrap, CSS and JavaScript to
ensure that users interact well with the system in performing their operations. Each user of the
system plays his/her role as defined during registration process. Each user must provide his/her
authentication credentials username and password accordingly so as to access the system; the
system should direct the user according to his/her role to have the privilege access of the system.
The following hints show user interface interaction depending on their roles:
i) When a System academic officer log in to this interface, they will be able to do their
roles as explained previously in this report.

Figure 6.5:After Academic Officer Login

ii) When a Student login to this interface, they will be able to perform some of the
activities as explained before.

Figure 7.5: Students after Login.

 iii. When a teacher login to this interface, they will be able to perform some of the activities
as explained before.

Figure 8.5: Teachers after Login.

5.8 System Testing and Evaluation

Testing is intended to show that a program does what it is intended to do and to discover
program defects before it is put into use (Sommerville, 2011). When you test software, you
execute a program using artificial data. You check the results of the test run for errors,
anomalies, or information about the programs non-functional attributes. Testing is conducted to
check if software meets customer requirements also to discover situations in which the behavior
of the software is incorrect, undesirable, or does not conform to its specification. The following
are the types of testing to be done;
5.8.1 Unit testing
These testing individual program units are tested. Unit testing should focus on testing the
functionality of objects or methods. This is to ensure that every part of the system has met the
intended functionality.
5.8.2 Component testing
This testing several individual units is integrated to create composite components. Component
testing should focus on testing component interfaces. This testing facilitates the individual parts
of the system to be integrated with other part in ensuring the operations of the system are well
achieved in integrated manner. Example academic officer check if the student is registered.
5.8.3 System design
In this, some or all of the components in a system are integrated and the system is tested as a
whole. System testing should focus on testing component interactions. Also, this testing is
performed to check if the project objectives are met in order to solve the intended problem. In
this system, the components are tested and work successfully.
5.8.4 Test case
Test cases are specifications of the inputs to the test and the expected output from the system (the
test results), plus a statement of what is being tested (Sommerville, 2011). Test data are the
inputs that have been devised to test a system. Test data can sometimes be generated
automatically, but automatic test case generation is impossible, except that people who
understand what the system is supposed to do must be involved to specify the expected test
results. A test case might consist of test case name, test objective, actual result, and expected
result.
 CHAPTER SIX
CONCLUSION AND RECOMMENDATIONS
6.0 Introduction
This chapter describes the objectives of the system described in earlier chapters, achievement of
the system objectives, conclusion and recommendations of the system.
6.1 Achievements of research objectives
The main objective of this project is to develop and implement a web-based system that will help
student’s parents to academic record of their student at school through normal messages and the
organization to keep academic records in simple way.
6.2 Future work
i. This system should be integrated with other systems in a school/college or universities to
ensure efficiency and easy access of information.
ii. The system should focus on extending its functionalities including building a mobile
application to enhance system availability and accessibility.
6.3 Conclusion and recommendations
The Secondary School Academic Record System helps in managing school academic information
and hence solves many problems associated with manual task systems such as to store student
academic information on papers. From this system there will be no more use of paper work and
hence reduction of cost and time management.
 REFERENCES

https://www.w3schools.com/php/

Data Base Management System by RaghuRamaKrishnan (Tata Mc-Graw hill,3rd edition)

https://stackoverflow.com
Jiang, J. J., Klein, G., & Balloun, J. (1996). Ranking of system implementation success factors.
Project Management Journal, 27, 49-53.

K. Kendall, J. K. (2011). System Analysis and Design 8th ed.

Kenneth E. Kendall, Julie E. Kendall (Ed.) (2010). Systems analysis and design (8th Ed.). New

Sommerville, I. (2016). Software Engineering (10th edition ed.). Published by Pearson education

Teorey, T.J., Lightstone, S.S., et al., (2009). Database Design: Know it all.1st ed. Burlington,
MA.: Morgan Kaufmann Publishers.

Berge, Zane L. (2002, April 2). The Role of the Online Instructor/Facilitator. Available at
http://www.emoderators.com/moderators/teach_online.html