Abstract

There were a number of problems associated with adopted manual methods to manage student
information at Pokola Day Secondary School located in the North-Western province of Zambia,
these followed regulations caused delay in the delivery of services to students, inaccuracies in
the completion of tasks and so on. A new system designed and implemented by using the Web
Development tools to solve most of the problems and obstacles resulting from the use of the old
methods and techniques.

The main work of the software design process included requirements analysis, database
description and logical structure design of the data. Database System test results show that the
database system meets the requirements of each module with a graphical user interface and
simple procedures.

Student data can be updated by the administrator of the system efficiently, accurately in a short
time and in a flexible manner.

The new Student Information System (SIS) for Pokola Day Secondary School is developed in-
house based on the requirement specification of the Head Teacher’s Office. The system is
developed using PHP programming language with MySQL database. Apache Server is used to
configure the system. After properly testing the SIS it was implemented successfully. The system
supports functions including storing and processing students’ enrollment data, handling class
registration, scheduling classes, entering and processing grades, generating grade reports and
transcripts, processing graduation related data and generating statistical reports of different kind
for multiple purposes.

Finally concluded that adopted this new database SIS helps to accomplish the tasks at high speed
and accuracy, also helps the management of the school in speed of decision-making, which helps
raise the level of performance of the academic school in general.

Student Information System P a g e 1 of 95

Acknowledgement

Contents
Student Information System P a g e 2 of 95
CHAPTER 1: INTRODUCTION........................................................................................................................7
1.1. Background..................................................................................................................................7
1.2. Objectives....................................................................................................................................8
1.3. Purpose, Scope and Applicability.................................................................................................8
1.3.1. Purpose................................................................................................................................8
1.3.2. Scope...................................................................................................................................8
1.3.3. Applicability.........................................................................................................................9
1.4. Achievements..............................................................................................................................9
1.5. Organization of Report................................................................................................................9
CHAPTER 2: SURVEY OF TECHNOLOGIES...................................................................................................11
CHAPTER 3: REQUIREMENTS AND ANALYSIS.............................................................................................21
3.1. Problem Definition..........................................................................................................................21
3.2. Requirements Specification............................................................................................................22
3.3. Planning and Scheduling.................................................................................................................26
3.4. Hardware and Software Requirements..........................................................................................27
3.5. Preliminary Product Description.....................................................................................................28
3.6. Conceptual Models.........................................................................................................................29
CHAPTER 4: SYSTEM DESIGN.....................................................................................................................30
4.1. Basic Modules.................................................................................................................................30
4.2. Data Design.....................................................................................................................................31
4.2.1. Schema Design.........................................................................................................................31
4.2.2. Data Integrity and Constraints.................................................................................................32
4.3. Procedural Design...........................................................................................................................33
4.3.1. Logic Diagrams.............................................................................................................................33
4.2.2. Data Structures............................................................................................................................37
4.2.3. Algorithms Design........................................................................................................................44
4.4. User Interface Design.....................................................................................................................45
4.5. Security Issues................................................................................................................................47
4.6. Test Case Design.............................................................................................................................47
CHAPTER 5: IMPLEMENTATION AND TESTING..........................................................................................49
5.1. Implementation Approaches..........................................................................................................49
5.2. Coding Details and Code Efficiency.................................................................................................51
5.2.1. Code Efficiency.........................................................................................................................51
5.3. Testing Approach............................................................................................................................51

Student Information System P a g e 3 of 95

 5.3.1. Unit Testing..............................................................................................................................51
5.3.2. Integrated Testing....................................................................................................................51
5.4. Modifications and Improvements...................................................................................................51
CHAPTER 6: RESULTS AND DISCUSSION.....................................................................................................52
6.1. Test Reports....................................................................................................................................52
6.2. User Documentation.......................................................................................................................52
CHAPTER 7: CONCLUSIONS........................................................................................................................53
7.1. Conclusion......................................................................................................................................53
7.2. Limitations of the System...............................................................................................................53
7.3. Future Scope of the Projects...........................................................................................................53
REFRENCES................................................................................................................................................54
GLOSSARY..................................................................................................................................................55
ACRONYMS................................................................................................................................................56
APPENDIX A...............................................................................................................................................57
Installation Manual................................................................................................................................57
User Manual..........................................................................................................................................60
APPENDIX B...............................................................................................................................................80
Technical Manual...................................................................................................................................80

Student Information System P a g e 4 of 95

Table of Figures

User Profile………………………………………………………………………….….…...14

Tutor Registration.......………………………………………………………………….…...16

Assign Tutor………………………………………………………………………………...16

Platform, Database and Development Language…………………………………………...18

Student Interaction with the System………………………………………………………...19

ER Diagram……….………………………………………………………………………...31

Administrator Use CASE…………………………………………………………………...33

Standard User Use CASE …………………...……………………………………………...34

Class Teacher Use CASE …………………………………………………………………...34

Teacher Use CASE …………………………….….………………………………………...35

Student Use CASE …………………...……………………………………………………...35

System Flowchart...……………………………………………………………………...…...36

Users Table...………………………………………………….……………………………...37

User Groups Table...………………………………………...…………………...….………...37

Students Table...………………………………………………………………………....…...38

Enrollment Table...……………………………………………………………………....…...38

Subjects Table………………………………………………………………………………...39

Classes Table………….……………………………………………………………………...39

Class Subjects table…………………………………………………………………………...39

Student Subjects Table…………...…………………………………………………………...40

Timetable Table….…………………………………………………………………………...40

Assessment Types Table……………………………………………………………………...40

Student Information System P a g e 5 of 95

Assessment Schedules Table……...…………………………………………………………...41

Assessment Results Table…………...………………………………………………………...41

Employees Table….…………………………………………………………………………...42

Teachers Table…….…………………………………………………………………………...42

Academic Period Table……………………….…………………………………………...…...43

Student Information System P a g e 6 of 95

CHAPTER 1: INTRODUCTION

1.1. Background

Student information system literally means the general information systems for maintaining and
providing student information. It exists in all the schools, colleges, universities and any other
education institutions. However, those information systems vary. Some of them are paper based;
heavily manual work is involved in managing and maintaining information such as student
personal records files. However, recently, most schools, even down to the very smallest, utilize
computers in some way or another. The uses to which the computers are put vary enormously,
ranging from word processing and spreadsheet through to worldwide on-line access, complicated
user access permission system and vast functionalities.

It is probably true that many of today’ s business simply could not function effectively without
automated information processing systems of some form or another, so do academic schools. All
of them have common tasks such as collecting, storing and processing information regarding
their students, staff and the work done within the department. With the increase of information, it
is unwise to adopting the traditional paper based system which is slow to access and therefore,
inefficient. Recent years, many systems were developed either by the academic schools or the
software companies in order to partially automate many of the processes carried out by the
department. Those developments dramatically reduce the time take in searching information and
should enable the school to maintain precise and up-to-date information. For example,
previously, students would have to enquire for much of his information from the school student
office, which
required more time and effort, particularly from members of staff. The new system is more
efficient and also often presents more accurate information. However, those systems vary even
within the same academic school. Some are quite well developed and implemented, some still
adopting the inferior and out-of-date technology. This is also one of the project’ s aims: to
analysis some sample systems in order to attain the strengths and eliminate the weaknesses in
developing the new potential student information system.

Student Information System P a g e 7 of 95

1.2. Objectives

General Objectives

 The study aims to develop Students Information System for Pokola Day Secondary
School to have much accurate, organized of students’ information and to ensure data
integrity, privacy, and security in an open-access environment.

 Reduce manpower and manual paper works for maintaining the records offline.
Specific Objectives

 To make their work easier and to be accurate on their work.

 To have a privacy and security to the students’ information.
 To easily search to access the students’ information.
 To register and enroll student using an online web application.
 To create an online class timetable for teachers and students using a web application.
 To easily identify and determine the name of the students’ information for a particular
School Year.
 To record student assessment results based on a certain academic period and School
Year.
 To allow students to check for their assessment results and print out their report forms
online using web based SIS without making queues.

1.3. Purpose, Scope and Applicability

1.3.1. Purpose
The main purpose from this study is to design database to construct Student Information System
at Pokola Day Secondary School, this system will solve most of the problems and obstacles
resulting from the old methods and techniques that have been previously mentioned. Thus
transform the work in this school from manually to a computer based system, which leads to
provide accuracy, efficiency, security and so on.

1.3.2. Scope
The proposed system will be implemented and it will be limited only to Pokola Day Secondary
School. The target respondents of this study are the administration and the students of Pokola

Student Information System P a g e 8 of 95

Day Secondary School holding the position as a Head Teacher or Senior Teacher and to all the
students enrolled in school.

1.3.3. Applicability
Student Information Systems (SIS) are designed with diverse application potentials ranging from
simple management of students’ records at school to management of all student related functions
as well as administrative functions of an academic or tertiary school (e.g. University or College)
or a chain of education establishments.

Students can also keep track of their application through SIS seamless. The class timetables,
assessment results and other school administrative tasks can also be accomplished using the
computerized student information system quickly and in real-time.

1.4. Achievements
The achievements of the new Student Information System include:

 Fast student registration and enrollment.

 The implementation of Timetable Scheduling tools for both teachers and students at
large.
 The implementation of the student assessment results module which allows subject
teachers to enter student assessment results faster and then the system provides the
functionality of automatic grading of subject results thereby reducing the stress among
teachers to assign grades and remarks to final assessment results.
 The implementation of an online student portal which allows students/parents/guardians
to login from wherever they are using internet and web browser when they wish to check
for the daily class timetable or student subject assessment results.

1.5. Organization of Report

The report is split into seven separate chapters, references and appendices. It is structured to
reflect how the study was attempted and to try to show the logic with which this project was
approached. Indeed, the report is largely in an order of how the study was completed.

Chapter 2 of the report discusses the Technological surveys and literature review that were
carried out in order to proceed with the project. It explains and justifies the manner in which this
project was approached.

Student Information System P a g e 9 of 95

