Esguerra, Carla A.

Flores, Jinky D.
Nitafan, Allyssa Jozel B.
Yanday, Charrie D.

BACKGROUND OF THE STUDY
Nowadays, the way many people interact with each other has changed because
of technology. First of all, absolute advantage is that technology makes the world
move faster. To support, speed of daily business interactions increasing all the
time. There are many ways in which how technology is changing educating from pre-
school to College, the education trend has now changed. Communications and delivery
of the education has become so advanced. Right from the primary school grades to the
height of graduate school, technology can be used as a powerful tool for education.
Teachers, and students should take advantage of this.
Grading System is a very important aspect of a schools operation and goals.
The student are graded to accurately compute the grades of the students using their
calculators, whether an ordinary of scientific type.
Grading System will help to improve to make faster and easier the manual
grading system in every school in many ways such as in computing and analyzing the
performance, talent and skills of students. It is the important record to keep even
for the longest time for the referral and credentials of the student to enter their
next level of attaining their goals. It is the tract record that recognizes of one
student, this maybe use for analyzing of your attitude and values.
According to(http://ursinus.abroadoffice.net/Grading.html), the U.S. Grading
System at the end of each semester, you will be given a grade for the quality and
quantity of your work in a given class. A students academic standing is determined
by the number of credits (classes) completed and his or her GPA. A students GPA is
calculated by multiplying the number of units (credits) attempted in each course by
the grade points earned per course. All grade point totals are added together. This
sum is divided by the total number of credits, creating a final mean value.

Mangatarem Institute was the old name of the school, they renamed it as
Mangatarem Catholic School that was founded in 1956.Mangatarem Catholic Schooloffers
programs in pre-school, elementary and secondary levels. The principal of the school
was Mrs. Rita Fernandez Austria and Sr. Natividad M. Mendoza the directress who led
the school.
Table 1 shows the number of students in Mangatarem Catholic School.
The list of the students enrolled in Mangatarem Catholic School:
Grade/Year
No. of Students
Grade 7 100
Grade 8 83
3
rd
year 145
4
th
year 110
All level were divided by two sections. The school has 20 employees, 3 are non-
teaching and there are 17 teachers who supervise the students. They have five
building in this institution to accommodate the employees and the students.They also
have 20 working computers, also they have room for the film showing, and they teach
some advance topic in college in order for them to ready the students for taking up
college.
We choose this system for widely used of technology in education. Until today
many school still using the old system type. If we create a computer-based grading
system, it will be more easy and reliable work for the teachers. Many teachers today
are still using the lesson plan. Because of many work of the teachers for the lesson
and for the teaching, it will be less stress for them if they will used computer-
based grading system.


STATEMENT OF THE PROBLEM
The study aims to make a computer-based grading database which
can help aid the problem regarding in recording, and reporting
student grades. Especially it seeks answer the following problems:
1. What are the existing processes in the Mangatarem Catholic School?
2. What are the features to include?
3. What is the acceptance level in term of CARTS?
a. completeness;
b. accuracy;
c. reliability;
d. timeliness and;
e. security?

SCOPE AND DELIMITATION
The proponents set the scope and limitation of the proposed
system to have a guide in developing the system.
The proposed system is computer-based. It can encode records
of the students for the first grading until fourth grading. And
also can encode the information of students. It can perform the
computation for the grades to first grading until fourth
grading. It can auto organize the arrangement of the student by
default in student numbers but it can also arrange by
alphabetical or grades. It can also print the record in the
database.

SIGNIFICANCE OF THE STUDY
The following entities are the beneficiaries of this study:
Mangatarem Catholic School. This will further help to make their
daily routine easier.
Teachers.The system will help the teachers more efficient. Also
this grading system make students data easily accessible in an
accurate manner. Using the system, the teachers now can focused
more in teaching and can also focused in managing programs in the
school.
Students. The system will help students to see their grades easily
and to be benefited of having safe and secured records in the long
run the system.
Proponents. The study has also helped the developers to acquire
knowledge regarding the operation of the school with the use of
gathered information about the facts of the process involved in
grading system. Implementation of the study will broaden the
knowledge of the developers on how to build, design and implement a
grading system.
Future proponents. This research study will serve as reference of
an associated study on grading system. They can get the things that
they needed from this study.

RESEARCH METHODOLOGY
This chapter presents the research methodology. It
consists of the specific discussions on the methods and
procedures that were used, the sources of data,
instrumentation and the data collection and the tools
for data analysis.
The proponents will use the descriptive library and
research method to gather information and gain more
knowledge about the proposed system. We also searched
some data and documentation for more related studies.
The internet, interviews and personal queries was also
considered in laying out the concepts and design of the
proposed system.

WATERFALL MODEL

Design
Requirements
Implementation
Verification
Maintenance

The Waterfall Model is a sequential software
development model in which development is seen as flowing
steadily downwards through the phases of requirements, design,
implement, verification and maintenance. It is signed that the
waterfall model in general can be suited to software projects
which and stable especially those projects with unchanging
requirements and where it is possible and likely that designers
will be able fully predict problem areas of the system and
produce a correct design before implementation is started.
Waterfall development isn't new -- it's been around
since 1970 -- but most proponents still only have a vague idea
of what it means. Essentially, it's a framework for software
development in which development proceeds sequentially through
a series of phases, starting with system requirements analysis
and leading up to product release and maintenance. Feedback
loops exist between each phase, so that as new information is
uncovered or problems are discovered, it is possible to "go
back" a phase and make appropriate modification. Progress
"flows" from one stage to the next, much like the waterfall
that gives the model its name.

The requirements are fully completed, one proceeds
to the design. In this state the software is designed
for a blueprint. The design should be a plan for
implementing the requirements given. Towards the late
stages of this implementation phase, separate software
components produced are combined to introduce new
functionality and reduced risk through the removal of
errors.
Being a very old model it is not recommended for use
on proprietary or customized systems due to its
inability to adapt to constantly changing requirements.
However, in the laze of eons software, the set of
requirements is first engineered and finalize before any
development process, there are already concrete
requirements specifications to work with.

A number of variants of this model exist, with each one
quoting slightly different labels for the various stages. In general,
however, the model may be considered as having five distinct phases,
described below:
Requirements Phases.
The waterfall model approach emphasizes a structured
progression between defined phases. Requirements are a set of functions
and constraints that the end user expects from the system. The
requirements are gathered from the assessment of the manual process of
Mangatarem Catholic School, and are analyzed for their validity and the
possibility of incorporating them. (McConell, 2006).
The proponents made unstructured interview and thorough
investigation by searching the history of the manual process, looking for
the procedure and collated the findings. These findings were verified
thru a survey questionnaire in the School of Mangatarem Catholic School,
students and all the employees. From this, the proponents will
identified all the requirements for the grading system that were used to
develop a design that served as a prototype model that solve the findings
of the proponents during the investigation.
From this, the proponents will identified all the requirements
for the grading system that were used to develop a design that served as
a prototype model that solve the findings of the proponents during the
investigation.

Design Phase.
This is the next stage after the analysis and requirement phase. In this
part, the physical and logical designs of the proposed system are built. The output
of this phase is reflected on the capability of the system. This phase took the
requirements identified in the first stage as the initial input. For each
requirement, a set of one or more design elements are produced as a result of
interviews, workshops and prototype efforts. The requirements must be reflect on the
design of the system (Laplante, 2009).
After the beneficiary has approved the specification of requirements the
proponents used use case to represent the group of elements like classes and
interfaces, entity relationship diagram to represent the structure data, database
instances to describe a complete database environment and lastly, the database
schema to describe the tables and views in a database together with the
relationships between them. Clearly the detailed design stage is the most demanding
in terms of resources and time.
Implementation Phase .
This is the stage where the proponents are divided the system according to
function. The coding of the program takes place in this phase as well as the
checking of the compatibility of the programs to different aspect such as software,
hardware and people-ware (Hay, 2011).
This is where the proponents used their skills in programming in certain
problems on the detailed manner, code generation, designing interfaces and features
of the system. Allow the proponents to assume an implementation of the system to the
company. Implementations of such specifications involved in modular designs are
those exact processes even to the proponents as constructing the design proponents
to assume an implementation of the system to the company. Implementations of such
specifications involved in modular designs are those exact processes even to the
proponents as constructing the design.

Verification Phase.
This stage is an activity which aimed to evaluate an
attribute or capability of a program or system and determining that it
meets its required results. Testing is more than just debugging. The
purpose of testing can be quality assurance, verification and validation,
or reliability estimation (William C., 2001).
This phase in waterfall model is where the designs were
translated into a machine readable form. This is where the proponents
must use their skills in programming in certain problems on the detailed
manner; code generation can be accomplished mechanistically.
Maintenance Phase .
This stage includes the implementation of the system. This
phase is the last phase to be implemented in the development process.
This stage can be implemented upon the approval of the client (Wideman,
2010).
In this phase, once the design has been tried and tested by
the testing team, the customers are given a demo version of the final
program. Now they must use the program and indicate whether they are
satisfied with the product or not. If they accept that the software is
satisfactory and as per their demands and requirements, the process is
completed. On the other hand, if he is dissatisfied with certain aspects
of the software, or feels that an integral component is missing, the
design team proceeds to solve this problem.
The deployment and maintenance of the system includes changes
and enhancements before the decommissioning or sunset of the system. As
key personnel charge positions in the organization new changes were
implemented, which were required system update (Martin, 2012).

SOURCE OF DATA
The main source of data in the study is the employee
records kept at the Mangatarem Catholic School. The data
being gathered in this project is classified as the
primary and secondary sources.
The proponents used structured interviews as primary
sources. An interview guide is used in studying the
system, through the help of Mrs. Rita Fernandez Austria
the principal of Mangatarem Catholic School and the
teachers.The proponents used surveys and internet as a
secondary sources.

DATA GATHERING
The proponents used the following to gather
related information in developing the Grading System of
the Mangatarem Catholic School.
Questionnaire. A set of objective questions regarding
the proposed systems and problems, it tries to solve
what was presented to respondents. The results of these
are carefully evaluated so that this study would mean
very much significant.
The Internet. A huge basket of information available at
the tip of our fingers. With connections of many people
compiled knowledge and ideas that are made free for use,
we were able to research related topics of the same
concepts and ideas.
SCOPE DATA ANALYSIS
This section gives an explicit presentation of tools used by the proponents
for data analysis.
Use Case.
The proponents used this tool to show all system activities that have
significance to the users. A Use Case describes a sequence of actions that provide
something of measurable value to an actor and is drawn as a horizontal ellipse. It
could provide an overview of the usage requirements for a system.
It is used by the proponents to determine the behavioral the requirements
and the missions and goals for the system.
Entity-Relationship Diagram (ERD).
ERD refer to the tool that the proponents have used in data analysis of
the project. The proponents used this as a tool because to clearly visualize a
relational database. An ERD is a special graphic that illustrates the
interrelationship between entities in a database. Boxes are commonly used to
represent entities. Diamonds are normally used to represent relationships and ovals
are used to represent attributes.
Database Schema.
The developers used this tool to layout the structure of the database and
the relationships that exist between elements of the database.A database schema is a
collection of meta-data that describes the relations in a database. A schema can be
simply described as the layout of a database of the blueprint that outlines the
way data is organized into tables. Schema are normally described using Structured
Query Language as a series of CREATE statements that may be used to replicate the
schema in a new database. (see Appendix D).
The developer had utilized a database schema in order to fully illustrate
the structure of the developed systems database.


Flowchart.
The proponents will be used flowhart to
represent The sequence of the contents of the
process from the start to the end of process
points. It was also be used by the proponent to
organize the topics strategies, treatments and
option will work out the details flowchart as a
working map of the project study. Flowchart will
be used to show existing processes.
WEIGHTED MEAN.
An average calculated by taking into
account not only the frequencies of the values of
a variable but also some other factor such as
their variance. The weighted average of observed
data is the result of dividing the sum of the
products of each observed value, the number of
times it occurs, and this other factor by the
total number of observations.