School Management System Design Study
School Management System Design Study
BY
UJ/2018/2019/DCS/0014
SCIENCE,
UNIVERSITY OF JOS,NIGERIA
DECEMBER,2023.
Contents
APPROVAL............................................................................................................................................. ⅰ
1
2
DEDICATION.......................................................................................................................................... ⅱ
ACKNOWLEDGEMENT...........................................................................................................................ⅲ
ABSTRACT............................................................................................................................................. ⅳ
TABLES OF FIGURES...............................................................................................................................ⅴ
LIST OF TABLES...................................................................................................................................... 10
CHAPTPER ONE..................................................................................................................................... 12
INTRODUCTION.....................................................................................................................................12
1.1PROBLEM AREA................................................................................................................................15
CHAPTER TWO...................................................................................................................................... 20
2.3 CONCLUSION...................................................................................................................................29
CHAPTER 3............................................................................................................................................ 30
PROPOSED SOLUTIONS......................................................................................................................... 30
3.0 INTRODUCTION...............................................................................................................................30
2
3
3.3 CONCLUSION...................................................................................................................................36
CHAPTER 4............................................................................................................................................ 37
4.1 INTRODUCTION............................................................................................................................ 37
4.5 TESTING........................................................................................................................................ 39
4.10 SUMMARY.....................................................................................................................................51
CHATPER 5.............................................................................................................................................52
5.1 OVERVIEW.................................................................................................................................... 52
5.5 RECOMMENDATIONS................................................................................................................... 54
5.6 SUMMARY.................................................................................................................................... 54
REFERENCES..........................................................................................................................................56
APPENDIX B – Questionnaire................................................................................................................ 60
3
4
DECLARATION
I hereby declare that this work project by GEOFFREY DANLAMI BARJE was
carried out under the supervision and my guidance Mr. DAVID E. OGUCHE
This documentation has not been presented elsewhere for the award of
diploma in the department of computer science University of Jos. All sources
have been duly distinguished and appropriately acknowledge.
4
5
APPROVAL
This research project is read and approved as meeting the standard required in
the Department of computer science ,faculty of
Natural Science, University of Jos, for the award of Diploma in computer
Science.
5
6
DEDICATION
6
7
ACKNOWLEDGEMENT
Finally many thanks to my Elder brother [Link] Nathan also my friends, who
have helped and given suggestion, supports and sincere thanks to my parents
for their counter supports and encouragement. corrections throughout the
project.
7
8
ABSTRACT
8
9
9
10
10
11
Figure [Link]
Form……………………………………………………………………….22
Figure [Link]
Form………………………………………………………………………………
..23
Figure [Link]'s
Record………………………………………………………………........24
11
12
Figure [Link]
record……………………………………………………………………………
…25
LIST OF TABLES
Table.3.2Functional requirement
specification…………………………………………30
12
13
CHAPTPER ONE
INTRODUCTION
13
14
PROBLEM AREA
In order to control absentees and know the number of days that a student has
been absent from the school during the school days the attendance officer has
to collect the attendance slips from the corresponding homeroom teachers and
compile it which is also a time taking process.
AIMS
OBJECTIVES
14
15
in The School Management System (SMS) is responsible for duties like student
keeping track of staff information. SMS gives managers the knowledge they
need to run an
15
16
organization effectively and efficiently. These systems stand out from other
information
systems because they are made to be utilized for strategic and operational
analysis and
1.1PROBLEM AREA
16
17
Due to the inefficiency of the current manual system, the need arises to
automate School Management System in order to efficiently handle
students’ attendance, to produce transcript, report cards and the various
reports satisfying users and customers and to produce timetable which
can schedule courses for teachers and classes of students (Bober, 2001).
17
18
18
19
In Chapter Four, the design for the system set out in Chapter
Three is implemented detailing how the system would be
developed, what tools will be used in the development and
what would be required for the development of the system,
satisfying the remainder of the requirements of Objective
II.1.7 SCOPE AND LIMITATION
This study covers the school management system for secondary school
management using Salama High School Jos. Its strictly focuses on school
management records.
The Study is outlined according to chapters, each dealing with a specific subject
under the Study. An overview of these chapters follows.
1.9.1 CHAPTER TWO: LITERATURE REVIEW; Here, a literary basis is formed for
the Study; current systems of information are explored and the system users
are identified based on a review of their media consumption habits.
19
20
from the data collection are analysed and determinations are made. A
specification of requirements is defined from the analysed data. Building off of
this specification, the prototype is designed in this Chapter.
1.9.5 CONCLUSION:
This chapter started by introducing the research work and discussing the
background of study. The problem areas and statement was identified and the
primary aim of the project was set. Objectives for the research work were
defined alongside the methodology for achieving these objectives. The scope
and limitation of the project were also highlighted. the next Chapter shall go
into detail forming a literary basis for the Study.
20
21
CHAPTER TWO
INTRODUCTION
21
22
This chapter covers the literature review of the techniques and technology
used in this thesis. It also provides information on numerous studies carried
out by distinguished experts and clarifies terminology pertaining to the
creation and use of a school management system. The chapter provides a
summary of the problem's past and present state, which is outlined by a review
of earlier research on closely similar issues.
For instance, six hundred million dollars ($600,000,000) in loans was approved
by the World Bank to be taken out on June 25, 1998, and July 26, 2004, for
Turkey's Primary Education Program. In the first phase of the program, at least
two elementary schools in each of Turkey's 921 counties received information
technology equipment before being put into operation. Twenty-five thousand
(25,000) teachers and two thousand, two hundred and fifty (2,250)
22
23
23
24
24
25
staff performance (Telem, 1999). To understand more about how schools are
advancing their capacity to include ICT into learning, teaching, and
management processes, several surveys have been developed in recent years.
Literature has shown a gradual rise in the use of computers and other
technologies, with most schools meeting the baseline goals for
computer-to-pupil ratios. This statistic somewhat conceals the wide range of
access to reliable technology and broadband connectivity that exists both
inside and between schools (Rae Condie & Bob Munro, 2007). A survey of 98
elementary school principals was conducted in Turkey to learn more about how
they felt about the usage of School Management Systems in managing primary
and secondary schools. The study found that School Management Systems
made a significant contribution to school management even if the
technological infrastructures of elementary schools were lacking. Additionally,
the school administrators were advised and persuaded to adopt information
systems, that data are important sources for making decisions, and that School
Management Systems support the implementation of educational changes
(Demir, 2006). Information systems assist innovations as well as information
processes. These solutions can help you deal with the need for change because
they are flexible. As a result, school management systems help the school
better adapt to its surroundings. They enable the school to comprehend and
describe inward and outward information transfer. Thus, school administration
satisfies the needs and desires of both its internal and external (teacher,
student) members and guarantees that school activities are scheduled
precisely and on time. (Haag & Cummings, 2010). The implementation of a
school management system has significantly altered the duties and working
methods of school management (Telem, 1999). The school management
system has altered leadership, decision-making, workload, human resource
25
26
26
27
managers claimed that using these systems had given them access to
technologies and facilities, reduced their workload, made management
processes more efficient, helped them use their time more effectively, made
teachers feel more important, made them and the teachers want to improve
themselves more, and made them more impatient (Gurr, 2000). It was also
found that school managers believed that school management systems result
in significant changes at schools in their study with school managers. The
quality of teaching programs has grown, student-teacher interaction has been
facilitated, teacher coordination has improved, and systematic and continuous
information transfer to parents has all been made easier thanks to this
application, say school administrators (Telem, 1999). Finally, Anderson and
Dexter pointed out that school managers' technological leadership is more
crucial than their prior knowledge of how to use technology effectively in
classrooms (Anderson & Dexter, 2005). Education is not something separate
from life and society, but rather the process of learning to live as a useful and
acceptable member of the community. Education is one of the foundations of
shaping human beings and existed long before organized schools were ever
thought of. It is significant to remember that formal education, as provided in
schools, is one of the influences on people that is least lasting. The ancient and
contemporary educational systems are both fully 10 recognized as socialization
and economic development agents. According to Filter, "one of the issues our
schools face today is insufficient student attention and inaccurate judgment of
student achievement." The phrase "assessment" typically carries negative
connotations, particularly for students enrolled in academic programs. Even
though higher performance and public accountability are the main goals of
student education and the evaluation of its consequences, students rarely see
these prospects for growth. Instead, evaluation is viewed by students as a
27
28
barrier based on danger. Evaluation barriers, which are usually driven by a fear
of failure and have negative repercussions for those who fail, channel learner
behavior and thought. In such student-faculty agreements, evaluation is viewed
as a tool to increase student competency and safeguard the public. Most
students submit to the evaluation procedure reluctantly; rarely do they seek
out and appreciate the process (Haag & Cummings, 2010). In industrialized
countries, students are formally evaluated at strategic points in the curriculum
to gauge and record their satisfactory progress toward achieving their learning
goals and required competences. At designated points during each course,
these reviews take place regularly. These evaluations are made to rate
students' levels of knowledge, problem-solving abilities, psychomotor and
clinical competence, and behavioral performances during each course and/or
fieldwork experience, depending on the learning and competency outcome
objectives. Depending on the course or experiential learning opportunity,
different evaluation techniques may be used, such as formal exams, written
essays, portfolio assignments, design and fabrication projects, psychomotor
skills testing, or other techniques to gauge how well each student has mastered
the course material and skill competencies. In formal exams, student
performance is evaluated using a standard grading scale that is based on the
nation's or school's regulation and is graded using a numerical/alphabetical
system. Following each exam, students are typically given feedback and grade
reports reflecting their performance on each test item. Throughout their
academic career, students will be asked to take part in competency-based
examinations at various points (Anderson & Dexter, 2005). Primary school
evaluation has a positive side, especially when both students and instructors
agree that producing outstanding pupils is the goal. The focus shifts from
enforcement to improvement and mastery when educational evaluation
28
29
statistics are used as a tool rather than a weapon. This perspective also alters
the psychological environment in favor of positive advancement as opposed to
apprehension (Demir, 2006).
29
30
needs of the students, assisting school administrators and other staff with their
duties, and enhancing their performance, effectiveness, and efficiency (Gurr,
2000).
2.3 CONCLUSION
The literature review was carried out under the main headings, which are
introduction, historical overview, and related works. Different aspects have
been examined in this chapter, theoretical and conceptual frameworks that
30
31
CHAPTER 3
PROPOSED SOLUTIONS
3.0 INTRODUCTION
This chapter explores the design method and numerous procedures carried out
in adopting this design. It also describes in detail the system design
methodology. Methodology is one the most crucial sections in any project. The
31
32
various data collection techniques are introduced, along with how they are
employed in the project, for the reader. Data collection is necessary for any
analysis to have meaning. The requirements specifications were also discussed
which includes user requirement, system requirement, functional
requirements, and non-functional requirements of the proposed system.
Additionally, the class diagram, sequence diagram, activity diagram, use case
diagram of the proposed system, and description of the use cases were
discussed, as well as the necessary hardware and software to execute the
system.
Table 3.2
Table 3.1
32
33
R-103 The system should have login capabilities that allow Functional
users to have allowed access.
R-105 The system should display all the current teachers Functional
registered
33
34
immediately observe. (Paech, 2002). Table 3.3 displays the list of nonfunctional
requirements required for the system being designed.
These are formal technique to depict how a system interacts with its
surroundings. A use case diagram helps the stakeholders understand the
34
35
system and the services the system provides. Knowing how the system works is
beneficial to the user. Figure 3.1 is the use case diagram for the system being
designed.
algorithm usually refers to a small procedure that solves a recurrent problem. Algorithms are
also used as specifications for performing data processing and play a major role in
automated.
35
36
36
37
3.3 CONCLUSION
37
38
CHAPTER 4
38
39
4.1 INTRODUCTION
This application is a web portal, and its main objective is to assist in the
management of students and staff. Each activity has its dedicated area on the
dashboard. The API is designed to interface all the activities with the database.
The application was implemented through coding. Some of the codes that were
used to implement this application will be further shown to explain the main
features of this application.
39
40
To address each problem that would limit the development of this application,
each issue has been identified and investigated. The majority of the bugs were
fixed through looking online for people who had encountered the same or
similar issues and checking for a solution. The best course of action if a
particular one is unique and cannot be located is to submit the problem online
on a website like Stack-overflow or Git-hub, where developers will respond
with a potential solution within a few hours. An example of problems faced is:
Integrating the database I had issues integrating the database. I kept on getting
errors like uncaught type error, undefined array key I so on. I resolved this by
going through the JDC documentation on the official java website and also
watching a lot of YouTube videos”.
4.5 TESTING
Software testing provides the final assessment of the specification, design, and
code and is a critical component of software quality assurance. System testing
is a crucial stage that presents an intriguing software anomaly. As a result, the
proposed system must undergo a number of tests before it is ready for user
acceptance testing. A program is tested by being run with the goal of
identifying any errors. A test case is effective if it has a high chance of spotting
an error that hasn't been noticed before. A test that finds a previously
unknown error is considered successful. Several tests were conducted such as
unit test, integration test, system test, and acceptance test.
40
41
Integration Test: This test is the one that follows the unit test. The modules that
have undergone individual unit testing are then combined to create aggregates.
The huge aggregates are then tested according to the integration test plan.
System Test: This comes after the integration test. Each module's integration is
examined during system testing. Additionally, it checks for inconsistencies
between the system's current specification, initial aim, and system
documentation.
The user guide explains how the product will be used to its fullest potential by
its users. It serves as a reference tool for users when they run into issues using
the application and outlines each user role when using it. The screenshots and
operation of the implemented system are introduced and shown below.
Log In Screen: The user login on this page. Upon pressing the Log In butter or
enter, the user is redirected to the dashboard
41
42
42
43
43
44
Teacher Form (Admin Dashboard): Clicking the teacher form page on the
admin dashboard opens up a form for the teacher registration. Figure 4.3
below shows the teacher form required to register a new teacher into the
system.
44
45
Admission Form (Admin Dashboard): Clicking the Admission form page on the
admin dashboard opens a form where you can register a new student. Figure
4.4 below shows the student form required to register a new student into the
system.
45
46
Staff Form (Admin Dashboard): Clicking the Staff form page on the admin
dashboard opens a form where you can register a non-teaching staff. Figure 4.4
below shows the staff form required to register non-teaching staff into the
system.
46
47
Teachers record Clicking on teachers record the page on the admin dashboard
opens a form where you can view list of teaching staff. Figure 4.4 below shows
the list of teaching staff in the system.
47
48
Staff records Clicking on teachers record the page on the admin dashboard
opens a form where you can view list of non-teaching staff. Figure 4.4 below
shows the list of non-teaching staff in the system.
48
49
For a system to be used efficiently and accurately, all computer software needs
and are often used as a guideline as opposed to an absolute rule. Most software
increasing demand for higher processing power and resources in newer versions
suggest that this trend plays a bigger part in driving upgrades to existing
organization starts with a set of Business requirements and then derives the
System requirements from there. The most common set of requirements defined
49
50
behaviour of a system to be developed and may include a set of use cases that
describe interactions the users will have with the software. In addition it also
the basis for agreement between customers and contractors or suppliers on what
design can begin and reduces later redesign. The software requirements
50
51
have clear and thorough understanding of the web app to be developed or being
developed. The software components used for this project includes the
IV. JAVA.
V. RAM 512MB.
These individuals performed the same activities tested under system testing
with a variety of devices with Android versions ranging from Android 6.0 to 9.0.
The testers were asked to perform a subset of the tasks detailed in the system
testing covering all tasks. All testers performed their tasks without interference
from the developer and were asked to make observations as they carried out
the tasks. All testers were successful in performing the tasks documented in the
system testing above.
51
52
4.10 SUMMARY
This chapter briefs the reader on the main features of the application and
describes in detail the implementation procedures used, the issues
encountered, and the steps taken to overcome these issues. It previews the
tests run on the system with test cases. In the software development life cycle
of a project, this chapter is extremely important because proper
implementation is necessary to deliver a dependable and efficient system that
satisfies the requirements of the organizations; an improper installation may
affect the efficiency and overall general output of a system.
52
53
CHAPTER 5
5.1 OVERVIEW
This is the final chapter of the thesis. In it, we’ll go over an objective
assessment of the project, discuss the limitations and challenges faced during
the development and also analyze plans for future enhancements for this
project. and finally, recommendations will be made, based on the findings of
this project.
53
54
The biggest issue I encountered during this process was a system crash. Luckily
my important files backed up and I was able to recover the project although I
had to start the documentation again. Another hurdle encountered were
coding errors during implementation which were very stressful, but now that
the system is operating effectively, all the obstacles and hurdles I encountered
while implementing are in the past.
Even though I made every attempt to make the software adaptable and simple
to use, limitations are unavoidable. Although the software offers its user a wide
variety of options, some complex features could not be covered, in part
because of a lack of sophistication. A fundamental constraint was time;
therefore, it was impossible to create software that was both dynamic and
error-free. I had to neglect some things since I ran out of time. Some features I
would like to add in the future include:
54
55
5.5 RECOMMENDATIONS
5.6 SUMMARY
55
56
REFERENCES
Bradford, P., Porciello, M., Balkon, N., & Backus, D. (2007). The Blackboard
Learning System: The Be All and End All in Educational Instruction? Journal of
Educational Technology Systems, 35(3), 301–314.
[Link]
Bregzis, R., Gotlieb, C., & Moore, C. (2002). The beginning of automation in the
University of Toronto Library, 1963-1972. IEEE Annals of the History of
Computing, 24(2), 50–70. [Link]
56
57
57
58
[Link]
ools-AGuide-for-School/Johnson-Jr-Uline-Perez/p/book/9780815384458
Richey, R. C., & Klein, J. D. (2014). Design and development research. Handbook
of Research on Educational Communications and Technology: Fourth Edition,
141–150. [Link] 53
58
59
Scholtz, S. E., de Klerk, W., & de Beer, L. T. (2020). The Use of Research
Methods in Psychological Research: A Systematised Review. Frontiers in
Research Metrics and Analytics, 0, 1.
[Link]
Vorkink, A. N., Griffin, C. C., Mclaughlin, M., & Sahmali, F. (2004). The World
Bank THE REPUBLIC OF TURKEY FOR A BASIC EDUCATION PROJECT IN SUPPORT
OF THE FIRST PHASE OF THE BASIC EDUCATION PROGRAM Human
Development Sector Unit Europe and Central Asia Region.
Weber, G. (2011). Defining the paperless workplace with the paper metaphor:
not a contradiction in terms. Conference: Proceedings of the Fourth
Australasian Workshop on Health Informatics and Knowledge Management -
Volume 120.
[Link]
s_workplace_w ith_the_paper_metaphor_not_a_contradiction_in_terms Yuen,
59
60
A. H. K., Law, N., & Wong, K. C. (2003). ICT implementation and school
leadership: Case studies of ICT integration in teaching and learning. Journal of
Educational Administration, 41(2).
[Link]
APPENDIX B – Questionnaire
· How is Continuous Assessment carried out for the students? Response: This is
conducted in terms of tests, midterms, and assignment. The score is based on
maximum 30%, while the remaining 70% goes to final examination.
· How do you keep the students and teachers’ records? Response: We use files
to save and store student records. This method is inadequate and insecure, and
it has led some documents being eaten by termites/insects and decaying
sometimes they go missing or maybe even taken by trespassers and are easily
misplaced by those in charge of them.
60