Chapter 3 shows the product of the project, which is the detailed requirement specification of the
new Student Information System. That chapter also discusses how it was derived from the
previous investigation.

Chapter 4 shows the design of the system; this involves the listing down of all the basic modules
of the new system, data design, database schema design, data integrity and constraints, security
issues, user interface design and Use case diagrams which depicts the actual functionality of the
proposed SIS.

Chapter 5 shows the implementation plan adopted and the various types of system tests which
were carried out during the implementation process.

Chapter 6 shows the test reports together with the user documentation of the new system.

Chapter 7 is the final chapter to finish the report; it shows the evaluation of the outcomes of the
project, which includes identifying the weaknesses in processing the project and providing
further enhancements to the system development. It also discusses the limitations of the system
and future scope of the project.

References lists down the books and websites addresses where we borrowed some report content
during the organising and development of the system report and the functional system at large.

Glossary shows the meaning of various terms and abbreviations used throughout this report.

Appendix A discusses the system Installation and User Manual for the new Student Information
System.

Appendix B shows the Technical manual which includes the source codes of the new system in
PHP and JavaScript.

Student Information System P a g e 10 of 95

CHAPTER 2: SURVEY OF TECHNOLOGIES
2.1. Introduction

This part of the report provides a basic outline of the research done during the project for the
purpose of acquiring an understanding of the subject content i.e. the Student Information System
(SIS) and its components.

2.2 To investigate what the Online Student Information System

Student information system literally means the general information systems for maintaining and
Providing student information. It exists in all the schools, colleges, universities and any other
education institutions. However, those information systems vary. Some of them are paper based;
heavily manual work is involved in managing and maintaining information such as student
personal records files. However, recently, most schools, even down to the very smallest, utilize
computers in some way or another. The uses to which the computers are put vary enormously,
ranging from word processing and spreadsheet through to worldwide on-line access, complicated
user access permission system and vast functionalities.
2.3. Methodology

System development methodologies have over the past years evolved from traditional System
Development Life Cycle (SDLC) to agile methodologies. The adopted methodology for the
development of the proposed system is the Agile methodology due to its ability to expose
progress and problems. Rico (2007), defines agile methods as lightweight software design
processes based on small teams using flexible technologies to iteratively improve software using
customer feedback to converge on solutions.

Characteristics of the Agile methodology

2.3.1. Extreme Programming; this is a development approach that is more of code oriented
rather than design oriented. Testing is thus made easy with extreme programming. Abrahamson
(2002)

2.3.2. Dynamic System Development method (DSDM); DSDM is an agile project management
method and delivery framework that aims to deliver the right solution at the right time. Richard
(2010).

Student Information System P a g e 11 of 95

2.4 Application Development Technologies

This section of the report describes the technologies used to develop the system. It takes into
consideration both the front and backend technologies used in the whole process.

Front end technologies are the user interaction processes that enable a user to interact with the
system. These technologies include the tools used in the designing and implementation of forms;
reports input responses and the look and feel of the application.

Frontend processes usually run on the client machine while the actual process is executed in the
backend by backend technologies

The frontend technologies used in the design and implementation of the system are;

2.4.1Cascading Style Sheets (CSS): CSS is used to define styles for your web pages, including
the design, layout and variations in display for different devices and screen sizes. It saves a lot of
work! With an external style sheet file, you can change the look of an entire website by changing
just one file! CSS describes how HTML elements are to be displayed on screen, paper, or in
other media. CSS saves a lot of work. It can control the layout of multiple web pages all at once.

2.4.2. JavaScript is an object- and prototype based programming language created by Brendan
Each at Netscape. Although similar, JavaScript is not Java. Unlike Java, JavaScript is not a full
programming language; its main used in the web environment and even then it is used in
conjunction with another language, usually HTML. JavaScript is an excellent language to use for
functionality such as rotating pictures on a page, error handling when inputting information in
forms and setting responses to certain events on a web page. Robbins (2006)

2.4.3. HTML: HTML is the language for describing the structure of Web pages. HTML gives
authors the means to:

● Publish online documents with headings, text, tables, lists, photos, etc.
● Retrieve online information via hypertext links, at the click of a button.
● Design forms for conducting transactions with remote services, for use in searching for
information, making reservations, ordering products, etc.
● Include spread-sheets, video clips, sound clips, and other applications directly in their
documents.

Student Information System P a g e 12 of 95

Back end technologies are mainly processes that interact with database creation and
manipulation, connections and storage. They provide support to front end technologies for
services such as addition, retrieval, updating and deleting information or data.

The backend technologies used in the design and implementation of the system are;

2.4.4. PHP is a server side scripting language that was designed for creating dynamic websites.
It runs on the server and processes instructions contained in a web page before that page is sent
to a user’s web browser. PHP can also “talk” with various database systems, giving developers
the ability to generate dynamic pages based on the results of an SQL query. Moncur (2009).

2.4.5. MySQL: MySQL is the most popular open source SQL database management system
Telecom companies and forward-thinking corporate IT Managers because it eliminates the major
problems associated with downtime, maintenance and administration for modern, online
applications.

● Backup: It’s easier to setup automatic backups in Microsoft SQL Server and ensure
there’s a point of restore.
● Security: Because SQL Server integrates with Windows Active Directory, it is quite easy
to determine access to the databases via logins for the users in the security module of the
database management system.
● Auditability: You cannot copy or duplicate the SQL Database without leaving an audit
trail which administrators can easily review and track the users who logged in and made
any changes.
● Scalability: SQL Server can handle much larger databases with large amounts of data; it
is easy to grow a SQL server database as the data demands of the organization increase.

2.5. Review of Similar Systems

Activities

• Browse internet for information on similar systems

• Review system documentation for similar systems that are implemented elsewhere

• Compare the systems

• Select suitable features to implement

Student Information System P a g e 13 of 95

This objective aimed at evaluating other available systems of similar nature in order to assist
with selecting and exploring features that would be incorporated in the proposed system. By
reviewing the systems that have already been implemented, it would help in not having to
reinvent the wheel by redeveloping what already exists and also avoid making similar mistakes
to develop a robust system.

In order to achieve this, thorough research through the internet as well as documentation of
existing systems would have to be done. After comparing the systems suitable features were
selected to include in the final system.

This chapter of the report discusses different systems with similar concepts implemented
elsewhere. This evaluation will assist in learning from the similar systems i.e. to incorporate
useful similar features and also avoid any likely mistakes that may have been made during
design or development of the systems.

The area on which the evaluation was focused was a simple overview, the appearance,
navigation, usability and functionality.

The three systems that were reviewed in this chapter are;

2.5.1. SOAR Student Online Registration System

2.5.1.1. Overview

The SOAR student online registration system was designed to enable academic institutions to
register students online and manage their academic activities. It enables students to register to
classes and keep track of their academic progress. The main actors in of the system are the
student, tutor and administrator.

2.5.1.2. Appearance

The application has a user-friendly interface. It has a list of menu options to the left of its screen
that are easily accessible to the user. Once logged in, it displays the users’ details and allows the
users to edit their profile details as shown in figure.

Student Information System P a g e 14 of 95

Figure 1; menu tab and the functionality to edit user profile

Data capture page adapted from http://1stsystem.com/soar_system_solution.html

2.5.1.3. Functionality

The functionality of the system consists of a number of things such as; capturing of user details,
assigning students to classes and lectures, tracking of students’ progress, viewing of students,
viewing of students and their records. It also enables administrators to manage student
registration, and to manage the school. Professors are able to manage students’ grades, and
attendance.

2.5.1.4. Navigation

The application has got a menu grid at the left of the screen as shown in figure 1. This grid has
links that a user can select from in order to go to the page that they wish to go to. It also has a
drop down menu at the top right of the screen that enables the user to sign out of the system.

2.5.1.5. Usability

Student Information System P a g e 15 of 95

The responsiveness of the website enables the user to move from one textbox or for to another
using the tab key. Users can complete forms using the autocomplete functionality and
predetermined entries that can be picked from the database. The system also has regular buttons
used for saving or submitting information.

2.5.1.6. Features Adopted

• The progress view. A student is able to see the status of their academic progress. This is a
very useful functionality because a student is kept aware of their academic status

• The interface display was helpful in that it gave me a guideline in how to place the menu
and the links in the new system.

2.5.2. Motor Driving School system

2.5.2.1. Overview

This Motor Driving School System is a system designed by Nevon projects. System helps
driving schools to automate the manual tasks of maintaining and managing clients. The
application helps in the assigning of instructors to students and also enables instructors to assign
a training slot available to a student.

The system enables students to register online using a registration form. Once a student registers
to the system, a notification is sent to the email address they provide.

2.5.2.2. Appearance

The system is a web based system that uses. It was developed in php. The system has one log in
form on the home page. Once logged into the system, each profile shows the details of the person
logged. Each page has a menu bar at the top section of the page.

2.5.2.3. Functionality

The Motor Driving School management system enables users to register online using a
registration form. It enables the administrator to register a tutor as shown in figure 2. The system
also enables a driving school to assign tutors to students as shown in figure 3, view students,
adding tutors and select a training slot. The system also enables students to make online
payments to the school. A school is also able to view the list of all its students and the list of all
tutors.
Student Information System P a g e 16 of 95
Figure 2; shows tutor registration

Data capture page adapted from http://nevonprojects.com/motor-driving-school-system/

Figure 3; shows the assigning of a tutor

Data capture page adapted from http://nevonprojects.com/motor-driving-school-system/

2.5.2.4. Navigation

Student Information System P a g e 17 of 95

The system provides buttons and indicators to assist users find their way around the system
through each page has a menu bar that enables a user to navigate to the task that they want for
instance, if a user wants to view their user details they can go to the menu bar and select view
user details. A user is directed to their profile by entering their log in details and then selecting
log in.

2.5.2.5. Usability

The system is a very user friendly system. It is not sophisticated and it has a very user friendly
interface. Simple language and on its GUI was used. All users log in using the same form. This
makes it simple because one will not have to start looking for a different type of log in form in
order to log into the system.

2.5.2.6. Features Adopted

