Академический Документы
Профессиональный Документы
Культура Документы
Jordan T. Segundo
Seiji P. Soliweg
ABSTRACT
Information system in any organization is an essential
element. For this purpose, many organization spend budget to
buy a good system in order to have a reliable system to be
operated in their organization. These are Information Systems
(IS) used to generate, collect, organize, store, retrieve, and
disseminate information. Specific IS used to manage student
information is referred to as Student Information System (SIS).
This research proposed a SIS for Saint Pauls Academy High
School (SPAHS) to address its problems with regard to
managing student information which are in enormous amount of
paper, documents or records filed in folders and stored in filing
cabinets. Considering that information is a set or collection of
data, with the manual information system approach, generating
information suffers difficulties. After identifying the problem of
SPAHS, a system architecture of the proposed SIS was
established. The system architecture used a three tiered pattern
and Unified Modeling Language (UML) was used to present the
different views of the systems architecture. Functionalities
include tracking all the details of a student from the day one to
the end of the students stay in the school which can be used for
all reporting purpose, tracking of attendance, progress in the
subject, completed school years, project or any other assignment
details, final exam result and all these will be available through a
secure, online interface embedded in the schools website. It will
also have faculty details, batch execution details, students
details in all aspects, the various academic notifications to the
staff, students and parents updated by the administrator.
Different reports and queries can be generated based on vast
options related to students, batch, course, faculty, exams, school
years, and even for the entire school. Lastly, this design was then
evaluated using a questionnaire to measure usability.
KEYWORDS
Information system, Student Information System, UML
1. INTRODUCTION
According to Swartz (2007) almost all institutions depend
on data. Consequently, Pacio (2013) added, we are witnessing a
profound change in the way in which institutions perceive,
understand, and manage their information. There is now a
2. METHODS
The researchers have conducted a research with regard to
the company profile through an observation of the business
functions and processes in SPAHS followed by an interview
with the school principal and 2 faculty members. They chose
which business process problem to focus on. Lastly, they
identified/proposed a system that could help solve the chosen
problem and identified the systems requirements and risks.
After the identifying the problem and specifying the
requirements, the design of the proposed enterprise system was
established with the use of the different architectural styles and
patterns and UML diagramming tools namely use case, class,
sequence, package, and deployment diagrams. The knowledge
with regards these processes were from attended lectures and
background reading from related articles. First, they were
oriented about the different architectural styles and patterns then
they decided what architectural pattern will be the most suitable
for the proposed system. Second, they were oriented about the
different views of architecture and the UML diagrams used to
present each view. Before modelling the diagrams, the
researchers listed the actors, existing student information system
scenarios and the proposed student information system
scenarios. Modelling of the diagrams was done hierarchically.
The proposed systems scenarios was analyzed to come up with
the list of use cases. First, a use case diagram was modelled to
present the systems functionalities. After modelling the use case
diagram, any from class, sequence or package diagram may
follow. Next the researchers modelled the class diagram using
the same scenarios where the parts of speech were identified and
the words were grouped into nouns, verbs and adjectives. These
3.2.1
3.2.2
3. FINDINGS
3.1 Problems
The following are the problems encountered in St. Pauls
Academy High School that requires a design of an enterprise
system:
1. Not well-organized student records
2. Inaccurate student records
3. Time consuming access to student records
3.2
Systems Architecture
3.3 Evaluation
Below is a table of the evaluation result:
No.
Lloyd
Gina
Cherry
Escao
Balansi
Bacdayan
1
/
/
/
2
/
/
/
3
/
/
/
4
X
X
X
5
/
X
/
6
/
/
/
7
/
/
/
8
/
/
/
9
/
/
/
10
/
X
/
11
/
X
/
12
/
/
/
13
/
/
/
14
/
/
/
15
/
/
/
16
X
X
X
17
/
/
/
18
X
X
X
19
X
X
X
20
/
/
/
TOTAL 16
14
16
TOTAL
3
3
3
0
2
3
3
3
3
2
2
3
3
3
3
0
3
0
0
3
46
DISCUSSIONS
4.1 Problem
4.
Systems Architecture
Architectural Pattern
Class Diagram
Sequence Diagram
the user and clicks delete user button. The system then prompts
for confirmation and the administrator confirms deletion.
The generate report subsystem is used by the administrator who
enters a keyword in the search bar or he/she can query the
database. The database is searched and the system shows
result/s. The administrator clicks the printer icon to print the
report.
The keep students records subsystem is used to update students
records. Advisers check attendance and the system sends the
daily list of absentees to the Prefect of Disciplines who give
corresponding remarks. They also enter the summary of
disciplinary record of students in updating disciplinary records.
The teachers give syllabus and may include resources at the start
of school year and enters students grades every grading period.
Lastly, the cashier enters students statement of account. For
every, update in students record, the system calls the notify()
under the Notify subsystem.
The notify subsystem is run for every update in the students
records, notify() is called and a notification is generated and sent
to corresponding student and parent. The administrator may also
publish a notice by clicking the publish notice to call notify().
The system shows the editor pane where the announcement is
typed and necessary files may be attached. The administrator
chooses receiver/s and hits the send button to send the
notification to the corresponding user.
4.2.5
Package Diagram
Deployment Diagram
The web browser communicates with the clients. Here, the web
browser displays data, collects input from the user and posts it
back to the web server. The web server serves up data from the
web browser and passes these to the business logic tier and vice
versa. The application server provide its clients with access to
the business logic and where the data source layer is accessed.
Lastly, the data source tier is where information is organized by
the database server and stored/fetched from the database.
4.3 Evaluation
Three persons evaluated the architecture in terms of usability.
The checklist is composed of 20 questions. The results were
interpreted using mean as the central tendency by dividing the
total score by three. Out of 60, the design had 46 points in total
which resulted to an average of 15.33 points. The assessment
table shown in appendix c tells that the average score
corresponds to 55%-75% applicability rate which means that the
design is applicable with major revisions that need to be
addressed. This revisions were identified as:
RECOMMENDATIONS
7.
5. CONCLUSIONS
(FOR OBJ. 1)To solve St. Pauls Academy High Schools
problem of student records management, the proposed design of
Student Information System shall be implemented for students
and departments to access/ update information in a much
quicker turnaround making information well organized and
accurate for ready access by the administrative, academic and
accounting departments, and information requests faster to fulfill
core functional needs like student record keeping, registration,
grade reporting, student billing, academic advising, and alumni
relations.
(FOR OBJ. 2)A three tier pattern suits the design of the
proposed SIS because of data-related and process-related
groupings of its components. The modular design will enable
scalability and easier modification of the system or parts of the
system whenever needed, without affecting the system as a
whole.
(FOR OBJ. 3) The researchers have learned that in establishing a
good systems architecture, error-handling strategy must be
described and justified, reliability and performance needs should
be addressed, all security considerations should be addressed
and the architecture itself should show that it is designed to
accommodate likely changes. The researchers also learned that it
is important to evaluate the systems architecture before finally
implementing it to measure not just its usability but the other
REFERENCES