Megi Duci
Megi Duci
Abstract
This paper aims to document all the stages of the development of a management system
for a non-public educational institution. Through the use of the latest literature and the
qualitative method of data collection, this paper presents each element of the phases of the
life cycle of the development of a system, based on the most efficient methodology, carried
out concretely to meet the objectives and requirements presented by the selected school. The
work’s main goal is to design and implement an automated system based on the web, to
replace the current system with which the school staff works daily. The reason is related to
the problems encountered during the realization of various routine tasks, which are delayed,
inefficient, inconvenient, and deficient in functionality. In addition to the loss of time, high
possibility of errors, low level of cooperation and marked lack of transparency, manual
management of the school process requires a lot of human effort and ongoing monetary
costs. To help promote student achievement and success, the institution must have access
to complete, accurate, and real-time information. Therefore, the proposed system, passing
through the planning phase, the analysis of every data and report collected, the design of
the prototype, and the development of the final product, is ready to be implemented in the
school, achieving error-free, safe, reliable, and fast procedures.
The education system forms the backbone of any nation and therefore it is
important to provide a strong educational foundation to the younger generation
to ensure the development of open-minded global citizens. Since education is
essential for development, it is considered one of the most powerful instruments in
laying a foundation for sustainable economic and social growth. With this aim, our
country for years has paid special attention to the education sector and activities
for the improvement of relevant institutions, such as schools of different levels,
from preschool to high school. To help promote student achievement and success,
schools must have access to complete, accurate, and real-time information.
Unfortunately, public and non-public schools in our country still record data
through paper-based documentation systems for conducting various studies and
generating reports and information that administrators and other employees need
to make routine decisions and more. The manual procedures of different tasks
take time and may not be completely accurate, since some of the recorded data
may be left uncalculated and taken into consideration, as an error on the part of
the employee who is manipulating and using them or by the employee who may
have performed the initial registration, not in the correct format. In addition to
the problem of spending time and the possibility of mistakes, there is also the
problem of transparency, since data can be manipulated without leaving a trace in
the documents or, due to the lack of correctness on the part of the employees, they
are not delegated to the people who should have access in them, such as a parent’s
knowledge of their child’s grades. So, in other words, this manual system is not
reliable, besides slow and not at all efficient.
Due to the problems of the current manual system, there is a need to automate
it to efficiently handle every registration, update, and deletion of data, generate
complete and fast transcripts and reports that satisfy the users and realize
continuous communication, transparency in processes, and continuity in periodic
updates. The motive for the realization of this work arose from the current situation
of educational institutions. The desire to implement my knowledge in the field of
development, to help improve management and coordination in schools such as
the high school where I completed my secondary studies, prompted me to work on
the design and construction of a computer-based management system.
The general and main objective of the project is the design and implementation
of a web-based computer system for data management of “Preka College”, to move
from the traditional manual system to an automated one, significantly improving
the process of data storage and data manipulation of this institution. To achieve the
general objective, I aim to achieve these specific objectives:
INGENIOUS No. 1, ISSUE 2/ 2021 93
• To record data accurately to increase transparency and efficiency throughout
the necessary processes, thus reaching a management system without errors,
that is safe, reliable, and fast.
• To create a large volume grouping with real and current data of the institution.
• To carry out quality communication with the database to generate reports
in real-time and with high authenticity thus helping in the decision-making
process.
• To build a specific profile for the role of the system administrator with full
access rights, as well as a profile for students, teachers, and parents, with
more limited access rights.
• Successfully carry out all the tasks and communications that will be assigned
to each of the profiles by the real relationships outside the system, to
emphasize once again the collaborative environment.
• Follow the activities of students and teachers through updates related to
timetables, grades, exams, payments, announcements, or direct messages.
Literature Review
Most organizations find it useful to use a standard set of steps, known as a system
development methodology, to develop and support their information systems.
Like many processes, information systems development often follows a life cycle,
known as the Software Development Life Cycle (SDLC). Scholars and researchers
describe the system development life cycle as a methodology used to develop,
maintain, modify or completely replace existing information systems through the
phases of planning, analysis, design, implementation, and maintenance (Gillenson
et al., 2011).
To propitiously develop the school management system, it is necessary to
choose the right methodology. Gillenson et al. (2011) in their study stated that
the choice of the appropriate methodology determines the quality of the system,
meets or exceeds the expectations of the end users, and reduces the subsequent
costs to be managed and improved. However, the choice of methodology depends
on the size and type of project, therefore no methodology is the absolute best; all
models have their advantages and disadvantages, and the key is to be flexible and
find what works for the organization and end users (Satzinger et al., 2015). In this
section, the selection of the appropriate development will be carried out as well as
the reasoning why, just as in the case of the selection of the information system.
Let us first deal with the SDLC phases, which are presented in the diagram below:
According to (Stanisevic et al., 2011) the choice of methodology is not easy because
no methodology is always the absolute best. However, based on the characteristics
of each of the methodologies, an ideal one can be selected even in the case of
a school management system. We can achieve a result if we make a comparison
between the methodologies used in different situations based on these criteria:
the user’s ambiguous requirement, which emphasizes the team’s ability to adapt
to the situation when the user does not know how the system should be or what
his system should do; the ability to adapt to a new technology that cannot be used
by users; the complexity of the system; reliability; the user’s estimated time for the
final project; visibility from iterated parties and finally documentation along the
way.
After evaluating the previous criteria throughout a development project, it
seems that the throwaway prototype methodology is the most appropriate one to
develop the new management system proposed in this paper. With the help of the
selected methodology and the cooperation of all interested parties, the existing
system will be analyzed, later to design and build the prototype of the system, which
the users will evaluate and give corrective feedback, thus understanding what the
system can do. According to (Sami, n.d.) throwaway prototyping methodologies
are excellent choices when timelines are short, which once again emphasizes that
development through “throwaway” prototypes is the most appropriate to follow in
this case study.
In conducting any type of research, the researchers must understand the particular
problem they aim to solve; this will help them understand the various important
areas of research evaluated. Therefore, through this chapter, I intend to highlight
the real problems of the current manual system that “Preka College” continues to
use in its daily life and the expectations of end users towards the new digital system.
To proceed with the phases of this cycle, it is first necessary to carry out research.
This is an organized investigation that uses conventional scientific methodology to
solve problems and create new knowledge that is generally appropriate, to create
and achieve new conditions (Goundar, 2012).
Given the purpose of this paper and the data it needs, this research will focus
entirely on qualitative research, which is described as collecting, analyzing, and
interpreting data by observing what people do and say; to discover meaning, and
feel and giving a broad description of the exact situation. It is necessary, to help the
college under study, to know more about the problems of the current system and
how it can be changed to be more user-friendly. The best way to collect the data
needed would be to interview the administrator and the head of “Preka College”.
For years now, most of these schools have made it part of their regulations to
keep up-to-date with the opinions and suggestions that come from these external
factors periodically, so the school leaders are aware of the problems and needs of
the students, their parents, and employees as well. This justifies the reason why
part of this study will be an interview with the two persons responsible for the
administrative and managerial parts of the school. Two main things are intended
to be achieved through the interview: pointing out the problems that require
solutions and suggestions from the interviewed staff regarding those requirements
that they have and want to see implemented in the system that will be developed.
Planning
Analysis
During this phase, it is essential to do a proper study of all the needs presented
by the school, its staff, and third parties, problems, and requirements, which we
can group according to users or system elements. If through the analysis of the
responses from the interview it is possible to identify opportunities and areas for
improvement, then a concept for the new system can be easily developed, and by
understanding where these requirements come from, we can specify who are the
users who will interact with the proposed system. According to the representatives
of “Preka College”, the problems with the manual system start from the moment the
students are registered in the school, a procedure that takes time and is not efficient
at all. The only person who had full rights over the system was the secretary of
the institution, this means the problem with transparency was identified. Requests
for data views, changes, copies, and everything else go to that employee, which
also creates unpleasant and unnecessary delays, which is pointed out not only by
the academic staff but also parents of students. Also, academic staff and students
needed a space where they could access additional learning information and
communicate more easily about academic progress, through grades or comments.
Design
Requirements specifications
With the explanation of the functionalities and requirements of the system in the
previous chapter, now the functionalities will be described not simply listed but
1. Login/Logout: Enables users to log into the system using their user email and
password; logout serves to exit the system.
2. Forgot password: If users happen to have forgotten their password, they are
allowed to retrieve their password via an email message.
3. Add/Edit/Delete: Users such as administrators or teachers will have the
opportunity to add, edit and delete data, within the level of access they have.
4. Download/Upload document: Students will be able to download study
materials placed on the system by their teachers. Also, through this function,
the student data recorded by the secretary can be easily uploaded.
5. Send message: Essential element for ease of communication, increased
collaboration, and reduced time, available for all user dashboards.
6. Print document: Some documents need the option to be printed for
transparency and two-sided correctness, for example, financial invoices.
Use Case diagrams are functional diagrams that describe the basic functions of
the system, showing what users can do and how the system can respond to their
actions. Each graphical element in the Use Case diagram describes one and only
one function through which users interact with the system, although users may
take several paths to interact with it.
The system does not allow the selection of the subject, without first selecting the
class. Then you can proceed with the display of grades.
Development Tools
Based on the literature and other studies that are not included in this paper,
programming languages, libraries, different frameworks, data management systems
or other elements related to the development of the system and its deployment
are endless and each with specific characteristics and attributes, resulting in none
being the best possible solution for every possible case. In the following parts, the
tools and the reasons why they were chosen to be used in the construction of the
Preka College system are specifically addressed.
The environment selected for the development of the Preka school system is
Visual Studio Code because it is open source, user-friendly, and has extensions
that significantly facilitate the work during coding. The main language selected
for the development of the proposed system is PHP. It is known as a server-side
scripting language that is used for many purposes, but that serves mostly for web
developments, making them dynamic and interactive. Being a web-based system,
in this paper PHP is incorporated with HTML, CSS, and JS. To make the system
easy to navigate and aesthetically attractive, this paper it was chosen to use the
CSS framework, Bootstrap. Having a time limit for the design and construction of
the concrete system has increased the need for the use of this framework, which
manages to help the development process of the front-end nature. In addition
to Bootstrap, another framework that has been used in this work is the PHP
framework, CodeIgniter. CodeIgniter provides “out of the box” libraries to connect
to the database and perform various operations such as sending emails, uploading
files, managing sessions, etc.
In addition to the tools that are needed for the development of the system, the
tools that serve for the creation of the database and their management should also
be mentioned. The first tool used is the Xampp platform, which helps a local host
or server to test the website before releasing it to the main server. It is a platform
that provides a convenient environment to test and verify the operation of projects
based on Apache, Perl, MySQL Database, and PHP through the host system itself.
Consequently, based on the fact that the work is done with PHP, it seems like the
After developing a system, the next thing that is done by the programmers is to
verify, validate and control the application, as well as to detect defects and errors
that need to be given more attention. This stage is part of the implementation stage
and is called testing. Testing is performed to ensure that the system meets business
requirements and technical procedures and to ensure that it functions perfectly.
Testing of the Kolegji Preka management system will be carried out at this stage
of development to detect unnecessary errors before it is presented as a finished
system to end users. In fact, the testing phase does not start and end with control
performed by the working group. The latter is based heavily on the feedback and
opinions that users create during the period they use the system. This helps the
team to continuously improve and update the system, always if this is part of the
agreement between the developer business and the requesting client. An example
would be testing whether anyone can become part of the system, or whether
previously imposed restrictions work. If a user tries to enter the system without
Conclusion
This work was carried out to document the work and processes of building
a Management System for the non-public High School, Kolegji Preka, which
submitted the request for the replacement of the current manual system used
by their academic staff, with an automated and easily accessible one. The work
has been divided into stages according to the phases of the systems development
life cycle, therefore it started with the planning of the work processes and ended
with the implementation phase. Initially, a detailed study of the existing literature
was carried out, comparisons were made between different information systems,
to conclude that this system will serve as an MIS and TPS at the same time. In
addition to this comparison, several others were made about system development
methodologies, where “Throwaway Prototyping Development Methodology” was
more efficient. After clarifying these details, the paper continues with the concrete
and practical side of the SDLC phases.
The first action during the planning phase consisted of communication with
the leaders of Preka College through a physical interview, intending to collect as
much data as possible related to the progress and continuity of daily life of the
current system. The interview is considered a “fact-finding” technique, which
serves to clarify the situation as much as possible and to avoid later problems if the
requirements and objectives are not set properly. During this phase, it was clarified
that the school’s resources will be used for the construction of the new system and
not for the improvement of the existing one.
Conducting the interview and collecting complete data opened the way to the
analysis phase, which consisted of studying the interview to list concrete, clear
and realistic objectives and requirements for the system. The result included
requirements related to building panels for different users, who should have
different levels of accessibility; having a way of logging into the system that
protects the data, but also allows different users to access the data that is part of
their responsibility, such as students checking their grades after different tests;
increasing transparency and speed of data collection or processing; facilitating
processes related to payments or obligations that different individuals have towards
the school; storing data quickly and managing it quickly and accurately. Also, the
References