• Assigning of tutors to a student

• View registered students

• Approve applications from the students

• Online registration of students

2.5.3 Case Study 3 SIS

2.5.3.1. Introduction
SIS stands for School Information System, which is the main administrative database system
within the School of Computing (SoC). All members of the SoC have the access via its main
interface (web based) intranet web pages at http://www.comp.leeds.ac.uk/cgi-
bin/sis/main/index.cgi by providing their Linux username and password. The value proposal to
the user is the effective and efficient way of broader range of information access. From the
student’ s prospect, it also means convenient coursework submitting and results checking
whereas, for the staff, it helps staff generate workload report and ease administration process.
2.5.3.2. Overview of the System
System Scope: The web based SIS is available for both staff and student of SoC to browse, and
provides them with different information from any Internet enabled computer. The SIS and
dynamic web page generation system interface with a number of existing systems, including
university student information management system Banner, Edass and several administrative
Student Information System P a g e 18 of 95
systems, such as those used to issue standard letters to students, the sorting of post and oversight
of placement student are connected dynamically to the SIS database.
Technology: Dynamic web information system provides updated and accurate information to
both
students and staff. Modern IT technologies are used within the system integration and database
management to provide as much information as the system can to the end users.
Stakeholder and User profile:
System users: Total head count of SoC is 852, which includes 514 full-time students.
Stakeholder
summary and user profile will be detailed in the SIS requirement specification in Appendix D.
2.5.3.3. Technical Architecture
Security: Users of SIS are issued a Linux username and password, which are intensely managed
by the computing administrative staff.
Figure 4; Platform, Database and Development language

Student Information System P a g e 19 of 95

User Environment:
The user will be accessing the system via a connection to the Internet. This is most likely to be
from home or Lab, which are the excellent baseline, as this category includes the slowest types
of Internet connection. However, the staff may normally use the system at work from the
university’ s PCs and network while they are working.
Figure 5; Student Interaction with the System

2.5.3.4. Features Adopted

• Reports and its ability to show all the registered students and staff details.

Student Information System P a g e 20 of 95

CHAPTER 3: REQUIREMENTS AND ANALYSIS

3.1. Problem Definition

Notably, student information system or SIS incurs such application software designed for
educational establishments to manage student data. Student information systems provide
capabilities for entering student test and other assessment scores, building student schedules,
tracking student attendance as well as managing many other student-related data needs within the
institution university. Thus, many of these systems applied in the Zambia can be scaled to
different levels of activity and can be configured by their home institutions to meet local needs.

Moreover, before universities have created their own bespoke student record systems, but with
growing complexity in the business of educational establishments, organizations now choose to
buy customizable within the shelf software.

It can be that, modern student information systems are usually server-based, with the application
residing on central computer server and are being accessed by client applications at various
places within and even outside the school.

During the year 1990s, student information systems have been changing and are fast adopted
through the presence of a web medium as a channel for accessing SIS without any hassle upon
viewing student details and information.

This study deals with the Proposed SIS for Pokola Day Secondary School Specifically, this study
aims to answer the following questions:

 What are the problems encountered by the system of the students’ information system in
terms of services?
 How do the above to be improved?
 Is the proposed system can really make solution for these problems?
 Does the computer based system can help the school to make Collection process fast and
ease?

This chapter outlines how the requirements of the proposed system used in order to meet its
objectives were derived taking into account both functional and non-functional requirements.

In this chapter we will also explore some fact finding techniques and also illustrate the
requirements by the use of modeling.
Student Information System P a g e 21 of 95
3.1.1. Fact finding techniques
The fact finding techniques are the methods used to acquire information that is to be used for the
purpose of determining the requirements of the proposed system.

3.1.2. Interviews
Interviews are a very essential method of gathering information in projects of many kinds
regardless of the subject of research. Interviews were used to provide an insight on the
challenges that users face in the current system. The current system does not provide for
accountability and the reporting of student assessment results is not possible unless done
manually. The interview process also unveiled the challenge of data capture that the users were
facing
3.1.3. Questionnaire
The defenders employ the use of questionnaires in finding solutions to the critical and
controversial problems of the present study. The results of the questionnaires supported the
formulation of the hypotheses. The defenders gather accurate information on how a manual
system of gathering and managing collection reports operates particularly about the processes
involved in such. Weaknesses of a manual system are examined for further analysis.
3.2. Requirements Specification
This system modelling and requirements analysis apply to the academic school’ s Student
Information System, which is going to be developed for Pokola Day Secondary School. The
system will be installed and maintained at the academic school level. The web based Student
Information System will be available for both staff and students of that individual school to
browse, and will provide them with different information authorizations from any Internet
enabled computer.
This chapter mainly focuses on the functional and non-functional requirements of the proposed
system.
3.2.1. Functional Requirements

Functional requirements refer to the fundamental functions a system is able to perform based on
the users’ needs. Bennet (2005), describes functional requirements as functionality that a system
is expected to perform.
For the proposed system the functional requirements were grouped according to the user
categories and included the outlined below;
Student Information System P a g e 22 of 95
 1. System Administrators.
2. Standard.
3. Class Teacher.
4. Teacher.
5. Students.
Systems Administrator User (Head Teacher) requirements:
● System should authenticate the users. The home page will have a login form that will
request for the Username and Password in order to log in.

● Create User.

● View users.

● Delete User.

● Create Employee.

● Edit and Delete Employee Record.

● Create Education Standard.

● Assign Employee as Teacher.

● Create Classes.

● Create Subjects.

● Edit and Delete Classes and Subjects.

● Assign Subjects to Classes.

● Assign Subjects to Teachers.

● Assign Teacher as Class Teacher.

● Setup Final Assessment Slip format.

● Create Assessment Types.

● Create Assessment Grades.

● Create School Year.

● Create Academic Period.

● Setup Database.

● Backup and Restore Database.

Student Information System P a g e 23 of 95

Standard User requirements:
● System should authenticate the users. The home page will have a login form that will
request for the Username and Password in order to log in.

● Create Classes.

● Create Subjects.

● Edit and Delete Classes and Subjects.

● Register and Enroll Students.

● Edit and Delete Student.

● Create Class Timetable.

● Edit and Delete Class Timetable.

● Create New Assessment Schedule.

● Edit and Delete Assessment Schedules.

● View Assessment Results for All Classes.

Class Teacher User requirements:

● System should authenticate the users. The home page will have a login form that will
request for the Username and Password in order to log in.

● Create Subjects.

● Create Class Timetable.

● Edit and Delete Class Timetable.

● Create New Assessment Schedule.

● Edit and Delete Assessment Schedules.

● View Class Assessment Results.

● View Class Timetable.

Teacher User requirements:

● System should authenticate the users. The home page will have a login form that will
request for the Username and Password in order to log in.

● Enter Student Assessment Results.

● Edit and Delete Student Assessment Results.

Student Information System P a g e 24 of 95

 ● View Student Assessment Results.

● View Class Subject Timetable.

Student User requirements:

● System should authenticate the users. The home page will have a login form that will
request for the Username and Password in order to log in.

● View Class Timetable.

● View Assessment Results.

The figure below illustrates the description of some functional requirements that is available in
the new Online Student Information System.

Table 1: Functional Requirements

Functional Requirements
Creation and deleting users The administrator of the system will be able
to create new users to the system. The users
of the system are Standard, Class Teacher,
Teacher and Students. The Administrator
will also be able to delete the users
Registering and Enrollment of Students The Standard user will be able to register
and enroll new students to the system.
Students will be able to login and browse
for their assessment results and view class
Timetable online.
Assigning of Teachers to Classes and The system will enable the administrator to
Subjects define class teachers and assign subjects to
Teachers based on various classes.
Creation of Class Timetable The Class Teacher will be able to create a
class Timetable for each and every class
which he/she has been assigned to manage.
Entering of Assessment Results The subject teacher will be able to enter
student assessment results based on the
specific assessment schedule created by the
standard user or administrator under a
certain academic period within an active
School Year.

3.2.2. Non-Functional Requirements

Non-Functional Requirements are those that describe aspects of the system that are concerned
with how well it provides the functionality required (Bennett, 2005).
Table 2; shows the non-functional requirements of the system
Student Information System P a g e 25 of 95
 Non-functional requirement Description
Security The system will be able to control user
account access. This will be achieved using
passwords and controlling access levels
Capacity The system will be able to manage multiple
transactions at a goal and store them without
having any negative effects on its
performance.
Extensibility It being a very new system, it will be
subjected to a lot of change in terms of
additions and subtractions to its functionality.
The system will be able to handle these
changes without distorting existing data and
functionalities.
Data Recovery The system will be able to recover from
critical failure when it crashes. There will be
able to achieve recovery by database restore.
Data integrity The system will be able to regulate the type of
data entered through input validation that will
be in every form.

3.3. Planning and Scheduling

The Student Information System is expected to be complete within 3 to 4months. Below is the
proposed calendar of events.

Table 3; Project Schedule

1 User Requirements 16/12/2019 31/12/2019

1.1 Interview staff 1/01/2020 04/01/2020
1.2 Observation 5/01/2020 6/01/2020
1.3 Literature Review 7/01/2020 8/01/2020
1.4 Questionnaire 9/01/2020 13/01/2020
2 Review Similar 17/01/2020 18/01/2020
Systems
2.1 Check other systems online 17/01/2020 17/01/2020

2.2 Interview students and school staff 18/01/2020 18/01/2020

3 Review 21/01/2020 24/01/2020

Student Information System P a g e 26 of 95

 Methodologies
4 Design & 25/01/2020 11/01/2020
Implementation
4.1 Use Case Diagram 25/01/2020 25/01/2020
4.2 EERD 26/01/2020 29/01/2020
4.3 Relational Schema 30/01/2020 3/02/2020
4.4 Normalization 3/02/2020 5/02/2020
4.5 Database 5/02/2020 10/02/2020
Development
4.6 Website Design 11/02/2020 14/02/2020
4.7 PHP 15/09/2020 1/03/2020
4.8 Connect Front/Back 2/3/2020 6/03/2020
4.9 Report 7/3/2020 11/03/2020
5 Evaluate Online SIS 12/3/2020 19/03/2020

5.1 Module testing 12/3/2020 13/03/2020

5.2 Integrated testing 14/3/2020 15/03/2020
5.3 System Testing 16/3/2020 17/03/2020
5.4 SIS Evaluation 18/33/2020 25/03/2020
5.5 Final report writing 26/5/2020 31/03/2020
5.6 Report Ready to 1/04/2020 1/04/2020
Submit

3.4. Hardware and Software Requirements

3.4.1. Hardware Requirements

 1.5Ghz or better of processor
 20 GB or more of hard drive
 512 MB or more of RAM
 Mouse

Student Information System P a g e 27 of 95

  Monitor
 Keyboard
3.4.2. Software Requirements
 Wampserver 3.0.6 or Higher
 MySQL 5.7.14 or Higher
 Adobe Dreamweaver CS5 or Higher
 Notepad ++ 7
 Mozilla Firefox version 29 or Higher
 Windows 7 32/64 bit or Higher

3.5. Preliminary Product Description

Before starting the process of collecting data for the purpose of analysis and using it in the
design of an information system based on the computer, it must first determine the objectives for
which this system was found, also determine the necessary requirements in the design of the
system. Thus there is a good analysis results in successful design meets with the requirements of
the beneficiary body. After having a full awareness of the obstacles and problems facing the staff
responsible for the administration of the in the Pokola Day Secondary School in the North
Western province of Zambia.

3.5.1. Elements of the SIS Environment

It has been identified in the SIS environment five major elements: people, procedures, data,
software and hardware.

 People: The first component is the people involved with the system. There are four
different types of people who are involved in the environment of a SIS, application
developers, database administrators, end-user and database designers.
 Procedures: This component refers to the rules and instructions which manages the
design and use of the database. The staff and the user of the system who run the database
need to document the procedures on how to use or operation of the system. This may be
composed of instructions on how to:
o Use of a particular database management system or application program.
o Start and stop database management systems.
o Create backups of the database.

Student Information System P a g e 28 of 95

 o Dealing with the failure of software and hardware.
o Highlight the database across multiple disks, change a table structure, store data
to secondary storage and improve performance.
 Data: Maybe the most significant part of the SIS environment is the data, where data is a
collection of facts stored in the database.
 Software: Software element consists of database management system software and
application software, in addition to the operating system and contains software network
in the case that the SIS used through the network.
 Hardware: The applications and the Database Management System (DBMS) need the
hardware to run. Hardware can range from a single personal computer to a single central
or the network of computers. Hardware depends on the specific requirements of the
organization and database management systems are used. In some SISs run only on
specific operating systems or hardware, while others run on a variety of operating
systems and hardware. However, the new SIS can run on Windows, Linux, Mac/Apple
and IBM platforms.

3.6. Conceptual Models

A conceptual model is a representation of a system made of the composition of concepts which
are used to help people know, understand or simulate a subject the model represents. It is also a
set of concepts.

Analysts who adopt the SDLC approach often benefit from productivity tools, called Computer-
Aided Software Engineering (CASE) tools, that have been created explicitly to improve their
routine work through the use of automated support. Analysts rely on CASE tools to increase
productivity, communicate more effectively with users, and integrate the work that they do on
the
system from the beginning to the end of the life cycle.

Use Case diagrams, Entity Relationship Diagrams, Flow Charts are the selected models which
has been used in this report. The next chapter shows graphical design of the system using these
models.

CHAPTER 4: SYSTEM DESIGN

Student Information System P a g e 29 of 95

The most creative and challenging phase of the system life cycle is system design. The term
design describes a final system and the process by which it is developed. It refers to the technical
specifications that will be applied in implementing the proposed system. It also includes the
construction of program and designing of output, input, code, database and process of the
system.

4.1. Basic Modules

Student Information System is a complete online electronic system for managing school
information such as Subjects, Classes, Teachers, Timetable and Assessments information. The
system has got the following list of modules.
1. Education Standards
Education Standards is the module used to setup the level of education being offered at
school such as Early Childhood Education, Primary Education, Junior Secondary Education,
Senior Secondary Education etc.
2. Employee Management
The Employee Management module helps with the management of employee data, it consists
of tools for recording employees and setting employee as teacher.
3. Subjects Management
Subjects management is used to add subject offered under a specified Education Standard.
4. Classes Management
Classes management is used to add classes offered under a specified Education Standard. It is
also used to define class teachers and assign subjects to classes and teachers which teach
subjects for various classes under a specific education standard or level. Class subjects’
definition has got two options. You can assign multiple class subjects to a single teacher or
assign multiple teachers to a single subject.
5. Students Management
Student management module is used to register and enroll new students. This allows users to
view student list and Edit/Delete them quickly in realtime.
6. Timetable Management
This module provides the tools for Administrators, Standard Users and Class Teachers to
create a class timetable which displays the class subject schedules to subject teachers and
students so that they are well informed about when the specific tutorial session begin and end
including its duration.

7. Assessments Management

Student Information System P a g e 30 of 95

 This module is used by class teachers to setup an assessment schedule. It also provides an
interface for subject teachers to enter and edit assessment results. The assessment results
grades and remarks are automatically generated by the system on behalf of the teachers.
8. System Users Management
This module can only be accessed by the System Administrator after login to the system
successfully. All users of the system are created through this module except the student users
who are automatically created by the system during the student registration process. When a
student is registered for the first time, the Student Number automatically becomes the
Username and Password, but the Password can be changed later on.
9. System Setup
This module is only available on administrator users. It consists of the tools for setting up
School information (e.g. School Name, Address, Email, Phone etc.), School Year, Academic
Period, Assessment Types and Assessment Grades and Remarks.
10. Student Portal
This module provides the platform for students to login to the system and check for class
timetable and also view and print their assessment result slip/report forms anywhere using
the internet network on their computer or mobile devices.
4.2. Data Design

Several design models will be used to illustrate how functional and non-functional requirements
are attained by the proposed system in this chapter.

The Stackoverflow website defines Database design as “the process of specifying the logical
and/or physical parts of a database. The goal of database design is to make a representation of
some "universe of discourse" - the types of facts, business rules and other requirements that the
database is intended to model.”

4.2.1. Schema Design

Database design is the method in which all the necessary data to be used in the system as well as
the relationships between that data. To sufficiently achieve this Entity relationship modelling
was used for the design of the database.

Student Information System P a g e 31 of 95

4.2.2. Data Integrity and Constraints
Firstly, all the entities and their attributes are identified. After these are identified the
relationships between the data entities are then identified.

Constraints of the relationships between the entities are then identified.

Listed below are the identified entities with their attributes to be used in the design of the
Database:

USERS (User ID, User Type)

EMPLOYEES(EmployeeID)

TEACHERS (TeacherID, EmployeeID)

SUBJECTS(SubjectID)

CLASSES (ClassID, TeacherID)

Student Information System P a g e 32 of 95
CLASSSUBJECTS (ClassSubjectID, ClassID, SubjectID, TeacherID)

STUDENTS(StudentID)

ENROLLMENT (EnrollmentID, StudentID)

STUDENTSUBJECTS (StudentID, EnrollmentID, ClassID, SubjectID, SchoolYear)

TIMETABLE (TimetableID, ClassID, SubjectID, TeacherID, AcademicPeriod, SchoolYear,

Day, StartTime, EndTime)

ASSESSMENTSCHEDULES (AssessmentID, StartDate, EndDate, Day, StartTime, EndTime)

ASSESSMENTRESULTS (AssessmentResultID, AssessmentID, TeacherID, ClassID,

SubjectID, StudentID, EnrollmentID)

4.3. Procedural Design

This is a design methodology which combines a systematic set of rules for creating a program
design with diagramming tools needed to represent it. Procedural design is best used to model
programs that have an obvious flow of data from input to output.

4.3.1. Logic Diagrams

Use Case Diagrams
The use case is actually shown or drawn from a user’s perspective and how well the
system will interact from front end to front end. Well, according to
(BusinessAnalystFaq 2013); “Use case helps to specify and explain the interaction
between the actors and the system. Use cases are important because they are in a
tracking format”. Below is the UML diagram for the Online Student Information
System.

Student Information System P a g e 33 of 95

Administrator Use Case

Student Information System P a g e 34 of 95

Standard User Use Case

Class Teacher Use Case

Student Information System P a g e 35 of 95

Teacher Use Case

Student Use Case

Student

Student Information System P a g e 36 of 95

Flowchart

4.2.2. Data Structures

Data structures are a specialized means of organising and storing data in computers in such a
way that we can perform operations on the stored data more efficiently. Data structures have a
wide and diverse scope of usage across the fields of Computer Science and Software
Engineering.

Student Information System P a g e 37 of 95

There following below is the database tables structure

Users Table

User Groups Table

Student Information System P a g e 38 of 95

Students Table

Enrollment Table

Student Information System P a g e 39 of 95

Subjects Table

Classes Table

Class Subjects

Student Information System P a g e 40 of 95

Student Subjects Table

Timetable Table

Assessment Types Table

Student Information System P a g e 41 of 95

Assessment Schedules Table

Assessment Results Table

Student Information System P a g e 42 of 95

Employees Table

Teachers Table

School Year Table

Student Information System P a g e 43 of 95

Academic Period Table

4.2.3. Algorithms Design

Algorithm design is the branch of discrete mathematics and computer science that deals with the
research, development and implementation of sequential and asynchronous algorithms. While
there aren’t really any jobs with the title algorithm designer, most graduate-level computer
science work involves quite a bit of algorithm theory and research. Algorithms are used in every
field that deals with values that can be quantified and many fields that deal with values that
cannot.
An algorithm is simply a sequence of instructions; a recipe is an algorithm, and so is a list of
driving instructions.
The reason algorithms are used so often in computer science is that computers can be
programmed to execute instructions in a sequence, allowing programmers to instruct computers
how to render 3-D graphics, display text and perform various operations on numbers. The first
uses of computers were to perform basic arithmetic operations on huge volume of numbers,
sometimes requiring several months to return an answer that would take a few seconds or
minutes on today’s hardware. Computer scientists at the time didn’t realize that algorithms could
be used to program computers to make photo-editing and design applications, video games and
automated financial trading software.
However, in the case of the proposed new online Student Information System (SIS) PHP and
JavaScript programming languages has been used to write extremely web app to manage student
information at Pokola Day Secondary School with relatively little code.

Student Information System P a g e 44 of 95

4.4. User Interface Design
User interface design or user interface engineering is the design of user interfaces for machines
and software, such as computers, home mobile devices, and other electronic devices, with the
focus on maximizing usability. The graphical user interface is presented (displayed) on the
computer screen. It is the result of processed user input and usually the primary interface for
human-machine interaction. Good user interface design facilitates finishing the task at hand
without drawing unnecessary attention to itself. Graphic design and typography are utilized to
support its usability, influencing how the user performs certain interactions and improving the
aesthetic appeal of design; design aesthetics may enhance or distract from the ability of users to
use the functions of the interface. The design process must balance technical functionality and
visual elements (e.g., mental model) to create a system that is not only operational but also
usable and adaptable to changing user needs. Interface design is involved in a wide range of
projects from computer systems, to cars, to commercial planes; all of these projects involve
much of the same basic human interactions yet also require some unique skills and knowledge.
As a result, designers tend to specialize in certain types of projects and have skills centered on
their expertise, whether it is a software design, user research, or web design or industrial design.

The following below are the design of theHome page/Login for the new SIS user interface.

Student Information System P a g e 45 of 95

Dashboard

Student Information System P a g e 46 of 95

4.5. Security Issues
Security to the system will mainly be implemented by the use of passwords. Users of the system
will be required to log on to the Server, which will monitor all users online. The administrator on
the server side will monitor all user requests and will have the ability to log off any user from the
server.

Passwords and usernames will determine the privileges of the client who logs on to the server.
The server administrator will also be required to log on to the system server by use of a password
and username.

The figure below illustrates the login form that will be used to authenticate each and every user
credentials.

4.6. Test Case Design

Test case design refers to how you set up test cases. It is important that your tests are designed
well, or you could fail to identify bugs and defects in your software during testing designing and
good test cases ensure that every aspect of your software gets tested so that you can find and fix
any issues.

There are many different test case design techniques used to test the functionality and various
features of the software.

1. Test case design for the new SIS Login

Title: Login to the Website

Description: User should be able to successfully log into their account on the website/app
Preconditions: User must already be registered and use the correct login details.

Student Information System P a g e 47 of 95

Assumptions: they are using a supported device or browser to log in.

Test Steps:

1. Open website
2. Enter the Username and Password in the appropriate fields.
3. Click Login

Expected Result: The User should log in successfully.

2. Test case design for the new SIS Dashboard

Title: Website Dashboard

Description: User should be able to successfully log into their account on the website/app and
then select various options from the SIS Dashboard

Preconditions: User must already be logged into the System.

Assumptions: they are using a supported device or browser with JavaScript Support.

Test Steps:

1. Open website
2. Enter the Username and Password in the appropriate fields.
3. Click Login
4. Dashboard is displayed based on user access level.
5. Select an option from the system menu in order to perform a desired task.

Expected Result: The User should be able to perform a desired task successfully (e.g.
Registering a Student, View Student Results, View Class Timetable etc.).

Student Information System P a g e 48 of 95

CHAPTER 5: IMPLEMENTATION AND TESTING

5.1. Implementation Approaches

Implementation means replacing the old system with new system, training the users on how to
use the system. This is done to make sure that the users are conversant with the system.

This system was implemented in an application developing language such as PHP, JavaScript,
MySQL and HTML. The following is the description of how the system was realized following
the design. The forms (interface) that will be used for input and output will be discussed. This
chapter focuses on what was actually done. It will contain a description of implementation,
showing how it arises from the design. Different modules codes were written in order to
implement the system design and satisfy the success criteria.

Hardware Requirements:

● PIV 2.8 GHz Processor and Above

● RAM 512GB and Above
● HDD 50 GB free Hard Disk Space and Above
Software Requirements:
● WINDOWS OS (2003/ 2008 Server / 2012 Server/Windows 7,8 or 10)
● Wamp Server 3.0.6 or Higher/XAMP
● PHP 5.6.25 or Higher
● MySQL 5.7.14 or Higher
● Apache 2.4.23 or Higher
Interface Implementation
The system application software provides a clear and easy to use user interface. The system was
designed with independent forms that perform independent tasks. The programming languages
used in the implementation process was PHP and JavaScript.

User Training
There two aspects to user training:
Familiarization with the processing system itself
I.e. the equipment used for data entry or processing
Training in using the application
I.e. the software that accepts the data processes and produces the results
Student Information System P a g e 49 of 95
Conversion

Conversion is the process of changing from the old to the new one.

Pilot Approach

When new systems also involve new techniques or drastic changes in organization performance,
the pilot approach is often preferred. In this method a working version of the system is
implemented in one part of the organization such as a single work area or department. The users
in this area typically know that they are piloting a new system and that changes can be made to
improve the system.

When the new system is deemed complete, it is installed throughout the organization, either all at
once or gradually.

Front end and Back end technologies

Below is a summary of the technologies used, how and why they were used.

Table 4: Technologies used

Technology Purpose Why

PHP & Hypertext Markup HTML is what was used in The 2 technologies allow
Language (HTML) describing the rendering of separation of static data or
the pages while PHP was text from the code behind the
used in the development of pages.
dynamic web pages.
Cascading Style sheets (CSS) CSS was used to for styling CSS makes it easier to make
the pages and how they changes or define a style
would be rendered. because one change applies to
a number of items on a
number of pages. It also
brings about consistency in
terms of appearance and
styling.
JavaScript JavaScript was used for JavaScript helps to enforce
validating the forms. validation on the input forms.
MS SQL Server MySQL Server was used to SQL Server helps to improve
create the database and its Security. Its ability to
tables as well as enabling the integrate with Windows
querying of the database and Active Directory makes it is
implementing security and quite easy to determine how
access control to the database. the database is accessed.

Student Information System P a g e 50 of 95

5.2. Coding Details and Code Efficiency
5.2.1. Code Efficiency
The efficiency of the coding system is the ratio of the average information per symbol to the
average code length. The maximum efficiency is 1, and can theoretically be obtained using a
prefix code. However, the PHP programming language used in the development of SIS has more
efficient coding standards which include assigned of defined variables, encoding/decoding of
data etc.

5.3. Testing Approach

In this section, we will be more focused on the types of tests that were performed on the Online
Student Information System, so as to ensure that it meets the user requirements highlighted in the
design.
5.3.1. Unit Testing
System units called modules will be independently tested. Testing will help in locating errors
before any surprise after implementation.
5.3.2. Integrated Testing
This testing will involve orderly progression of testing which modules or which hardware
elements or both will be combined and then tested units and the entire system is integrated.

5.4. Modifications and Improvements

The system or way of applying will be enhanced when this system is implemented.

Since this system was developed using free and open source software, it will not only be easy to
upgrade or improve, but cheaper as well.

It is recommended that users are security conscious and not disclose their passwords to other
people.

Students’ records (details) are private and confidential, and must be treated as such.

Further work can be done to improve security and functionality; this has just been the beginning.

Student Information System P a g e 51 of 95

CHAPTER 6: RESULTS AND DISCUSSION

6.1. Test Reports

The test summary report outlines the summation of software testing activities and final testing
results. Software testers are required to communicate testing results and findings to project
stakeholders on the completion of testing cycle.

6.2. User Documentation

Procedure manuals are common organizational documents that most people have seen. They are
the English-language component of documentation, although they may also contain program
codes, flowcharts, and so on. Manuals are intended to communicate to those who use them. They
may contain background comments, steps required to accomplish different transactions,
instructions on how to recover from problems, and what to do next if something isn’t working
(troubleshooting). Many manuals are now available online, with hypertext capability that
facilitates use.

A straightforward, standardized approach to creating user support documentation is also

desirable. To be useful, user documentation must be kept up to date. Use of the Web has
revolutionized the speed with which assistance can be obtained by users. Many software
developers have moved user support—complete with manuals, FAQ pages, online chat, and user
communities—to the Web.

Key sections of a manual should include an introduction, how to use the software, what to

do if things go wrong, a technical reference section, an index, and information on how to contact
the manufacturer. The biggest complaints with procedure manuals are that (1) they are poorly
organized,

(2) it is hard to find needed information in them, (3) the specific case in question does

not appear in the manual, and (4) the manual is not written in plain English.

The user documentation manual for the new Student Information System is discussed in
APPENDIX A of this document.

Student Information System P a g e 52 of 95

CHAPTER 7: CONCLUSIONS

7.1. Conclusion
In this study we have introduced a database management system for students at Pokola Day
Secondary School in the North Western province of Zambia. The main objective to design and
carry out this system is to collect students' data in one place and making various transactions and
modifications on it and retrieve this data according to the need of generating the report, this
objective as well as the functions for which they were designed this system has been achieved.
This system will transfer the work in this department from the manual to the computer-based
system and is able to store huge data of the students, also enables the user to get access to data
through a user-friendly interface. In addition, this system can promote the management of
academic school to carry out its tasks high efficiently.

Student Information System can reduce time and effort required in the process of management
students' information, also the need for a large number of staff to carry out the functions of the
school, where the management of this system needs to only one employee, furthermore it will
help the administration of the school to speed decision-making, where this system has made it
possible for the administration of the school to use real-time data when making decisions, which
flows into the benefit of the school. The characteristics of this system is the answer for all the
questions raised from the purpose of this study.

7.2. Limitations of the System

 Financial resources: there were limited financial resources for printing the documentation
needed for the project. It will be better if the institution started funding the projects in future.
 Programing language used: it was difficult to learn a programing language and implement the
in a limited period of time. To make it easy, the students should be programing in
programing languages that they are supposed to use in their projects

7.3. Future Scope of the Projects

For further recommendations, linking Student Information System (SIS) with the school's
website enable the student to directly access all aspects of his academic study through the online
interface embedded on the school website. This online system can use a user authentication,
where every student has a username and password to display his information and give requests
online thus reducing time processing. Additionally, students can be involved in operations of
updating and modifying his information, which leads to faster order fulfillment.
Student Information System P a g e 53 of 95
REFRENCES
 Alshawaf, Abdulrida and Khalil, Omar E. M. (2008). IS Success factors and IS
organizational Impact: Does ownership type Matter in Kuwait? International Journal of
Enterprise Information Systems, 4(2).
 Kendall and Kendall, Eighth Edition, Systems Analysis and Design.
 Connolly T. M. and Begg C. E., (2010), Debases Systems: A Practical Approach to
Design, Implementation and Management, 5th ed., Boston: Pearson, pp. 340-344.
 http://www.webopedia.com. (Data Download Date: 3rd April 2020).
 http://www.researchgate.com. (Data Download Date: 3rd April 2020).
 Bennett, B, McRobb, S and Farmer, R, 2006, Object-Oriented Systems Analysis and
Design Using UML 3rd Edition, McGraw-Hill Education Limited United Kingdom NCC
education limited The Towers, Towers Business Park Wilmslow Road, and Didsbury
Manchester M20 2EZ, UK.
 Schwalbe K. (2010), “Managing Information Technology Projects”, CENCAGE
Learning, Australia.
 https://www.google.com/StudentInformationSystem. (Data Download Date: 12th May
2020).
 http://www.w3schools.com/html/html_intro.asp Date accessed (12/03/2020)

Student Information System P a g e 54 of 95

GLOSSARY
ACTOR In UML, a particular role of a user of the system. The actor exists outside the system
and interacts with the system in a specific way. An actor can be a human, another system, or a
device such as a keyboard. See also use case.

AJAX A method using JavaScript and XML to dynamically change Web pages without
displaying a new page by obtaining small amounts of data from the server.

ALIAS Alternative name for a data element used by different users. Recorded in a data
dictionary.

ATTRIBUTE Some characteristic of an entity. There can be many attributes for each entity.

BROWSER Special software that runs on an Internet connected computer enabling users to
view hypertext-based Web pages on the Internet. Microsoft Internet Explorer and Mozilla’s
Firefox are examples of graphical browsers.

CASE TOOLS Computer-aided software engineering tools that include computer-based

automated diagramming, analyzing, and modeling capabilities.

DASHBOARD Display for decision makers including a variety of displays of relevant

performance measurements.

END USERS In an organization, no information system professionals who specify the business
requirements for and use software applications. End users often request new or modified
applications, test and approve applications, and may serve on project teams as business experts.

ENTITY-RELATIONSHIP (E-R) DIAGRAM A graphical representation of an E-R model.

FAVICON A small icon displayed next to any bookmarked address in a browser. Copying the
bookmarked link to a desktop results in a larger version of the icon being placed there. Unique
favicons can be generated with a Java icon generator or with other graphics programs.

FIREWALL Computer security software used to erect a barrier between an organization’s LAN
and the Internet. Although it prevents hackers from getting into an internal network, it also stops
organizational members from getting direct access to the Internet.

Student Information System P a g e 55 of 95

IMPLEMENTATION The last phase of the systems development life cycle, in which the
analyst ensures that the system is in operation and then allows users to take over its operation
and evaluation.

INPUT Any data, either text or numbers, that are entered into an information system for storage
or processing via forms, screens, voice, or interactive Web fill-in forms.

PROCESS The activities that transform or change data in an information system. They can be
either manual or automated. Signified by a rounded rectangle in a data flow diagram.

OUTPUT Information delivered to users through the information system by way of intranets,
extranets, or the Web, on printed reports, on displays, or via audio.

PRIMARY KEY A key that uniquely identifies a record.

RECORD A collection of data items that have something in common with the entity described.

RELATIONSHIP Association between entities (sometimes referred to as data association); can

take the form of one-to-one, one-to-many, many-to-one, or many-to-many.

USE CASE In UML, a sequence of transactions in a system; the purpose is to produce

something of value to an actor in the system; focuses on what the system does rather than on how
it does it. The use case model is based on the interactions and relationships of individual use
cases. In a use case, an actor using the system initiates an event that begins a related series of
interactions in the system.

ACRONYMS
CSS cascading style sheets.

ERD Entity Relationship Diagram.

HTML hypertext markup language.

PHP hypertext preprocessor; an open source programming language.

SIS Student Information System.

SDLC systems development life cycle.

WWW World Wide Web.

Student Information System P a g e 56 of 95

APPENDIX A

Installation Manual

Introduction

This document aims to describe how the new Student Information System can be used
effectively. If this manual is effectively used, the user will get full benefits of this system without
any problems. It guides the user on the steps to take to effectively utilize the system as well as
way of coming out of problems in case they arise.

Scope and Objectives

The scope and objectives of the document is to give a detailed guideline and steps on the
operations and installations procedure of the system. These details will help the user in knowing
what each screen appearance entails and also what each message entails if displayed on the
screen.

System Requirements

The system is designed to work with the following minimal hardware and software requirements
for it to function properly.

Hardware Requirements:

● PIV 2.8 GHz Processor and Above

● RAM 512GB and Above
● HDD 50 GB free Hard Disk Space and Above
Software Requirements:
● WINDOWS OS (2003/ 2008 Server / 2012 Server/Windows 7, 8 or 10)
● Linux or Ubuntu Operating System
● Mac OS
● Wamp Server 3.0.6 or Higher
● Anti-Virus (Kaspersky Internet Security recommended).

Student Information System P a g e 57 of 95

Other Requirements
To run this system, there is need to have a Database Specialist (Database Administrator and/or
Data Administrator) who will ensure that Data is managed very well as it is the main purpose of
the whole program. The Network Administrator is also required.
System Operators (those that collect the data) will need to go for a short training in order to
effectively operate the system.

Installing the Application

Install the Wamp server. After installation; launch the Wamp server, go to the Task bar, on the
Taskbar Tray click on Wamp Server Icon then Select the PhpMyAdmin option

Click Here

Student Information System P a g e 58 of 95

Installing the Database

Click Here to Login to MySQL

Click here to import Database

Student Information System P a g e 59 of 95

 Click here to locate the Database Script and then Click Go to import

After clicking Import then click on Choose File and locate the database script name “sis.sql” and
then click Go.

User Manual

Launching application

In order to launch the system firstly you need to copy the folder which contains the project files
to C: /Wamp64/www/. After this then launch the browser and type localhost/sis/ in the web
browser’s address bar and then press enter button on your keyboard. The application verifies the
requirements on your machine, if it does not meet the requirements. If, however the requirements
are met, the screen below is displayed.

Student Information System P a g e 60 of 95

Home Page

Login to the System

The page above shows the login form, therefore in order for any user (e.g. Administrator,
Standard, Class Teacher, Teacher, Student etc.) to login to the system they will be required to
enter correct Username and Password and then click Login button to sign in.

If the wrong login credentials are entered, the following window below is displayed.

Student Information System P a g e 61 of 95

The screenshots below show the different dashboard and system menu for various system users
based on their access levels after login to the Student Information System has been successful.

Administrator Home Page

Student Information System P a g e 62 of 95

Standard User Home Page

Class Teacher Home Page

Student Information System P a g e 63 of 95

Teacher Home Page

Student Portal

Student Information System P a g e 64 of 95

 1. Education Standards
Education Standards is the component used to setup the level of education being offered at
school such as Early Childhood Education, Primary Education, Junior Secondary Education,
Senior Secondary Education etc.

2. Employee Management
The Employee Management Component helps with the management of employee data, it
consists of tools for recording employees and setting employee as teacher.

Student Information System P a g e 65 of 95

 ADDING NEW EMPLOYEE

Student Information System P a g e 66 of 95

 LIST OF EMPLOYEES

SETTING EMPLOYEE AS TEACHER

Student Information System P a g e 67 of 95

 3. Subjects Management
Subjects management is used to add subject offered under a specified Education Standard.
ADDING NEW SUSBJECT

LIST OF SUBJECTS

4. Classes Management

Student Information System P a g e 68 of 95

 ADDING NEW CLASS

LIST OF CLASSES

DEFING CLASS SUBJECTS

Student Information System P a g e 69 of 95

 Class subjects’ definition has got two options. You can assign multiple class subjects to a
single teacher or assign multiple teachers to a single subject.

ASSIGN MULTIPLE SUBJECTS TO A SINGLE TEACHER

ASSIGN MULTIPLE TEACHERS TO A SINGLE SUBJECT

Student Information System P a g e 70 of 95
 LIST OF CLASS SUBJECTS

Student Information System P a g e 71 of 95

 5. Students Management
ADDING NEW STUDENT
Student Information System P a g e 72 of 95
 STUDENT LIST

Student Information System P a g e 73 of 95

 ENROL STUDENT

6. Timetable Management

Student Information System P a g e 74 of 95

 SELECTING PERIOD START AND END TIME

CLASS TIMETABLE CHART

Student Information System P a g e 75 of 95

Student Information System P a g e 76 of 95
 7. Assessment Management
SETUP ASSESSMENT SCHEDULE

LIST OF ASSESSMENT SCHEDULES

Student Information System P a g e 77 of 95

 ENTRY OF ASSESSMENT RESULTS

Student Information System P a g e 78 of 95

 ASSESSMENT RESULTS SLIP

Student Information System P a g e 79 of 95

APPENDIX B

Technical Manual
Technical manual’ is a term for any manual with technical character. In this chapter we list down
the source codes in PHP programming language which was written during the development and
implementation of the new Student Information System.

Home /Login Page – Source Codes

<? php

function ExecuteLoginAuditTrail($UserID,$LoginTime,$LoginDate,$Action,$InstitutionID){

include 'config/db_config.php';

#Query for User Details

$Query=$conn->query("SELECT*FROM users WHERE UserID='$UserID' AND
InstitutionID='$InstitutionID'");
$row=$Query->fetch_array(true);

$UserGroup=$row['UserType'];
$FullName=$row['FullName'];
$ActionDate=date('Y-m-d');
$ActionTime=date('H:i:s');
$Online='TRUE';

$SQL="INSERT INTO
audittrail(UserID,UserGroup,FullName,Action,LoginDate,LoginTime,ActionDate,ActionTime,
Online,InstitutionID)
VALUES('$UserID','$UserGroup','$FullName','$Action','$LoginDate','$LoginTime','$ActionDat
e','$ActionTime','$Online','$InstitutionID')";

if($conn->query($SQL)){
}else{
echo "Failed to Execute Login Audit Trail: - ".$conn->error;
}

function ExecuteLogoutAuditTrail($UserID,$Action,$InstitutionID,$LogoutParty,
$LogoutPartyID){

include 'config/db_config.php';

#Query for User Details

Student Information System P a g e 80 of 95

$Query=$conn->query("SELECT*FROM users WHERE UserID='$UserID' AND
InstitutionID='$InstitutionID'");
$row=$Query->fetch_array(true);

$UserGroup=$row['UserType'];
$FullName=$row['FullName'];
$ActionDate=date('Y-m-d');
$ActionTime=date('H:i:s');
$Online='TRUE';

#Query for Login Audit Trail Details

$Q=$conn->query("SELECT*FROM audittrail WHERE UserID='$UserID' AND
InstitutionID='$InstitutionID' AND Online='TRUE'");
$rs=$Q->fetch_array(true);

$LoginTime=$rs['LoginTime'];
$LoginDate=$rs['LoginDate'];

#Query for Logout Party User Details

$QLP=$conn->query("SELECT*FROM users WHERE UserID='$LogoutPartyID' AND
InstitutionID='$InstitutionID'");
$rec=$QLP->fetch_array(true);

$LogoutPartyUserGroup=$rec['UserType'];
$LogoutPartyFullName=$rec['FullName'];

$LogoutDate=date('Y-m-d');
$LogoutTime=date('H:i:s');

$SQL="INSERT INTO
audittrail(UserID,UserGroup,FullName,Action,LoginDate,LoginTime,ActionDate,ActionTime,
Online,InstitutionID)
VALUES('$UserID','$UserGroup','$FullName','$Action','$LoginDate','$LoginTime','$ActionDat
e','$ActionTime','$Online','$InstitutionID')";

$SQLLogOut="UPDATE audittrail SET

LogoutDate='$LogoutDate',LogoutTime='$LogoutTime',LogoutParty='$LogoutParty',LogoutPar
tyID='$LogoutPartyID',LogoutPartyUserGroup='$LogoutPartyUserGroup',LogoutPartyFullNam
e='$LogoutPartyFullName',Online='FALSE' WHERE UserID='$UserID' AND
InstitutionID='$InstitutionID' AND Online='TRUE'";

if($conn->query($SQL) && $conn->query($SQLLogOut)){

}else{
echo "Failed to Execute Logout Audit Trail: - ".$conn->error;
}

}
Student Information System P a g e 81 of 95
?>

<?php
if(isset($_POST['btnsubmit'])){

date_default_timezone_set($_SESSION['TimeZone']);

$username=$_POST['username'];
$password=VicsoftEncrypt($_POST['password'],2);

$QRYLogin=$conn->query("SELECT*FROM users WHERE Username='$username' AND

Password='$password'");

if($QRYLogin->num_rows>0){

$row=$QRYLogin->fetch_assoc();
$Blocked=$row['Blocked'];
$usertype=$row['UserType'];
//$result=$conn->query("");

if($Blocked=='FALSE'){

$_SESSION['UserID']=$row['UserID'];
$_SESSION['UserCode']=$row['UserCode'];
$_SESSION['Username']=$row['Username'];
$_SESSION['Password']=$row['Password'];
$_SESSION['UserType']=$row['UserType'];
$_SESSION['Email']=$row['Email'];
$_SESSION['FullName']=$row['FullName'];
$_SESSION['PhoneNumber']=$row['PhoneNumber'];
$_SESSION['Blocked']=$row['Blocked'];
$_SESSION['Online']=$row['Online'];
$_SESSION['ActivationCode']=$row['ActivationCode'];
$_SESSION['InstitutionID']=$row['InstitutionID'];
$_SESSION['Status']=$row['Status'];
$_SESSION['LoginDate']=date("Y-m-d");
$_SESSION['LoginTime']=date("H:i:s");

#CHECK IF THE USER DIDN'T LOGOUT HIS/HER PREVIOUS SESSION

if($row['Online']=='TRUE'){

ExecuteLogoutAuditTrail($_SESSION['UserID'],'Logged out of the System',

$_SESSION['InstitutionID'],'User',$_SESSION['UserID']);

}
Student Information System P a g e 82 of 95
##########################################################

#ADMINISTRATOR, STANDARD, EXECUTIVE, HEAD TEACHER, CLASS TEACHER,

TEACHER
if($usertype=="Administrator" || $usertype=="Standard" || $usertype=="Executive" ||
$usertype=="Head Teacher" || $usertype=="Class Teacher" || $usertype=="Teacher" ||
$usertype=="Cashier"){

if($conn->query("UPDATE users SET LoginStatus='Logged In',Online='TRUE' WHERE

UserID='".$_SESSION['UserID']."'")){

ExecuteLoginAuditTrail($_SESSION['UserID'],$_SESSION['LoginTime'],
$_SESSION['LoginDate'],'Logged Into the System',$_SESSION['InstitutionID']);

header("location: A_TlRnMk5qUXc=/");
}else{
echo '<script>alert("Failed to Update Login Status Query: - '.$conn->error.'"); </script>';
}

#STUDENT
if($usertype=="Student"){

if($conn->query("UPDATE users SET LoginStatus='Logged In',Online='TRUE' WHERE

UserID='".$_SESSION['UserID']."'")){

ExecuteLoginAuditTrail($_SESSION['UserID'],$_SESSION['LoginTime'],
$_SESSION['LoginDate'],'Logged Into the System',$_SESSION['InstitutionID']);

header("location: S_TlRnMk5qUXc=/");
}else{
echo '<script>alert("Failed to Update Login Status Query: - '.$conn->error.'"); </script>';
}

}else{

$err="Your User Account has been Blocked!";

header("location: ./?err=".VicsoftEncrypt($err,1));

}
Student Information System P a g e 83 of 95
}else{

$err="Invalid User Account Login Credentials!";

header("location: ./?err=".VicsoftEncrypt($err,1));

$conn->close();

?>

Student Registration – Source Codes

<?php

include '../config/db_config.php';

$InstitutionID=$_SESSION['InstitutionID'];

if(isset($_POST['btnsubmit'])){

$StudentNumber=str_replace("'","",$_POST['studentnumber']);
$FirstName=str_replace("'","",$_POST['firstname']);
$SurName=str_replace("'","",$_POST['surname']);
$OtherNames=str_replace("'","",$_POST['othernames']);
$FullName=$FirstName.' '.$SurName.' '.$OtherNames;
$Gender=$_POST['gender'];
$Address=str_replace("'","",$_POST['address']);
$DateofBirth=explode("/",$_POST['dateofbirth']);
$DateofBirth=$DateofBirth[2].'/'.$DateofBirth[0].'/'.$DateofBirth[1];
$Email=str_replace("'","",$_POST['email']);
$PhoneNumber=str_replace("'","",$_POST['phonenumber']);
$BiologicalStatus=$_POST['biologicalstatus'];
$GuardianName=str_replace("'","",$_POST['guardianname']);
$GuardianGender=$_POST['guardiangender'];
$GuardianIDType=$_POST['guardianidtype'];
$GuardianIDNumber=str_replace("'","",$_POST['guardianidnumber']);
$GuardianAddress=str_replace("'","",$_POST['guardianaddress']);
$GuardianPhoneNumber=str_replace("'","",$_POST['guardianphonenumber']);
$guardianemail=str_replace("'","",$_POST['guardianemail']);
$RelationshipToChild=str_replace("'","",$_POST['relationshiptochild']);
$DateRegistered=date('Y-m-d');
$PostingAccountNumber=$_POST['postingaccountnumber'];
$Status=$_POST['status'];
Student Information System P a g e 84 of 95
$GurdianOccupation=str_replace("'","",$_POST['guardianoccupation']);

$query=$conn->query("SELECT*FROM students WHERE StudentNumber='$StudentNumber'

AND InstitutionID='$InstitutionID'");

if($query->num_rows==0){

if($conn->query("INSERT INTO
students(InstitutionID,StudentNumber,FirstName,SurName,OtherNames,Gender,Address,Dateof
Birth,BiologicalStatus,GuardianName,GuardianGender,GuardianIDType,GuardianIDNumber,G
uardianAddress,GuardianPhoneNumber,GuardianEmail,RelationshipToChild,DateRegistered,Po
stingAccountNumber,Status,GuardianOccupation,Email,PhoneNumber)
VALUES('$InstitutionID','$StudentNumber','$FirstName','$SurName','$OtherNames','$Gender','
$Address','$DateofBirth','$BiologicalStatus','$GuardianName','$GuardianGender','$GuardianIDT
ype','$GuardianIDNumber','$GuardianAddress','$GuardianPhoneNumber','$guardianemail','$Rel
ationshipToChild','$DateRegistered','$PostingAccountNumber','$Status','$GurdianOccupation','$
Email','$PhoneNumber')")){

#############################################################################
##############

if($conn->query("INSERT INTO
users(InstitutionID,Username,UserCode,Password,UserType,Email,FullName,PhoneNumber,Ge
nder,Blocked)
VALUES('$InstitutionID','$StudentNumber','$StudentNumber','".base64_encode(base64_encode
($StudentNumber))."','Student','$Email','$FullName','$PhoneNumber','$Gender','FALSE')")){

echo '<script>alert("Record Saved Successfully"); window.location="New Student";</script>';

}else{

echo '<script>alert("Failed to create Student User Account: - '.$conn->error.'");</script>';

#############################################################################
##############

}else{
echo '<script>alert("Failed to Save record: - "'.$conn->error.'");</script>';
}

}
else{
echo '<script>alert("The Student Number you have entered Already Exist")</script>';

}
Student Information System P a g e 85 of 95
}

?>

Class Timetable – Source Codes

<?php

session_start();

echo '';

if(isset($_POST['SchoolYear']) && isset($_POST['EducationStandardID']) &&

isset($_POST['ClassID']) && isset($_POST['SubjectID']) && isset($_POST['Day']) &&
isset($_POST['StartTime']) && isset($_POST['EndTime']) && isset($_POST['TeacherID']) &&
isset($_POST['AcademicPeriodID']) && isset($_POST['EntryType'])){

include '../config/db_config.php';

include 'Date Convetor.php';

$InstitutionID=$_SESSION['InstitutionID'];

$EducationStandardID=$_POST['EducationStandardID'];

$TeacherID=$_POST['TeacherID'];

$ClassID=$_POST['ClassID'];

$SubjectID=$_POST['SubjectID'];

$Day=$_POST['Day'];

$DayNumber=GetWeekDayNumber($Day);

$StartTime=$_POST['StartTime'];

$EndTime=$_POST['EndTime'];

Student Information System P a g e 86 of 95

$SchoolYear=$_POST['SchoolYear'];

$AcademicPeriodID=$_POST['AcademicPeriodID'];

$EntryType=$_POST['EntryType'];

$ShowDescription='FALSE';

if($EntryType=="Break Time"){

$ShowDescription="TRUE";

$qry=$conn->query("SELECT*FROM classes WHERE ClassID='$ClassID'");

$ry=$qry->fetch_array(true);

$ClassName=$ry['ClassName'];

$DAP=$conn->query("SELECT*FROM educationstandards WHERE

EducationStandardID='$EducationStandardID'");

$rs=$DAP->fetch_array(true);

$EducationStandardName=$rs['EducationStandardName'];

$qryS=$conn->query("SELECT*FROM timetable WHERE SchoolYear='$SchoolYear' AND

EducationStandardID='$EducationStandardID' AND ClassID='$ClassID' AND
StartTime='$StartTime' AND EndTime='$EndTime' AND Day='$Day' AND
AcademicPeriodID='$AcademicPeriodID'");

if($qryS->num_rows>0){

echo '<font style="font-weight:bold; color="#FF0000;">'."You have Already Assigned a

Subject in this Class Name: ".$ClassName." between ".$StartTime." and ".$EndTime." on this
Day: ".$Day.'</font>';

Student Information System P a g e 87 of 95

} else {

if($conn->query ("INSERT INTO

timetable(InstitutionID,ClassID,SubjectID,Day,DayNumber,StartTime,EndTime,TeacherID,Sch
oolYear,EducationStandardID,AcademicPeriodID,EntryType,ShowDescription)
VALUES('$InstitutionID','$ClassID','$SubjectID','$Day','$DayNumber','$StartTime','$EndTime','
$TeacherID','$SchoolYear','$EducationStandardID','$AcademicPeriodID','$EntryType','$ShowD
escription')")){

echo '<font style="font-weight:bold; color="#060;">'.'Timetable Schedule Line Added

Successfully'.'</font>';

?>

<?php

}else{

echo '<font style="font-weight:bold; color="#FF0000;">'."Failed to Add Class Timetable

Schedule Line: - ".$conn->error.'</font>';

?>

Save Assessment Results – Source Codes

<?php
session_start();

Student Information System P a g e 88 of 95

include '../config/db_config.php';

if(isset($_POST['AssessmentID']) && !empty($_POST['AssessmentID']) &&

isset($_POST['EducationStandardID']) && !empty($_POST['EducationStandardID']) &&
isset($_POST['ClassID']) && !empty($_POST['ClassID']) && isset($_POST['SubjectID']) && !
empty($_POST['SubjectID']) && isset($_POST['Marks']) && !empty($_POST['Marks']) &&
isset($_POST['StudentID']) && !empty($_POST['StudentID'])){

$InstitutionID=$_SESSION['InstitutionID'];
$AssessmentID=$_POST['AssessmentID'];
$EducationStandardID=$_POST['EducationStandardID'];
$ClassID=$_POST['ClassID'];
$SubjectID=$_POST['SubjectID'];
$StudentID=$_POST['StudentID'];
$Marks=number_format($_POST['Marks']);
$Grade='';
$Remarks='';
$ISAbsent='FALSE';

#Assessments Query
$DAP=$conn->query("SELECT*FROM assessments WHERE
AssessmentID='$AssessmentID'");
$rs=$DAP->fetch_array(true);

$SchoolYear=$rs['SchoolYear'];

#Student Enrollment Query

$QueryStudentEnrollment=$conn->query("SELECT*FROM enrollment WHERE
StudentID='$StudentID' AND ClassID='$ClassID' AND SchoolYear='$SchoolYear' AND
InstitutionID='$InstitutionID'");
$rStudentEnrollment=$QueryStudentEnrollment->fetch_array(true);

Student Information System P a g e 89 of 95

$EnrollmentID=$rStudentEnrollment['EnrollmentID'];

#Calculate Grade and Remarks

$QGrading=$conn->query("SELECT*FROM gradingsetup WHERE
EducationStandardID='$EducationStandardID'");

while($rGrading=$QGrading->fetch_array(true)){

if($Marks>=$rGrading['MinMarks'] && $Marks<=$rGrading['MaxMarks']){

$Grade=$rGrading['GradeName'];
$Remarks=$rGrading['Remarks'];
}

if($conn->query("INSERT INTO
assessmentresults(AssessmentID,InstitutionID,EnrollmentID,StudentID,ClassID,SubjectID,Mark
s,Grade,Remarks,ISAbsent)
VALUES('$AssessmentID','$InstitutionID','$EnrollmentID','$StudentID','$ClassID','$SubjectID',
'$Marks','$Grade','$Remarks','$ISAbsent')")){
//echo 'Student Subject Assessment Results Added Successfully';
}else{
echo 'Failed to Add Student Assessment Results: '.$conn->errno.' - '.$conn->error;
}

?>
Student Information System P a g e 90 of 95
<!----Assessment Results Entry Table will be Displayed Here----------------------------------------->

<div class="module-body table">

<table id="example"
class="table table-bordered" cellspacing="0" width="100%">

<thead>
<tr>

<th><input
type="checkbox" onClick="return SelectAll(this);" /></th>

<th>
Subject Name
</th>

<th>Marks</th>

<th>Grade</th>

<th>Remarks</th>

</tr>
</thead>
<tbody>
Student Information System P a g e 91 of 95
<!--------------------Begin Already Entered Subject Marks Part------------------------------------->
<?php

$QSubjectResults=$conn->query("SELECT
`assessmentresults`.`AssessmentResultID`
, `assessmentresults`.`AssessmentID`
, `assessmentresults`.`InstitutionID`
, `assessmentresults`.`EnrollmentID`
, `assessmentresults`.`StudentID`
, `assessmentresults`.`ClassID`
, `assessmentresults`.`SubjectID`
, `assessmentresults`.`Marks`
, `assessmentresults`.`Grade`
, `assessmentresults`.`Remarks`
, `subjects`.`SubjectName`
FROM
`assessmentresults`
INNER JOIN `assessments`
ON (`assessmentresults`.`AssessmentID` = `assessments`.`AssessmentID`)
INNER JOIN `subjects`
ON (`assessmentresults`.`SubjectID` = `subjects`.`SubjectID`)
INNER JOIN `students`
ON (`assessmentresults`.`StudentID` = `students`.`StudentID`)
WHERE `assessmentresults`.`AssessmentID`='$AssessmentID' AND
`assessmentresults`.`StudentID`='$StudentID';");

if($QSubjectResults->num_rows>0){

Student Information System P a g e 92 of 95

while($rSR=$QSubjectResults->fetch_array(true)){

?>
<tr>
<td><input type="checkbox" name="check[]" value="<?php echo
$rSR['AssessmentResultID']; ?>" id="all" /></td>
<td><?php echo $rSR['SubjectName']; ?></td>
<td><?php echo number_format($rSR['Marks']); ?></td>
<td><?php echo $rSR['Grade']; ?></td>
<td><?php echo $rSR['Remarks']; ?></td>

</tr>

<?php
}
}
?>

<!--------------------End Already Entered Subject Marks Part--------------------------------------->

<tr>
<td style="width:10px"><input
type="checkbox" name="check[]" style="width:10px" value="" id="all" /></td>
<td style="width:240px">
<select data-placeholder="Select here.." name="subjects" style="width:240px" id="Subjects"
required>

<option value="">Select Subject Name</option>

Student Information System P a g e 93 of 95

<?php
$QFY=$conn->query("SELECT
`classsubjects`.`ClassSubjectID`
, `classsubjects`.`ClassID`
, `classsubjects`.`SubjectID`
, `subjects`.`SubjectName`
FROM
`subjects`
INNER JOIN `classsubjects`
ON (`subjects`.`SubjectID` = `classsubjects`.`SubjectID`)
WHERE `classsubjects`.`ClassID`='$ClassID';");

while($FYRows=$QFY->fetch_array(true)){
?>
<option value="<?php echo $FYRows['SubjectID']; ?>"><?php echo
$FYRows['SubjectName']; ?></option>
<?php
}
?>

</select>

</td>
<td
style="width:40px">
<input type="text" style="width:40px" name="marks" id="Marks" />
</td>
<td
style="width:160px"><input type="text" name="grade" id="Grade" readonly
style="background-color:transparent; cursor:inherit; width:160px;" /></td>
Student Information System P a g e 94 of 95
<td><input type="text" name="remarksentry" id="RemarksEntry" readonly style="background-
color:transparent; cursor:inherit;" /></td>
</tr>
</tbody>

</table>

</div>

<!-------------------------------------------------------------------------------------------------->

<?php
}else{
echo '';
}
?>

Student Information System P a g e 95 of 95