1

LYCEUM OF THE PHILIPPINES UNIVERSITY CAVITE

Chapter 1

Introduction



1.1 Background of the Study
Lyceum Philippine University is Located at General Trias Cavite. There
are five colleges in this school, the head faculty which is also the professor.
We all know that the number of research project, Scheduling a
Presentation, Grading the research project and management, cannot be controlled
and that keeping of records is one of the main problems in a school. Just like the
Lyceum Philippines University COECSA-Faculty whos experiencing the same
kind scenario where the number of research project and grades is keep on
increasing so they cannot handle their records efficiently.
The researchers decided to make an Online Scheduling, Grading and
Management System for DCS Research Presentation to accommodate the work
processes problems of the specific college in Lyceum Philippine University. The
Online Scheduling, Grading and Management System for DCS Research
Presentation, will help the college to minimize time doing the work processes and
to hasten the production of reports accurately.


Online Scheduling, Grading and Management System for DCS Research
Presentation is the structure of processes and procedures used to ensure that an
2

organization can fulfill tasks required to achieve its objectives. Online
Scheduling, Grading and Management System for DCS Research Presentation
generally includes detailed information on establishing Scheduling, Grading and
Management. The proposed system will be in HTML as main markup language,
PHP as server-side scripting language, Css for the look and formatting,
JavaScript, JQuery, AJAX for client-side scripting language which is used
widely in our generation.
The purpose of creating this system is to minimize the error, scheduling
every research project created, grading every project and manage the research
project and because of that the user will have a more time in doing another task.
The Administrator can easily login by using there username and password. The
Administrator can easily schedule if the group is not registered or scheduled and
they can easily grade and manage the research project. Administrator can easily
notice that this group in capstone is not scheduled. The most important part is the
report the system will automatically generate reports and grade the research
project and have a result within the day of the presentation.




1.2 Background of the Company
Lyceum Philippine University Cavite. is established by the year 2008 in
General Trias, Cavite, Philippines 14.2908N 120.9156E The Head Faculty
3

needs to schedule the group in capstone, Grade the research project of every
group and manage it. The all in all processes inside the school within college is
handled by the head faculty.
1.2.1 Mission
Lyceum of the Philippines University, espousing the ideals
of Jose P. Laurel is committed to the following

1. Provide equitable access to learning through relevant,
innovative, industry-based and environment-conscious
programs and services in the context of nationalism and
internationalism. - INSTRUCTION and QUALITY
SERVICES

2. Provide necessary knowledge and skills to meet entrepreneurial
development and the managerial requirements of the industry. -
INSTRUCTION

3. Establish local and international linkages that will be the
source of learning and growth of the members of the academic
community. - INSTRUCTION and INSTITUTIONAL
DEVELOPMENT

4. Advance and preserve knowledge by undertaking research and
disseminating and utilizing the results. - RESEARCH

5. Support a sustainable community extension program and be a
catalyst for social transformation and custodian of Filipino
culture and heritage. - COMMUNITY EXTENSION

4


6. Build a community of God-centered, nationalistic,
environment-conscious and globally-competitive professionals
with wholesome values and attitudes. -PROFESSIONALISM
and VALUES

1.2.2 Vision
Lyceum of the Philippines University envisions itself as a leading
university in the Asia-Pacific region, dedicated to the development of the
integral individual who constantly seeks the truth and acts with fortitude in
service to God and country.







1.3 Statement of the Problem
The college has a lot of paper works to do since scheduling, grading, and
management of records is part of their processes.
The head of the faculty, Jerian Peren, is assigned to give permission to the
secretary and faculty member to give schedule, manage the research project and
the faculty member who assign to grade the project who are taking capstone
5

project. She also handles all the information, updates of the information about the
system, add, delete and edit every schedule. About. Gathering information from
head faculty is quite easy for her, but keeping records scheduling grading takes
big responsibility. The head faculty let the secretary give schedule to group who
are taking capstone project by the use of writing their information in a record
book then encodes it in Microsoft Office Excel for reports. The information
needed includes (1) first name, (2) middle name, (3) surname,(4) section,(5) title
of the system. Though the details of group getting a schedule are quite hard
because of the time and date of the specific faculty member, the grading of their
project are quite hard to handle. One of the problems in this process is tampering
of the group who are scheduled.
Online Scheduling, Grading and Management System for DCS Research
Presentation is designed to make the processes and procedures easy and time
consumable. It has three users; the administrator or head faculty, panelist or the
professor and the adviser. The data is secured by computer by the use of log in.
The administrator can also manage all the research presentations by adding,
editing and deleting records of all researches, as well the research presentations,
advisers, panelists and the research presenters. The administrator can also approve
and disapprove a research project.

The Panelist can grade the research presenters through the computerized
grading system provided by the system, the system can also provide manual
grading sheet if the panelist cant use the computerized grading sheet. Panelist can
also view all of their schedule for a research presentations.
6


The Advisers can manage all of their handled sections with research
projects. They can add, edit and remove a research presenters with their research
titles and information. Advisers can also view all the research presentations
schedule of their handled sections.

Furthermore, the application needs an internet connection and browser to
use the system. All information from the system are stored and secured in a
database, which is located on the web server. The application also has a capability
to provide summary reports and information about the research presentation,
panelist, professors, advisers, presenters, grades and schedules.

The Internet connection is also a constraint for the application. Since the
application fetches data from the database over the Internet, it is crucial that there
is an Internet connection for the application to function.

The Internet browser is also a constraint for the application. Since the
application uses the latest functions and tools for designing and coding. The
internet browser must be in the latest version. Lower version of a browser can
cause unexpected results and will not display a result as expected to be.


1.4 Objective of the study
7

1.4.1 General Objectives
The main goal of this document is to give a detailed description of the
requirements for the Online Scheduling, Grading and Management System for
DCS Research Presentation software. It will illustrate the purpose and complete
declaration for the development of system. It will also explain system constraints,
interface and interactions with other external applications. This document is
primarily intended to be proposed to a customer for its approval and a reference
for developing the first version of the system for the development team.



1.4.2 Specific Objectives
The specific objectives are the following:
1.4.2.1 To provide well organized data in Online Scheduling, Grading
and Management System for DCS Research Presentation
1.4.2.2 To reduce paper works.
1.4.2.3 To fasten the work processes in Online Scheduling, Grading
and Management System for DCS Research Presentation
1.4.2.4 For faster and accurate release of reports.
1.4.2.5 For faster and accurate of grading the research project.
1.4.2.6 For faster scheduling of the presentation and to avoid conflict
to the schedule.
8

1.4.2.7 Provide security of data in Online Scheduling, Grading and
Management System for DCS Research Presentation
1.4.2.8 To easily monitor Online Scheduling, Grading and
Management System for DCS Research Presentation.

1.5 Significance of the Study
This study will help to reduce the time in Scheduling, grading,
management and to increase the effectiveness of Online Scheduling, Grading and
Management System for DCS Research Presentation. The Online Scheduling,
Grading and Management System for DCS Research Presentation aims to benefit
the school and college in their traditional scheduling and grading system. The
system desire to benefit the following:
1.5.1 The college
It will save time, because of manage and informative system can
do. The main recipient of the proposed system is the school and college
because it will help the COECSA faculty in minimizing errors that occurs
in the traditional system. This will also help them to become effective in
the reports that they are making.
1.5.2 The Administrator
The Administrator can schedule all the research presentations of all
sections with research projects, the scheduling has a decision support
capability to provide much easier scheduling by providing all panelist,
time and room without any conflicts. The administrator can view all the
9

grades of all the research presenters using the computerized grading
system, an automated grading system which the panelist can grade the
presenters using the computerized grading sheet, the grades are
automatically computed every time the user inputs a grade and
automatically compute its average grade based from the panelists total
grade. The administrator can also manage all the research presentations by
adding, editing and deleting records of all researches, as well the research
presentations, advisers, panelists and the research presenters. The
administrator can also approve and disapprove a research project.

1.5.3 The Panelist
The proposed Online Scheduling, Grading and Management
System for DCS Research Presentation will lessen the time of grading of
presenter and post the result of the there research. It will also help the
project leader because they will not be fill up the form again,
The Panelist can grade the research presenters through the
computerized grading system provided by the system, the system can also
provide manual grading sheet if the panelist cant use the computerized
grading sheet. Panelist can also view all of their schedule for a research
presentations.




10

1.5.4 The Adviser or faculty
The Advisers can manage all of their handled sections with
research projects. They can add, edit and remove a research presenters
with their research titles and information. Advisers can also view all the
research presentations schedule of their handled sections.
This study can help them by using this research as a reference for
their own.

1.6 Scope and Delimitation of the study
The Online Scheduling, Grading and Management System for DCS
Research Presentations is a web-based application which will provide easier
scheduling, grading and management of all the DCS research presentations.

The Administrator can schedule all the research presentations of all
sections with research projects, the scheduling has a decision support capability to
provide much easier scheduling by providing all panelist, time and room without
any conflicts. The administrator can view all the grades of all the research
presenters using the computerized grading system, an automated grading system
which the panelist can grade the presenters using the computerized grading sheet,
the grades are automatically computed every time the user inputs a grade and
automatically compute its average grade based from the panelists total grade. The
administrator can also manage all the research presentations by adding, editing
and deleting records of all researches, as well the research presentations, advisers,
11

panelists and the research presenters. The administrator can also approve and
disapprove a research project.

The Panelist can grade the research presenters through the computerized
grading system provided by the system, the system can also provide manual
grading sheet if the panelist cant use the computerized grading sheet. Panelist can
also view all of their schedule for a research presentations.

The Advisers can manage all of their handled sections with research
projects. They can add, edit and remove a research presenters with their research
titles and information. Advisers can also view all the research presentations
schedule of their handled sections.

Furthermore, the application needs an internet connection and browser to
use the system. All information from the system are stored and secured in a
database, which is located on the web server. The application also has a capability
to provide summary reports and information about the research presentation,
panelist, professors, advisers, presenters, grades and schedules.





12


1.7 Methodology of the Study
Developing Online Scheduling, Grading and Management System is quite
difficult to do because it will take time to finish accurately. It needs wide
variation of planning and analyzing on how the process will be minimized. Thus,
there is one useful tool that helps in making the system, the System Development
Life Cycle (SDLC). It is a process of creating or altering information systems, and
the models and methodologies that people use to develop these systems.
The Waterfall model is one example of the SLDC that is a Sequential
design process which includes Feasibility, Requirements Gathering, System
Design, Testing, and Implementation and Maintenance. It is used by many System
analyst because when a researcher or a system analyst commit an error to the
system he/she can go back easily to the previous step unlike other model that
requires to go back from the start.

1.7.1 System Planning
The first stage of SDLC model. This phase is basically the brainstorming
phase and often consists of sub-stages like Feasibility Analysis to check how
much of the idea can be put into action. It is the practice of collecting the
requirements of a system from users, customers and other stakeholders.
If any particular software needs to be modified, the underlying problem(s)
of that software is sorted out along with finding ways to solve it. If brand new
software is going to be developed, then every minute requirement regarding that
13

software is looked in to. This implies that this stage involves maximum research
and inputs from both the company that is developing the software and the client.
In this stage, the researchers set a meeting to plan what system is possible
to be created so the researchers look for a client to create system software. After
looking for a client, the researchers proposed a system that can monitor the Online
Scheduling, Grading and Management System of the administrator or the head of
faculty of the COECSA College and automatically generate reports in Online
Scheduling, Grading and Management System. The researchers prove that this is
feasible because of the bunch of records in the cabinet, less error and the most
important the reports. The requirements of the system in a user he/she must
computer literate.

1.7.2 System Analysis
This is the second phase of SDLC where the entire system is defined in
detail. In fact, it this stage wherein a detailed blueprint of various processes of the
software is developed. If needed the system is divided into smaller parts to make
it easier more manageable for the developers, designers, testers, project managers
and other professionals who are going to work on the software in the latter stages.
This stage is analysis stage; the researchers analyze the process of the COECSA-
College. So First, the adviser, panelist/faculty and head of faculty who want to
schedule, grade and manage the research project must register and the head of
faculty register the faculty according to their position in college. If the adviser,
panelist/faculty is already registered he/she schedule, grade and manage the
14

research project, in case the account of the adviser, panelist/faculty and head of
faculty is expire he/she should go to Administrator to request update or register or
reactivate the account and. After all of this the system can generate reports
efficiently.

1.7.3 System Design
In this phase, the physical system is designed with the help of the logical
design prepared by system analysts. The analysts and designers work together and
use certain tools and software to create the overall system design, including the
probable output.
The researchers used a simple yet good looking user friendly interface for
the proposed system to be used easily and effectively. The researchers used a
metro style design for the proposed system. This style looks like windows 8
interface. Metro style is a minimalistic and really popular design trend created by
Microsoft. It is also characterized by a flat look and feel, no levels and shadows.
As the name implies, in this stage the software is coded with precision. A
team of programmers are assigned by the company to work on the software. More
often than not, the work is sub-divided under a sub-phase called Task Allocation,
where each developer is assigned a part of the work depending on his or her skill
set(s). This helps complete the coding efficiently.

1.7.6 System Implementation
15

This is the final stage of system development life cycle. In this stage, if the
software is run on various systems by users, or if it runs smoothly on systems
without any flaw, then it is considered ready to be launched.
In Coding stage, the researchers has assigned a programmer in the team
and uses HTML, CSS, PHP, JavaScript, JQuery, and AJAX. The programmer
codes according to the system of the gym and how the system will easily manage.
In implementation stage the researchers need to sure that the proposed
system will work perfectly and have a support to the system, in case of the system
will have a bug.

1.7.5 System Operation & Support
When the software is ready, it is sent to the testing department where
Quality Analysts test it thoroughly for different errors by forming various test
cases. They either test the software manually or using automated testing tools and
ensure that each and every component of the software works fine. Once the QA
makes sure that the software is error-free, it goes to the next stage, which is
Implementation. Transactions and these errors are needed to be solved so this is
the step where we solve those problems.
This is the stage where the system should be done and ready to use. This is
where the researchers will test the system if it already meets the requirements
needed by the administrator or the head faculty. This will also help the researchers
to find out errors that will have to fix before implementing it o the user.
1.7.7 To conclude
16

Now that the basic details of software development life-cycle are
explained in the previous pages, it will help other researchers to develop software
with outmost perfection in the near future. For more details, other researchers can
look up various SDLC models and find the one that will suit to their software and
put it into practice.

















Planning

System Analysis

System Design

Implementation

17









Figure No. 1.1 System Development Life Cycle
Chapter 2
Conceptual Framework
2.1 Review of Related Literature
2.1.1 Foreign Literature
2.1.1.1 Bootstrap
Bootstrap is a free collection of tools for
creating websites and webapplications. It contains HTML and CSS-based
design templates for typography, forms, buttons, navigation and other
interface components, as well as optional JavaScript extensions. In June
2014 it was the No.1 project on GitHub with 69,000+ stars and 25,000+
forks, with a user base including MSNBC and NASA.
(http://en.wikipedia.org/)
18

The system used bootstrap to lessen time in creating a website and
have a simple but beautiful design in the system we created.
2.1.1.2 ActiveX Control
It is a software framework created by Microsoft that adapts its
earlier Component Object Model (COM) and Object Linking and
Embedding (OLE) technologies for content downloaded from a network,
particularly in the context of the World Wide Web. It was introduced in
1996 and is commonly used in its Windows operating system. In principle
it is not dependent on Microsoft Windows, but in practice, most ActiveX
controls require either Microsoft Windows or a Windows emulator. Most
also require the client to be running on Intel x86 hardware, because they
contain compiled code.
Many Microsoft Windows applications including many of those
from Microsoft itself, such as Internet Explorer, Microsoft Office,
Microsoft Visual Studio, and Windows Media Player use ActiveX
controls to build their feature-set and also encapsulate their own
functionality as ActiveX controls which can then be embedded into other
applications. Internet Explorer also allows the embedding of ActiveX
controls in web pages.
However, ActiveX will not work on all internet platforms, so using
ActiveX controls to implement essential functionality of a web page
restricts its usefulness.
(www.wikipedia.org)
19

ActiveX Control is Somehow Similar to our system because we
used ActiveX Control in it.
2.1.1.3 MySQL
MySQL can be used for a variety of applications, but is most
commonly found on Web servers. A website that uses MySQL may
include Web pages that access information from a database. These pages
are often referred to as "dynamic," meaning the content of each page is
generated from a database as the page loads. Websites that use dynamic
Web pages are often referred to as database-driven websites.
Many database-driven websites that use MySQL also use a
Web scripting language like PHP to access information from the database.
MySQL commands can be incorporated into the PHP code, allowing part
or all of a Web page to be generated from database information. Because
both MySQL and PHP are both open source (meaning they are free to
download and use), the PHP/MySQL combination has become a popular
choice for database-driven websites.
(www.techterms.com)
Relationship of MySQL to our System is that we use MySQL
language for our database in the system.

2.1.1.4 HTML
HTML or HyperText Markup Language is the standard markup
language used to create web pages.
20

HTML is written in the form of HTML elements consisting
of tags enclosed in angle brackets (like <html>). HTML tags most
commonly come in pairs like <h1> and </h1>, although some tags
represent empty elements and so are unpaired, for example <img>. The
first tag in a pair is the start tag, and the second tag is the end tag (they are
also called opening tags and closing tags).
A web browser can read HTML files and compose them into
visible or audible web pages. The browser does not display the HTML
tags, but uses them to interpret the content of the page. HTML describes
the structure of a website semantically along with cues for presentation,
making it a markup language rather than a programming language.
HTML elements form the building blocks of all websites. HTML
allows images and objects to be embedded and can be used to create
interactive. It provides a means to create structured documents by
denoting structural semantics for text such as headings, paragraphs,
lists, links, quotes and other items. It can embed scripts written in
languages such as JavaScript which affect the behavior of HTML web
pages.
Web browsers can also refer to Cascading Style Sheets (CSS) to
define the look and layout of text and other material. The W3C, maintainer
of both the HTML and the CSS standards, encourages the use of CSS over
explicit presentational HTML. (http://en.wikipedia.org/)


21





2.1.1.5 CSS
Cascading Style Sheets (CSS) is a style sheet language used for
describing the look and formatting of a document written in a markup
language. While most often used to style web pages and user interfaces
written in HTML and XHTML, the language can be applied to any kind of
XML document, including plain XML, SVG and XUL. CSS is a
cornerstone specification of the web and almost all web pages use CSS
style sheets to describe their presentation.
CSS is designed primarily to enable the separation of document
content from document presentation, including elements such as the
layout, colors, and fonts. This separation can improve content
accessibility, provide more flexibility and control in the specification of
presentation characteristics, enable multiple pages to share formatting, and
reduce complexity and repetition in the structural content (such as by
allowing for table less web design). It obviates those portions of markup
that would specify presentation by instead providing that information in a
separate file. For each relevant HTML element (identified by tags), it
provides a list of formatting instructions. For example, it might say (in
22

CSS syntax), "All heading 1 elements should be bold." Therefore, no
formatting markup such as bold tags (<b></b>)is needed within the
content; what is needed is simply semantic markup saying, "this text is a
level 1 heading."
CSS can also allow the same markup page to be presented in
different styles for different rendering methods, such as on-screen, in
print, by voice (when read out by a speech-based browser or screen
reader) and on Braille-based, tactile devices. It can also be used to allow
the web page to display differently depending on the screen size or device
on which it is being viewed. While the author of a document typically
links that document to a CSS file, readers can use a different style sheet,
perhaps one on their own computer, to override the one the author has
specified. However if the author or the reader did not link the document to
a specific style sheet the default style of the browser will be applied.
CSS specifies a priority scheme to determine which style rules
apply if more than one rule matches against a particular element. In this
so-called cascade, priorities or weights are calculated and assigned to
rules, so that the results are predictable.
The CSS specifications are maintained by the World Wide Web
Consortium (W3C). Internet media type (MIME type) text/css is registered
for use with CSS by RFC 2318 (March 1998), and they also operate a free
CSS validation service.
23


2.1.2 Local Literature
2.1.2.1 A Proposed Comprehensive Grading System to Predict
Outcome for Surgical Management of Intracranial Aneurysms.
By conducting a review of clinical outcomes for patients with
aneurysms treated using current microneurosurgical techniques and
intensive care unit management, we determined that grading systems
based only on the clinical condition of the patient failed to produce a
significant stratification of outcome between individual grades of patients.
We hypothesized that outcome prediction for patients surgically treated
for intracranial aneurysms could be improved by including factors other
than clinical condition that were also strongly associated with outcome.
(journals.lww.com)
2.1.2.2 Filters in license management system
A distributed computer system employs a license management
system to account for software product usage. A management policy
having a variety of alternative styles and contexts is provided. Each
licensed product upon start-up makes a call to a license server to check on
whether usage is permitted, and the license server checks a database of the
licenses, called product use authorizations, that it administers. If the
particular use requested is permitted, a grant is returned to the requesting
user node. The product use authorization is structured to define a license
management policy allowing a variety of license alternatives by values
24

called "style", "context", "duration" and "usage requirements
determination method". The license administration may be delegated by
the license server to a subsection of the organization, by creating another
license management facility duplicating the main facility. The license
server must receive a license document (a product use authorization) from
an issuer of licenses, where a license document generator is provided. A
mechanism is provided for one user node to make a call to use a software
product located on another user node; this is referred to as a "calling card",
by which a user node obtains permission to make a procedure call to use a
program on another node. A management interface allows a license
manager at a server to modify the license documents in the database
maintained by the server, within the restraints imposed by the license, to
make delegations, assignments, etc. The license documents are maintained
in a standard format referred to as a license document interchange format
so the management system is portable and can be used by all adhering
software vendors. A feature of the database management is the use of a
filter function.
(www.google.com)


2.2 Review of Related Studies
2.2.1 Foreign Related Studies
25

2.2.1.1 License document interchange format for license
management system
A distributed computer system employs a license management
system to account for software product usage. A management policy
having a variety of alternative styles and contexts is provided. Each
licensed product upon start-up makes a call to a license server to check on
whether usage is permitted, and the license server checks a database of the
licenses, called product use authorizations, that it administers. If the
particular use requested is permitted, a grant is returned to the requesting
user node. The product use authorization is structured to define a license
management policy allowing a variety of license alternatives by values
called "style", "context", "duration" and "usage requirements
determination method". The license administration may be delegated by
the license server to a subsection of the organization, by creating another
license management facility duplicating the main facility. The license
server must receive a license document (a product use authorization) from
an issuer of licenses, where a license document generator is provided. A
mechanism is provided for one user node to make a call to use a software
product located on another user node; this is referred to as a "calling card",
by which a user node obtains permission to make a procedure call to use a
program on another node. A management interface allows a license
manager at a server to modify the license documents in the database
maintained by the server, within the restraints imposed by the license, to
26

make delegations, assignments, etc. The license documents are maintained
in a standard format referred to as a license document interchange format
so the management system is portable and can be used by all adhering
software vendors. A feature of the database management is the use of a
filter function.
(http://www.google.com)
Looking at the License document interchange format for license
management system and in our system, their similarity is they both
provide a reliable, secure, and efficient method of Managing the records.
And they both produce reports. The difference between them is that
License document interchange format for license management system
involves License document interchange format for license.
2.2.1.2 Managing quality-of-control in network-based control systems
by controller and message scheduling co-design system
In network-based control systems (NCSs), plant sensor-controller-
actuator nodes in closed-loop operation drive principal network traffic.
The quality-of-control (QoC) in an NCS, i.e., the performance delivered
by each closed-loop operation, depends not only on the controller design
but also on the message scheduling strategy. In this paper, we show that
the co-design of adaptive controllers and feedback scheduling policies
allows for the optimization of the overall QoC. First, we discuss the
limitations of standard discrete-time control models for controllers of
control loops that are closed over communication networks. Afterwards,
27

we describe an approach to adaptive controllers for NCS that: 1)
overcomes some of the previous restrictions by online adapting the control
decisions according to the dynamics of both the application and executing
platform and 2) offers capabilities for dynamic management of QoC
through message scheduling.
(ieeexplore.ieee.org)

About Managing quality-of-control in network-based control
systems by controller and message scheduling co-design, visitor
monitoring and access control system and our system, they almost have
the same operations. Because they also use the process of scheduling to
analyse a particular security, the only difference is that the Managing
quality-of-control in network-based cognition system that efficiently
capabilities for dynamic management.


2.2.1.3 Customer relationship management in higher education: Using
information systems to improve the student-school relationship
Purpose The purpose of this paper is to explore customer
relationship management (CRM) in a higher education setting.
Design/methodology/approach The development and
implementation of a CRM project in a state community college was
28

examined as were the benefits realized by implementing CRM. As
colleges increasingly embrace distance learning and e-business, CRM will
become stronger and more pervasive. Viewing students as customers
provides a competitive advantage for higher education and enhances a
college's ability to attract, retain and serve its customers. Semi-structured
interviews were conducted with individuals involved with the planning,
development and implementation of a statewide CIS system. Student
support personnel were additionally interviewed.
Findings The benefits of implementing CRM in a college setting
include a student-centric focus, improved customer data and process
management, increased student loyalty, retention and satisfaction with the
college's programs and services.
Research limitations/implications The entire community college
system has not implemented the project. Rather, only the phase one
colleges have implemented at this juncture.
Originality/value Viewing students as customers provides a
competitive advantage and enhances a college's ability to attract, retain
and serve its customers. As colleges increasingly embrace distance
learning and e-business, CRM will become more pervasive.

29

With Customer relationship management in higher education:
Using information systems to improve the student-school relationship,
they both computer software that allows users easy and efficient control of
the file and manage it. But for Customer relationship management in
higher education: Using information systems to improve the student-
school relationship, they focus in their Students unlikely in our system; we
focus in the Research Project of the students in the School. And both
systems save time by using automated management.



2.2.1.4 JC Online scheduling system
Online scheduling systems comprise a scheduling module having
an electronic calendar showing a plurality of time slots. The scheduling
modules have executable instructions that transmit the electronic calendar
to and receive scheduling data from one or more buyer and seller
interfaces in order to facilitate the scheduling of a consultation between a
buyer and a seller. The online scheduling systems also comprise a
feedback module in communication with the scheduling module. The
feedback module has executable instructions configured to receive
feedback data from a buyer interface following a scheduled consultation.
30

The similarity about this system and in our system, they both have
a database. They can organize schedule, add, edit and delete categories
from a drop-down pick list. They can also launch Web sites in the default
browser and other features including logging supports, search supports,
custom backgrounds and automatic database maintenance. The only
difference about these two systems is that the JC Software Development
includes ID and personal notes.


2.2.1.5 The Wisconsin Age-related Maculopathy Grading System
A new system for grading age-related maculopathy is described
and measures of reliability are reported. A number of characteristics of
age-related maculopathy are graded in a semiquantitative fashion from
stereoscopic 30 color fundus photographs, using a grid to define
subfields, standard circles printed on plastic to assess size and area, and a
specially designed lightbox to allow better discrimination of subtle drusen.
The degree of exact agreement achieved between two trained graders
across a variety of lesions ranged from 67.1% for drusen size to 99.6% for
geographic atrophy. Kappa scores ranged from 0.55 (for drusen
confluence) to 0.95 for geographic atrophy. This system will be useful in
epidemiologic studies and clinical trials.
The Wisconsin Age-related Maculopathy Grading System also
Grade but their using The Wisconsin Age-related Maculopathy Grading
31

System which grading age-related maculopathy is described and measures
of reliability are reported. Both systems have far beyond simple time of
arrival and/or departure. Example for Wisconsin Age-related Maculopathy
Grading System, they will know if a patient have findings and, in the
proposed system the grades of the students will automatically computed.

2.2.2 Local Related Studies
2.2.2.1 Online E-Class Record of Holy Child Jesus Montessori
The online grading system was developed to replace the
existing manual grading system of holy child Jesus Montessori for
the purpose of computing students grades faster than before, and
more accurate in addition to help the members of the faculty ease if
not lessen their workloads. The study pertains of the processes
involved in the institution, and how the proposed system may help
make the tasks easier for the involved users. Necessary data were
collected to make the study possible.


2.2.2.2 Student Affais Office Services Record Management
System of Lyceum of the Philippines University of Cavite
The study entitled Student Affairs Office Sevices Record
Management System for Lyceum of the Philippines Uniersity is
was designed to improve the process of keeping and monitoring
32

the records of the student indifferent services of the StudentAffairs
Office. The services of the Student Affairs Office are student
violation, locker rental, lost and found and monitoring sanction.
The system was developed to convert manual process of the SAO
to computerize process. This system can also lessen the use of
papers and can be able to save time in recording student
information. Waterfall Methodology was used ti develop the
system because it is the most applicable methodology in the
studies. The researcher conducted the system testing with five(5)
participants which consists of (3) IT experts and (2) System
Administrators with the grand mean of 3.84 and an interpretation
of acceptable. The system evaluation was conducted with fifteen
(15) respondent consisting of (10) IT experts an (5) System
Administrators. The develop system got a 4:15 as the average
mean and the average standard deviation of 0.27 with an overall
interpretation of acceptable

.2.2.3 Online Medical Specialization Respository with Online
Navigation.
Focuses primarily in rendering convenient access to
different possible medical services that the health unit can offer.
Our society is in great need of quality services from us most
vulnerable field
33

It is capable of providing information concerning, list and
location of health units in the province of cavite, repository of
basic information of medical practitioners, list of prescriptions for
illness, medical services for animals are not covered in the study as
well as services for mental health units in the Province of Cavite.
OMRON is made to create a data repository for accessibility and
efficiency of information of medical practitioners including their
locations to offer reliable information for its accurate specialization
of medical practioners including their locations, to offer reliable
information for its accurate specialization of medical practitioners
their schedules and locations for the benefits of their customers and
to maintain a secure and balance relationship between the doctors
and patients, in terms of exchange of information.


2.2.2. LPU Faculty Attendance Management System with
Implementation of Biometric Device Fingerprint Scanner
The study entitled LPU Faculty Attendance Management
System with Implementation of Biometric Device Fingerprint
Scanner is a WLAN basic system design for the house office and
professors of LPU-Cavite and is exclusively for the premises of
LPU only. The system is designed to improve the process of
monitoring, organizing and assigning the attendance of the
34

professors. The system will prevent forging of information because
a biometric fingerprint scanner will be used for this study. The
research used Prototyping as the method for the development of
the system. After the research had conducted the test results to 15
different respondents that composed of alpha and beta testers. Out
of 241 criteria, 239 of them passed and 2 of them are for revision.
The said modules were debugged and improved to make sure that
the system will meet its objectives. The percentages are interpreted
as 98.88 for the remark passed and 1.12% for the remark of for
revision. The overall general average and standard deviation of all
the systems level of acceptability get 4.46 as the average mean
and 0.83 as the average standard deviation with an average remark
of Strongly Acceptable. The recommendations the were given by
the evaluators who graded the deliverables made by the evaluators
who graded the deliverables made by the research are the
following, Export of faculty Loads, Revise Filtering Method,
Revised Date filtering, Change the word Course into Program.
Revised the CBA of the proposed system. Change the graph to
college graph and include the reports that are submitted t different
departments.
2.3 Synthesis
The related literature and studies is based on other researched
studies of the past documentations. The proponents used the principles of
35

different studies and other application to develop the proposed system; the
ideas from different theses, books, sites, discussion and etc. helps to
improve details and processes in the developed system.
The formers are mainly similar with the proposed system in terms
of functionalities. Both offer the integrated components and modules of an
access control system and some scheduling, grading and management. The
greatest difference is there system not used web based application unlike
other related studies. The scheduling, grading and management that the
proponents used is the way to complete transaction to be processed
quickly.
The proposed system also offered this important function wherein
users of the system have been allotted an individual username and
password for the protection of files for unauthorized users. In this kind of
system, security is highly monitored because there is information and
grades involved, this eliminate anomalies that might occur.


Chapter 3
Theoretical Background

Theoretical framework is a compilation of interrelated concepts, such as a
statement of assumptions, operational definitions, Definition of terms, definition
36

of processes and theories. It will serve as a guide in doing the research, to identify
the core set of connectors within the topic and shows how they fit together.

3.1 Statement of Assumptions

3.1.1 The the administrator or head faculty Personnel will provide all
the information needed by the researchers for the proposed system.
All the information needed from the school college will be given,
mostly the existing system processes will be identified to let the
researchers know what are the things needed to do.

3.1.2 The administrator or head college, adviser, panelist and should be
Computer literate and he/she needs to learn the different functions
of the proposed system.
The administrator or head college, adviser, panelist should at least
know the basic functions of the proposed system so that it will be
used correctly.

3.1.3 The administrator or head college, adviser, panelist will support
the researchers regarding the proposed system.
All the information that is needed to know will be given so that the
researchers will be able to understand the proposed system.

37

3.1.4 The administrator or head college, adviser, panelist will be
cooperating or willing to cooperate with the requirements of the
proposed system needed by the researchers.
The administrator or head college, adviser, panelist should let the
researchers know all about the information of the proposed system.
3.1.5 The administrator or head college, adviser, panelist should be
willing to adopt and use the proposed system.
The administrator or head college, adviser, panelist should start to
adopt in the proposed system so it will be implemented and be
used by the whole COECSA-COLLEGE.


3.2 Operational Definitions
Operational definition a very clear and very precise explanation of
the items being measured or the terms that are used to ensures
comprehensible knowledge of the terminology and the ability to operate a
process, procedure, or service and/or collect data consistently and reliably.
3.2.1 Definition of terms
3.2.1.1. User- Someone who interacts with the web application system
3.2.1.2. Admin/Administrator -System administrator who is given a
specific permission for managing and controlling the system
3.2.1.3. Advisers - Someone who can manage the sections who are
involved in the research presenters; they are also in-charge of handling
38

researches of their students. They can also grade the research
presenters.
3.2.1.4. Panelist - Someone who will use the application for grading the
research presenters
3.2.1.5. DCS - Department of Computer Studies
3.2.1.6. DSS - Decision Support System, a computer-based information
system that supports business or organizational decision-making
activities
3.2.1.7. Scheduling - Arrange or plan (an event) to take place at a
particular time.
3.2.1.8. Grading - Arrange in or allocate to grades; class or sort.
3.2.1.9. Management - The process of dealing with or controlling things
or people.
3.2.1.10. Research - The systematic investigation into and study of
materials and sources in order to establish facts and reach new
conclusions.
3.2.1.11. Web Application - Any application software that runs in a web
browser and is created in a browser-supported programming language
(such as the combination of JavaScript, HTML and CSS) and relies on
a common web browser to render the application.
3.2.1.12. HTML - Hypertext Markup Language, a standardized system for
tagging text files to achieve font, color, graphic, and hyperlink effects
on World Wide Web pages.
39

3.2.1.13. CSS - A style sheet language used for describing the look and
formatting of a document written in a markup language.
3.2.1.14. Javascript - An object-oriented computer programming language
commonly used to create interactive effects within web browsers.
3.2.1.15. PHP - PHP: Hypertext Preprocessor, which is a recursive
acronym. PHP code can be simply mixed with HTML code, or it can be
used in combination with various templating engines and web
frameworks.
3.2.1.16. JQuery - A free and open source JavaScript library that is used by
Web developers to navigate HTML documents, handle events, perform
animations and add Ajax interactions to Web pages.
3.2.1.17. DESC Description
3.2.1.18. RAT Rational
3.2.1.19. DEP - Dependencies



3.2.2 Definition of Processes
3.2.2.1 Existing System Processes
1. Schedule the presenter The process which the head of
the faculty will check the records of the presenters if
already exists in the system and if there is no record she can
schedule the presenters to present their research project,
record in the record book and encode in Microsoft excel.
40

2. Grade Research project The process where the head of
the faculty will grade the research project in a yellow paper
or paper that can be used to grade research project and
encode in Microsoft excel.
3. Encode records The process which the office manager
encodes records in Microsoft Office Excel to produce
reports that will be given to the owner.
Proposed System Processes
1. Register the faculty or adviser The process which will
monitor if the faculty or adviser information already exists
in the faculty or adviser user list and if not the admin will
approved the registration of the faculty.
2. Schedule the presenter They schedule the research
project according to the free time of the faculty or adviser
of the presenter, by simply drag and drop on the available
time. And can easily edit, add, and delete if there is a
problem occur.
3. Grading the Research Project The process where the
head of the faculty will grade the research project in the
system to grade research project and automatically
compute the grade and see the result.
4. Produce Reports The process of generating the
particular reports such as Schedule, Grades.
41








3.3 Concepts Used in the Study
Water Fall Model
The waterfall model is a sequential design process, often used in
software development processes, in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases of Conception, Initiation,
Analysis, Design, Construction, Testing, Production/Implementation, and
Maintenance.
(www.wikipedia.org)
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 six distinct phases, described below:

Water runs over the following seven stages
1. Planning
2. System Analysis
3. System Design
42

4. Implementation
5. System Operation and Support





1. Planning
The stage of planning is the most important in making a system, the
Developer analyses users requirement and, performs further investigation of
requirements, produces developers version of requirements. Since oftentimes
users are unable to describe what they need with precision. However, when the
developer finally gets the users to accept the proposal they can now begin.
2. System Analysis
This second step is also the most important, because it involves gathering
information about what the customer needs and defining, in the clearest possible
terms, the problem that the product is expected to solve. Analysis includes
understanding the customer's business context and constraints, the functions the
product must perform, the performance levels it must adhere to, and the external
systems it must be compatible with. Techniques used to obtain this understanding
include customer interviews, use cases, and "shopping lists" of software features.
The results of the analysis are typically captured in a formal requirements
specification, which serves as input to the next step.
43






3. System Design
This step consists of "defining the hardware and software architecture,
components, modules, interfaces, and data...to satisfy specified requirements"
(Wikipedia). It involves defining the hardware and software architecture,
specifying performance and security parameters, designing data storage
containers and constraints, choosing the IDE and programming language, and
indicating strategies to deal with issues such as exception handling, resource
management and interface connectivity. This is also the stage at which user
interface design is addressed, including issues relating to navigation and
accessibility. The output of this stage is one or more design specifications, which
are used in the next stage of implementation.
4. Implementation
This step consists of actually constructing the product as per the design
specification(s) developed in the previous step. Typically, this step is performed
by a development team consisting of programmers, interface designers and other
specialists, using tools such as compilers, debuggers, interpreters and media
editors. The output of this step is one or more product components, built
according to a pre-defined coding standard and debugged, tested and integrated to
44

satisfy the system architecture requirements. For projects involving a large team,
version control is recommended to track changes to the code tree and revert to
previous snapshots in case of problems.
In this stage, both individual components and the integrated whole are
methodically verified to ensure that they are error-free and fully meet the
requirements outlined in the first step. An independent quality assurance team
defines "test cases" to evaluate whether the product fully or partially satisfies the
requirements outlined in the first step. Three types of testing typically take place:
unit testing of individual code modules; system testing of the integrated product;
and acceptance testing, formally conducted by or on behalf of the customer.
Defects, if found, are logged and feedback provided to the implementation team
to enable correction. This is also the stage at which product documentation, such
as a user manual, is prepared, reviewed and published.
5. System Operation and Support
This step occurs once the product has been tested and certified as fit for
use, and involves preparing the system or product for installation and use at the
customer site. Delivery may take place via the Internet or physical media, and the
deliverable is typically tagged with a formal revision number to facilitate updates
at a later date.
This step occurs after installation, and involves making modifications to
the system or an individual component to alter attributes or improve performance.
These modifications arise either due to change requests initiated by the customer,
or defects uncovered during live use of the system. Typically, every change made
45

to the product during the maintenance cycle is recorded and a new product release
(called a "maintenance release" and exhibiting an updated revision number) is
performed to enable the customer to gain the benefit of the update.
Data Flow Diagram
A data flow diagram (DFD) is a graphical representation of the "flow" of
data through an information system, modeling its process aspects. Often they are a
preliminary step used to create an overview of the system. DFDs can also be used
for the visualization of data processing (structured design).
(www.wikipedia.org)
A DFD shows what kinds of information will be input to and output from
the system, where the data will come from and go to, and where the data will be
stored. It does not show information about the timing of processes, or information
about whether processes will operate in sequence or in parallel (which is shown
on a flowchart).
Theory
It is common practice to draw the context-level data flow diagram first,
which shows the interaction between the system and external agents which act as
data sources and data sinks. On the context diagram the system's interactions with
the outside world are modelled purely in terms of data flows across the system
boundary. The context diagram shows the entire system as a single process, and
gives no clues as to its internal organization.
This context-level DFD is next "exploded", to produce a Level 1 DFD that
shows some of the detail of the system being modeled. The Level 1 DFD shows
46

how the system is divided into sub-systems (processes), each of which deals with
one or more of the data flows to or from an external agent, and which together
provide all of the functionality of the system as a whole. It also identifies internal
data stores that must be present in order for the system to do its job, and shows the
flow of data between the various parts of the system.
Data flow diagrams were proposed by Larry Constantine, the original
developer of structured design, based on Martin and Estrin's "data flow graph"
model of computation.
Data flow diagrams are one of the three essential perspectives of the
structured-systems analysis and design method SSADM. The sponsor of a project
and the end users will need to be briefed and consulted throughout all stages of a
system's evolution. With a data flow diagram, users are able to visualize how the
system will operate, what the system will accomplish, and how the system will be
implemented. The old system's dataflow diagrams can be drawn up and compared
with the new system's data flow diagrams to draw comparisons to implement a
more efficient system. Data flow diagrams can be used to provide the end user
with a physical idea of where the data they input ultimately has an effect upon the
structure of the whole system from order to dispatch to report. How any system is
developed can be determined through a data flow diagram model.
In the course of developing a set of leveled data flow diagrams the
analyst/designers is forced to address how the system may be decomposed into
component sub-systems, and to identify the transaction data in the data model.
47

Data flow diagrams can be used in both Analysis and Design phase of the
SDLC.
There are different notations to draw data flow diagrams (Yourdon & Coad
and Gane&Sarson), defining different visual representations for processes, data
stores, data flow, and external entities.
(www.infocenter.sybase.com)
Database Management System (DBMS)
A database is an organized collection of data. The data are typically
organized to model relevant aspects of reality in a way that supports processes
requiring this information. For example, modeling the availability of rooms in
hotels in a way that supports finding a hotel with vacancies.
Database management systems (DBMS)
DBMS are specially designed applications that interact with the user, other
applications, and the database itself to capture and analyze data. A general-
purpose database management system (DBMS) is a software system designed to
allow the definition, creation, querying, update, and administration of databases.
Well-known DBMSs include MySQL, PostgreSQL, SQLite, Microsoft SQL
Server, Microsoft Access, Oracle, SAP, dBASE, FoxPro, IBM DB2, LibreOffice
Base and FileMaker Pro. A database is not generally portable across different
DBMS, but different DBMSs can inter-operate by using standards such as SQL
and ODBC or JDBC to allow a single application to work with more than one
database.
(www.wikipedia.org)
48



Terminology and overview
Formally, the term "database" refers to the data itself and supporting data
structures. Databases are created to operate large quantities of information by
inputting, storing, retrieving, and managing that information. Databases are set up
so that one set of software programs provides all users with access to all the data.
A "database management system" (DBMS) is a suite of computer software
providing the interface between users and a database or databases. Because they
are so closely related, the term "database" when used casually often refers to both
a DBMS and the data it manipulates.
Outside the world of professional information technology, the term
database is sometimes used casually to refer to any collection of data (perhaps a
spreadsheet, maybe even a card index). This article is concerned only with
databases where the size and usage requirements necessitate use of a database
management system.
The interactions catered for by most existing DBMS fall into four main
groups:
Data definition. Defining new data structures for a database, removing
data structures from the database, modifying the structure of existing data.
Update. Inserting, modifying, and deleting data.
Retrieval. Obtaining information either for end-user queries and reports or
for processing by applications.
49

Administration. Registering and monitoring users, enforcing data security,
monitoring performance, maintaining data integrity, dealing with concurrency
control, and recovering information if the system fails.
A DBMS is responsible for maintaining the integrity and security of stored
data, and for recovering information if the system fails.
Both a database and its DBMS conform to the principles of a particular
database model. "Database system" refers collectively to the database model,
database management system, and database.
Physically, database servers are dedicated computers that hold the actual
databases and run only the DBMS and related software. Database servers are
usually multiprocessor computers, with generous memory and RAID disk arrays
used for stable storage. RAID is used for recovery of data if any of the disks fails.
Hardware database accelerators, connected to one or more servers via a high-
speed channel, are also used in large volume transaction processing environments.
DBMSs are found at the heart of most database applications. DBMSs may be built
around a custom multitasking kernel with built-in networking support, but modern
DBMSs typically rely on a standard operating system to provide these
functions.[citation needed] Since DBMSs comprise a significant economical
market, computer and storage vendors often take into account DBMS
requirements in their own development plans.[citation needed]
Databases and DBMSs can be categorized according to the database
model(s) that they support (such as relational or XML), the type(s) of computer
they run on (from a server cluster to a mobile phone), the query language(s) used
50

to access the database (such as SQL or XQuery), and their internal engineering,
which affects performance, scalability, resilience, and security.
Query Ability - Querying is the process of requesting attribute
information from various perspectives and combinations of factors.
(www.dbmswork.blogspot.com)
Database Query Language and report - Database Query Language and
report writer allow users to interactively interrogate the database, analyze its data
and update it according to the users privileges on data. It also controls the
security of the database. Data security prevents unauthorized users from viewing
or updating the database. Using passwords, users are allowed access to the entire
database or subsets of it called subschemas. For example, an employee database
can contain all the data about an individual employee, but one group of users may
be authorized to view only payroll data, while others are allowed access to only
work history and medical data. If the DBMS provides a way to interactively enter
and update the database, as well as interrogate it, this capability allows for
managing personal databases. However it may not leave an audit trail of actions
or provide the kinds of controls necessary in a multi-user organization. These
controls are only available when a set of application programs are customized for
each data entry and updating function.
Backup and Replication - Copies off attributes need to be made regularly
in case primary disks or other equipment fails. A periodic copy of attributes may
be also created for a distant organization that cannot readily access the original.
51

DBMS usually provide utilities to facilitate the process of extracting and
disseminating attribute sets.
Rule Enforcement - Often one wants to apply rules to attributes so that
the attributes are clean and reliable. For example, we may have rule that says each
car can have one engine associated with it (identified by Engine Number)
Security - For security reasons, it is desirable to limit who can see or
change specific attributes or groups of attributes. This may be managed directly
on an individual basis, or by the assignment of individuals and privileges to
groups m or (in the most elaborate models).
Computation - Common computations requested on attributes are
counting, summing, averaging, sorting, grouping, cross referencing, and so on.
Rather than have each computer application implement these from scratch, they
can rely on the DBMS to supply such calculations.
Change and access logging - This describes who accessed which
attributes, what was changed, and when it was changed. Logging services allow
this by keeping a record of occurrences and changes
Automated optimization - For frequently occurring usage patterns or
requests, some DBMS can adjust themselves to improve the speed of those
interactions. In some cases the DBMS will merely provide tools to monitor
performance, allowing a human expert to make the necessary adjustments after
reviewing the statistics collected.



52

Chapter 4
Methodology
4.1 Environment
4.1.1 Locale
The locale of the proposed system was set for the Lyceum of the
Philippine University of General Trias, Cavite.

4.1.2 Population of the Study

The user of the system DCS - Faculty of Cavite is estimated for
about 40 persons/Faculty member and it is continuing to grow fast.


4.2 Requirements Specifications
4.2.1 Operational Feasibility

4.2.1.1 Fishbone Diagram
4.2.1.2 Functional Decomposition Diagram
4.2.1.3 Human Resources Requirements
4.2.1.3.1 The System Analyst
A system analyst investigates, analyses, plans solution,
designs, develops, evaluates, and coordinates to meet the specific
requirements that the system must satisfy. They are not normally
involved in the actual hardware or software development though
they may be familiar in operating system or other programming
53

languages. The system analyst is responsible for all the tasks on
how the system will be developed.
A system analyst must have a broad knowledge technically,
and a logical approach to problem solving. They need to have an
ability to contribute to a team effort, have good interpersonal skills,
excellent oral and written communication skills to interact
with people at all levels. A system analyst also needs to have a
degree in Information system, computer science, business or if non
IT-related subjects, a relevant postgraduate qualification may be
useful.
4.2.1.3.2 The Programmer
A programmer is a person who writes system software.
They are assigned to code programs to create the system, and the
overall functions and performance of the user interface, and its
connection to the database needed.
A programmer should have a background on different
forms of computer coding language such as SQL which is used for
database, HTML, PHP, Java and more. They compose instructions
for computer systems to perform a given action.
4.2.1.3.3 The Trainer
A trainer is the person who guides, coaches, or give
knowledge to another person in a particular subject matter. The
54

main task of the trainer for using the proposed system is to guide
and teach the end user on how to operate the system. They are the
one whos responsible to teach and educate the user which is the
administrator or other personnel that will be involved in the whole
process. The programmer can also serves as the trainer since they
know the flow of the whole system.
A trainer should know how to share their knowledge in the
easiest but understandable way for the user to follow correctly.
4.2.1.3.4 The User
The users will be the administrator, the customer, the
system programmer, and the database manager. The administrator
and the customer will be the end users, they need to have enough
knowledge how to operate the system and the proponents are going
to conduct trainings so they will be familiar to the system. The
system programmer and the database manager is still considered as
users since they are assigned to fix bugs and update software and
hardware that will be used in the system.




55

4.2.2 Technical Feasibilty
4.2.2.1 Combatibilty checking (Hardware/Software and other
technologies)
4.2.2.1.1 System Installation
The proposed system is installed upon the approval of the
COECSA Head Faculty as they are the ones to give the
authorization to use the system. The system is can be access
thru lan which are for Head Faculty. A compute will also be
placed in the database of the system. This is scheduled on
September 20, 2014.
4.2.2.1.2 Conversion Plans
The proponents used the parallel conversion plan. With this
kind of plan, there is ease in comparing both systems. The
established solutions are easily shown as both systems run at the
same time. This kind of plan clarifies if the requirements are met
by the new system. From the obtained results, evaluating the
system can be done quickly and efficiently.




56

4.2.2.1.3 Training Plans
The proponents handled just one day for training
seminars. The reason why the training is just for one day is
because the Head of the faculty in the faculty, who will access the
system, is an I.T. also. So we just have to teach him about the
functionalities.
The objective of these training is to give knowledge to the
Head of the faculty who will be handling the system and also give
instructions on how the system may be operated. The proponents
find it important to implement trainings so that the Head of the
faculty will be capable to handle the system appropriately and
efficiently. The training involves demonstration on how the system
works, proper handling, troubleshooting, familiarization in using
Microsoft Office Access, how database works, and maintaining
record in the database, time keeping system works and
implementing instructions or rules on how the system will work
according to the guidelines set modules. This training is not only
for the two users of the system but for those employees who handle
the scheduling system.



57

Schedule of training:
Date Activity Participants Facilitator
September 20,
2013
Installation of the
system and
demonstration on
how the system
operates.
Employees of the
Head of the faculty
and Professor.
Proponents
September 21,
2013
Giving of
guidelines and
instruction on how
the system will be
implemented
Employees of the
Lyceum Philippine
University.
Proponents
Table 4.1 Schedule if Training

4.2.2.1.4 Testing
The accuracy of the system is put into a test. This proves
that the proposed system has met the requirements established to
come up on an effective attendance monitoring process. System
testing is done by the employees who are the users of system. End
users had run a comprehensive testing on the system to perform
designated task. Then, all the process on the system is checked to
determine the dependability of the system.
58

The proponents tested each module set. To make sure that
all the components of program are working properly. The
proponents used a bottom up approach of integration where all low
level modules are tested first before going up to the next level.

Date Action to be taken
September 23, 2014 The different modules are tested.
September 24, 2014 Modifications in the system are tested.
Table 4.2 Schedule of Testing
4.2.2.1.4 Maintenance Plan
The system should always be under the care of
programmers, system analysts, database managers, and especially
users. The software and hardware that is applied in the system
should maintain the requirements so it will not malfunction.
Maintenance plan will be implemented to identify and arrange all
required elements then repair in an orderly manner.
Users may use the system after the implementation and this
will come up with future support so that it will be uphold by
actions.


59

4.2.2.2 Relevance of the technologies
4.2.2.2.1 Software
The system software will keep up to date and will be provided
support for bug fixes. The proponents will immediately take action
depending upon the preferred choice of the company to ensure stable
function of the system.
4.2.3.2 Hardware
Cable, Keyboard, mouse, fingerprint scanner, and wirings will be
replaced when theres unnecessary errors occur. The router should also be
upgraded or replaced when needed to hasten the connection.










60

4.2.3 Schedule Feasibility
4.2.3.1 Gant Chart
FIGURE No. Gantt chart

61

Table Pert/CPM and Gantt chart List of Activities

PERT/CPM and Gantt chart List of Activities















Task/Activities

Duration (In days)

Predecessor
A. Planning 8 -
B. Client Searching 4 A
C. Information Gathering 4 B
D. Chapter 1 (Introduction) 8 C
E. Chapter 2 (Review of Related
Literature)
70 D
F. Chapter 3 and 4 ( TECHNICAL
BACKGROUND and -
METHODOLOGY)
14 E
G. DFD (Data Flow Diagram) 8 E
H. User Layout and Interface 4 G
I. Programming 60 F, G
J. Chapter 5 ( SUMMARY,
CONCLUSIONS AND
RECOMMENDATIONS )
10 H
K. Chapter 6 (IMPLEMENTATION
PLAN)
20 I
L. Final Draft of Documents 4 J, K
M. Mock Defense 2 I
N. Final Defense 6 L, M
A B C D
E
F
G
H
I
J
K
L
M
4
8
4 8
N
7
0
1
4
8
4
6
0
1
0
20
4
2
6
62



CPM
PATH 1: A+B+C+D+E+F+I+M+N PATH 4: A+B+C+D+E+G+I+K+L+N
8+4+4+8+70+14+60+2+6=176 8+4+4+8+70+8+60+20+4+6 = 192

PATH 2: A+B+C+D+E+F+I+K+L+N PATH 5: A+B+C+D+E+G+H+J+L+N
8+4+4+8+70+14+60+20+4+6 = 19 8+4+4+8+70+8+4+10+4+6 = 126

PATH 3: A+B+C+D+E+G+I+M+N
8+4+4+8+70+8+60+2+6 = 170
The critical path is Path 2 which is composed of 198 days. It consists of A. Planning, B.
Client Searching, C. Information Gathering, and D. Chapter 1, E. Chapter 2, F.
Chapter 3 & 4, I. Programming, K. Chapter 6, 7 & 8, L. Final Drafts of Document, and N.
Final Defense.



4.2.4 Economic Feasibility
4.2.8.1 Cost Benefit Analysis
4.2.8.2 Cost Recovery Scheme




Figure No. 5.4 PERT Diagram
63

4.2.5 Requirements Modeling
4.2.5.1 Inputs

Name of document: Student Data
Prepared by: Student
Number of copies: 1
Purpose: To provide details in the registration of Student.

Name of Document: Faculty Data
Prepared By: Faculty
Number of copies: 1
Purpose: To provide details in enrolling Faculty






64

Name of Document: Students Grades status, data and details
Prepared by: Faculty or Administrator
Number of copies: 1
Purpose: To provide Grades status and details.



4.2.5.2 Process
4.2.5.2.1 Register Student Records
BEGIN
IF Student is not registered in Student data the admin ipput
a data THEN
Obtain Student data from student
IF Student data is valid THEN
Register Customer
IF Student is registered, not enrolled or
Inactive THEN
Activate/Renew registered Student in
the program he/she choose.
65

END IF
The Student must register first by
admin/adviser before scheduling.
END IF
The admin must input a correct data
END IF
END
4.2.5.2.2 Register Faculty Records
BEGIN
IF Faculty is not registered in Faculty data data the admin
ipput a data THEN
Obtain Faculty data from Faculty
IF Faculty data is valid THEN
Register Customer
IF Faculty is registered, not enrolled or
Inactive THEN
Activate/Renew registered Faculty in
the program he/she choose.
END IF
66

The Faculty must register first by
admin/adviser before scheduling.
END IF
The admin must input a correct data
END IF
END


4.2.5.3 Grading of research project
BEGIN
IF Student is now registered THEN
The grade details store in grade record.
IF Student grade a research project THEN
The Student data sent to grade record from
panelist
END IF
END IF
END

67

4.2.5.4 Generate Schedule
BEGIN
IF Student is now registered, status is active THEN
The faculty can now view and print the schedule of
the student.
END IF
END


4.2.5.5 Generate Grades
BEGIN
IF Student is now registered, status is active THEN
The faculty can now grade and print the result of
research project of the student.
END IF
END



68

4.2.5.6 Produce Reports
BEGIN
GET Schedule record form from Schedule.
GET Grades records from Grades.
END
4.5.3 Output
Name of Document: Schedule
Prepared By: Administrator
Number of copies: 2
Frequency of distribution: Distributed once you are registered in the
system in the Online Scheduling, Grading and
Management for DCS research Presentation
Purpose: To provide the student schedule id the
Schedule for every registration made.
Recipient: Student and Administrator

Name of Document: Grades
Prepared By: Administrator
Number of copies: 2
69

Frequency of distribution: Distributed when the student are registered in
the Online Scheduling, Grading and
Management for DCS research Presentation
Purpose: To provide the computation of the grades and
result.
Recipient: Student, Faculty and Administrator
4.2.5.4 Performance
Water Fall Model
The waterfall model is a sequential design process, often used in
software development processes, in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases of Conception, Initiation,
Analysis, Design, Construction, Testing, Production/Implementation, and
Maintenance.
(www.wikipedia.org)
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 six distinct phases, described below:

Water runs over the following seven stages
1. Planning
2. System Analysis
3. System Design
70

4. Implementation
5. System Operation and Support

1. Planning
The stage of planning is the most important in making a system, the
Developer analyses users requirement and, performs further investigation of
requirements, produces developers version of requirements. Since oftentimes
users are unable to describe what they need with precision. However, when the
developer finally gets the users to accept the proposal they can now begin.
2. System Analysis
This second step is also the most important, because it involves gathering
information about what the customer needs and defining, in the clearest possible
terms, the problem that the product is expected to solve. Analysis includes
understanding the customer's business context and constraints, the functions the
product must perform, the performance levels it must adhere to, and the external
systems it must be compatible with. Techniques used to obtain this understanding
include customer interviews, use cases, and "shopping lists" of software features.
The results of the analysis are typically captured in a formal requirements
specification, which serves as input to the next step.

3. System Design
This step consists of "defining the hardware and software architecture,
components, modules, interfaces, and data...to satisfy specified requirements"
71

(Wikipedia). It involves defining the hardware and software architecture,
specifying performance and security parameters, designing data storage
containers and constraints, choosing the IDE and programming language, and
indicating strategies to deal with issues such as exception handling, resource
management and interface connectivity. This is also the stage at which user
interface design is addressed, including issues relating to navigation and
accessibility. The output of this stage is one or more design specifications, which
are used in the next stage of implementation.
4. Implementation
This step consists of actually constructing the product as per the design
specification(s) developed in the previous step. Typically, this step is performed
by a development team consisting of programmers, interface designers and other
specialists, using tools such as compilers, debuggers, interpreters and media
editors. The output of this step is one or more product components, built
according to a pre-defined coding standard and debugged, tested and integrated to
satisfy the system architecture requirements. For projects involving a large team,
version control is recommended to track changes to the code tree and revert to
previous snapshots in case of problems.
In this stage, both individual components and the integrated whole are
methodically verified to ensure that they are error-free and fully meet the
requirements outlined in the first step. An independent quality assurance team
defines "test cases" to evaluate whether the product fully or partially satisfies the
requirements outlined in the first step. Three types of testing typically take place:
72

unit testing of individual code modules; system testing of the integrated product;
and acceptance testing, formally conducted by or on behalf of the customer.
Defects, if found, are logged and feedback provided to the implementation team
to enable correction. This is also the stage at which product documentation, such
as a user manual, is prepared, reviewed and published.
5. System Operation and Support
This step occurs once the product has been tested and certified as fit for
use, and involves preparing the system or product for installation and use at the
customer site. Delivery may take place via the Internet or physical media, and the
deliverable is typically tagged with a formal revision number to facilitate updates
at a later date.
This step occurs after installation, and involves making modifications to
the system or an individual component to alter attributes or improve performance.
These modifications arise either due to change requests initiated by the customer,
or defects uncovered during live use of the system. Typically, every change made
to the product during the maintenance cycle is recorded and a new product release
(called a "maintenance release" and exhibiting an updated revision number) is
performed to enable the customer to gain the benefit of the update.
Data Flow Diagram
A data flow diagram (DFD) is a graphical representation of the "flow" of
data through an information system, modeling its process aspects. Often they are a
preliminary step used to create an overview of the system. DFDs can also be used
for the visualization of data processing (structured design).
73

(www.wikipedia.org)
A DFD shows what kinds of information will be input to and output from
the system, where the data will come from and go to, and where the data will be
stored. It does not show information about the timing of processes, or information
about whether processes will operate in sequence or in parallel (which is shown
on a flowchart).
Theory
It is common practice to draw the context-level data flow diagram first,
which shows the interaction between the system and external agents which act as
data sources and data sinks. On the context diagram the system's interactions with
the outside world are modelled purely in terms of data flows across the system
boundary. The context diagram shows the entire system as a single process, and
gives no clues as to its internal organization.
This context-level DFD is next "exploded", to produce a Level 1 DFD that
shows some of the detail of the system being modeled. The Level 1 DFD shows
how the system is divided into sub-systems (processes), each of which deals with
one or more of the data flows to or from an external agent, and which together
provide all of the functionality of the system as a whole. It also identifies internal
data stores that must be present in order for the system to do its job, and shows the
flow of data between the various parts of the system.
Data flow diagrams were proposed by Larry Constantine, the original
developer of structured design, based on Martin and Estrin's "data flow graph"
model of computation.
74

Data flow diagrams are one of the three essential perspectives of the
structured-systems analysis and design method SSADM. The sponsor of a project
and the end users will need to be briefed and consulted throughout all stages of a
system's evolution. With a data flow diagram, users are able to visualize how the
system will operate, what the system will accomplish, and how the system will be
implemented. The old system's dataflow diagrams can be drawn up and compared
with the new system's data flow diagrams to draw comparisons to implement a
more efficient system. Data flow diagrams can be used to provide the end user
with a physical idea of where the data they input ultimately has an effect upon the
structure of the whole system from order to dispatch to report. How any system is
developed can be determined through a data flow diagram model.
In the course of developing a set of leveled data flow diagrams the
analyst/designers is forced to address how the system may be decomposed into
component sub-systems, and to identify the transaction data in the data model.
Data flow diagrams can be used in both Analysis and Design phase of the
SDLC.
There are different notations to draw data flow diagrams (Yourdon & Coad
and Gane&Sarson), defining different visual representations for processes, data
stores, data flow, and external entities.
(www.infocenter.sybase.com)
Database Management System (DBMS)
A database is an organized collection of data. The data are typically
organized to model relevant aspects of reality in a way that supports processes
75

requiring this information. For example, modeling the availability of rooms in
hotels in a way that supports finding a hotel with vacancies.
Database management systems (DBMS)
DBMS are specially designed applications that interact with the user, other
applications, and the database itself to capture and analyze data. A general-
purpose database management system (DBMS) is a software system designed to
allow the definition, creation, querying, update, and administration of databases.
Well-known DBMSs include MySQL, PostgreSQL, SQLite, Microsoft SQL
Server, Microsoft Access, Oracle, SAP, dBASE, FoxPro, IBM DB2, LibreOffice
Base and FileMaker Pro. A database is not generally portable across different
DBMS, but different DBMSs can inter-operate by using standards such as SQL
and ODBC or JDBC to allow a single application to work with more than one
database.
(www.wikipedia.org)


4.2.5.5 Control
Formally, the term "database" refers to the data itself and supporting data
structures. Databases are created to operate large quantities of information by
inputting, storing, retrieving, and managing that information. Databases are set up
so that one set of software programs provides all users with access to all the data.
A "database management system" (DBMS) is a suite of computer software
providing the interface between users and a database or databases. Because they
76

are so closely related, the term "database" when used casually often refers to both
a DBMS and the data it manipulates.
Outside the world of professional information technology, the term
database is sometimes used casually to refer to any collection of data (perhaps a
spreadsheet, maybe even a card index). This article is concerned only with
databases where the size and usage requirements necessitate use of a database
management system.
The interactions catered for by most existing DBMS fall into four main
groups:
Data definition. Defining new data structures for a database, removing
data structures from the database, modifying the structure of existing data.
Update. Inserting, modifying, and deleting data.
Retrieval. Obtaining information either for end-user queries and reports or
for processing by applications.
Administration. Registering and monitoring users, enforcing data security,
monitoring performance, maintaining data integrity, dealing with concurrency
control, and recovering information if the system fails.
A DBMS is responsible for maintaining the integrity and security of stored
data, and for recovering information if the system fails.
Both a database and its DBMS conform to the principles of a particular
database model. "Database system" refers collectively to the database model,
database management system, and database.
77

Physically, database servers are dedicated computers that hold the actual
databases and run only the DBMS and related software. Database servers are
usually multiprocessor computers, with generous memory and RAID disk arrays
used for stable storage. RAID is used for recovery of data if any of the disks fails.
Hardware database accelerators, connected to one or more servers via a high-
speed channel, are also used in large volume transaction processing environments.
DBMSs are found at the heart of most database applications. DBMSs may be built
around a custom multitasking kernel with built-in networking support, but modern
DBMSs typically rely on a standard operating system to provide these
functions.[citation needed] Since DBMSs comprise a significant economical
market, computer and storage vendors often take into account DBMS
requirements in their own development plans.[citation needed]
Databases and DBMSs can be categorized according to the database
model(s) that they support (such as relational or XML), the type(s) of computer
they run on (from a server cluster to a mobile phone), the query language(s) used
to access the database (such as SQL or XQuery), and their internal engineering,
which affects performance, scalability, resilience, and security.
Query Ability - Querying is the process of requesting attribute
information from various perspectives and combinations of factors.
(www.dbmswork.blogspot.com)
Database Query Language and report - Database Query Language and
report writer allow users to interactively interrogate the database, analyze its data
and update it according to the users privileges on data. It also controls the
78

security of the database. Data security prevents unauthorized users from viewing
or updating the database. Using passwords, users are allowed access to the entire
database or subsets of it called subschemas. For example, an employee database
can contain all the data about an individual employee, but one group of users may
be authorized to view only payroll data, while others are allowed access to only
work history and medical data. If the DBMS provides a way to interactively enter
and update the database, as well as interrogate it, this capability allows for
managing personal databases. However it may not leave an audit trail of actions
or provide the kinds of controls necessary in a multi-user organization. These
controls are only available when a set of application programs are customized for
each data entry and updating function.
Backup and Replication - Copies off attributes need to be made regularly
in case primary disks or other equipment fails. A periodic copy of attributes may
be also created for a distant organization that cannot readily access the original.
DBMS usually provide utilities to facilitate the process of extracting and
disseminating attribute sets.
Rule Enforcement - Often one wants to apply rules to attributes so that
the attributes are clean and reliable. For example, we may have rule that says each
car can have one engine associated with it (identified by Engine Number)
Security - For security reasons, it is desirable to limit who can see or
change specific attributes or groups of attributes. This may be managed directly
on an individual basis, or by the assignment of individuals and privileges to
groups m or (in the most elaborate models).
79

Computation - Common computations requested on attributes are
counting, summing, averaging, sorting, grouping, cross referencing, and so on.
Rather than have each computer application implement these from scratch, they
can rely on the DBMS to supply such calculations.
Change and access logging - This describes who accessed which
attributes, what was changed, and when it was changed. Logging services allow
this by keeping a record of occurrences and changes
Automated optimization - For frequently occurring usage patterns or
requests, some DBMS can adjust themselves to improve the speed of those
interactions. In some cases the DBMS will merely provide tools to monitor
performance, allowing a human expert to make the necessary adjustments after
reviewing the statistics collected.


4.2.5.6 Data and Process Modeling
4.2.5.6.1 Context Diagram
4.2.5.7 Object Modeling
4.2.5.7.1
4.2.6 Risk Management/Analysis




80














Chapter 5
Proposed System

5.1 System Overview
The proposed system is made to facilitate all the customers needed
information in ARMM Gym efficiently. The traditional system will be replaced by
an Online Gym B-Pass System.
The proposed system will lessen the time of compiling customer's record
to produce reports viewing the companys progress from the record books that is
81

needed by the owner. This will also lessen the time used in the registration and
logging in process.
The system also has an interface that is meant for the customer, for them
to be able to register online. The customer can view their past records attended
in the gym and their present program they are enrolled at. They can also monitor
how many sessions left that they have in the gym.
The proposed system also produces reports in just few clicks. The
administrator will just have to select group of records that is needed for the report
and then the proposed system will generate it automatically.
















User Logs Details
Program Subscription
Details
Payment
Customer
Information/Subscript
ion
Program Subscription
Report
Payments Report
User Logs Report
Customer Data/Fingerprint
Customer Payment
Status and Details


Administrator/
Owner

0

ARMM
Attendance
Monitoring
System



CUSTOMER

Receipt
82




Figure No. 5.1 Context Diagram Proposed System of the
ARMM GYM B-Pass System












83

Figure No. 5.2 Level 0 Diagram of the Proposed of the ARMM GYM B-
Pass System








84

5.3 System Objectives
5.2.1 To generate and provide company a well-organized data.
5.2.2 To conserve time in processing enrollment in the Gym.
5.2.3 To secure the data of the Gym enrollee.
5.2.4 To have more efficient data storage.
5.2.5 To have and efficient, adding, deleting, story and processing of the
Gym enrollees files.

5.4 Scope and Limitations of Proposed System
5.3.1 This study is created for the Online Gym B-Pass System processes
of the ARMM GYM.
5.3.2 Our Online Gym B-Pass System will have a database that will
manage all the clients files and other records.
5.3.3 The system has two user levels to provide security to the clients
information.
5.3.4 This can also manage the accounts and the schedule of the clients if
there are charges.
5.3.5 The system can also view online.





85

5.5 System Justification
As a prolific Gym, there is a need for computerized Online Gym B-Pass
System. The number of customers is growing and so the Gym see that there's
still a lot of improvements needed to accommodate all the customers.
The proposed system will help the Gym to be more competitive by means
of having an organized flow of registration process and monitoring attendance of
customers that is accurate to the sessions depending on their programs.
The system study will help the personnel to lessen the time of finding all
the records, compiling, and encoding it into Microsoft Excel.















86

5.6 Project Schedule

FIGURE No. 5.3 Gantt chart
87



Table 5.1 Pert/CPM and Gantt chart List of Activities
















Task/Activities

Duration (In days)

Predecessor
A. Planning 8 -
B. Client Searching 4 A
C. Information Gathering 4 B
D. Chapter 1 (Introduction) 8 C
E. Chapter 2 (Review of Related
Literature)
70 D
F. Chapter 3 and 4 (Theoretical
Framework and Existing system)
14 E
G. DFD (Data Flow Diagram) 8 E
H. User Layout and Interface 4 G
I. Programming 60 F, G
J. Chapter 5 (The Proposed System) 10 H
K. Chapter 6,7 and 8
*Design of the Proposed System
*Testing Implementation
*Conclusion and Recommendation
20 I
L. Final Draft of Documents 4 J, K
M. Mock Defense 2 I
N. Final Defense 6 L, M
88


PERT/CPM and Gantt chart List of Activities









CPM
PATH 1: A+B+C+D+E+F+I+M+N PATH 4: A+B+C+D+E+G+I+K+L+N
8+4+4+8+70+14+60+2+6=176 8+4+4+8+70+8+60+20+4+6 = 192

PATH 2: A+B+C+D+E+F+I+K+L+N PATH 5: A+B+C+D+E+G+H+J+L+N
8+4+4+8+70+14+60+20+4+6 = 19 8+4+4+8+70+8+4+10+4+6 = 126

PATH 3: A+B+C+D+E+G+I+M+N
8+4+4+8+70+8+60+2+6 = 170
The critical path is Path 2 which is composed of 198 days. It consists of A. Planning, B.
Client Searching, C. Information Gathering, and D. Chapter 1, E. Chapter 2, F.
Chapter 3 & 4, I. Programming, K. Chapter 6, 7 & 8, L. Final Drafts of Document, and N.
Final Defense.







Figure No. 5.4 PERT Diagram
A B C D
E
F
G
H
I
J
K
L
M
4
8
4 8
N
7
0
1
4
8
4
6
0
1
0
20
4
2
6
89

0
20000
40000
60000
80000
100000
120000
140000
160000
1 2 3 4 5 6
Payback Analysis
Year Cumulative Costs Cumulative Benefits
5.7 Financial Analysis (CBA)












Figure No. 5.5 Payback Analysis

Orange part is year while yellow is cumulative cost crossing in green
cumulative benefits in between year 3 which means that in this year the
investment of the company on the system is return.








90





























91

Table 5.3 Net Present Value


















92

Recurring Cost




Item Quantity Unit Unit Price Price

Ballpen(Black) 2 packs PHP 54.99 PHP 109.98

Ballpen(Black) 2 packs PHP 54.99 PHP 109.98

Sign Pen 1 packs PHP 79.99 PHP 79.99

Receipt
25 packs PHP 85.99 PHP 2,149.75

Printer Ink (Black) 20 pcs PHP 150.00 PHP 3,000.00

TOTAL PHP 5,449.70


Non - Recurring Cost




Item Quantity Unit Unit Price Price

Computer Unit 1 Set
PHP
10,000.00
PHP 10,000.00

Biometric 1 pc PHP 5,000.00 PHP 5,000.00

TOTAL PHP 15,000.00


Software Cost




Human Resource Rate Day Price

System Analyst 150.00 50 PHP 7,500.00

Programmer 125.00 65 PHP 8,125.00

Database Administrator 100.00 25 PHP 2,500.00

Network Administrator 100.00 25 PHP 2,500.00

TOTAL PHP 20,625.00



Recurring Cost PHP 5,449.70

Non-Recurring Cost PHP 15,000.00

Software Cost PHP 20,625.00

TOTAL PHP 41,074.70



Table 5.4 Cost Analysis for Year 0 of Proposed System








93

Recurring Cost




Item Quantity Unit Unit Price Price

Ballpen(Black) 5 packs PHP 54.99 PHP 274.95

Ballpen(Black) 5 packs PHP 54.99 PHP 274.95

Sign Pen 5 packs PHP 79.99 PHP 399.95

Receipt
25 packs PHP 85.99 PHP 2,149.75

Printer Ink (Black) 20 pcs PHP 150.00 PHP 3,000.00

TOTAL PHP 6,099.60


Software Cost




Human Resource Rate Day Price

Database Administrator 100.00 50 PHP 5,000.00

TOTAL PHP 5,000.00








Recurring Cost PHP 6,099.60

Software Cost PHP 5,000.00


TOTAL
PHP 11,099.60



Table 5.5 Cost Analysis for Year 1 to 4 of Proposed System

















94

Recurring Cost




Item Quantity Unit Unit Price Price

Ballpen(Black) 5 packs PHP 54.99 PHP 274.95

Ballpen(Black) 5 packs PHP 54.99 PHP 274.95

Sign Pen 5 packs PHP 79.99 PHP 399.95

Receipt
25 packs PHP 85.99 PHP 2,149.75

Printer Ink (Black) 20 pcs PHP 150.00 PHP 3,000.00

TOTAL PHP 6,099.60


Non - Recurring Cost




Item Quantity Unit Unit Price Price

Printer 1 pc PHP 3,000.00 PHP 3,000.00



TOTAL PHP 3,000.00


Software Cost




Human Resource Rate Day Price

Database Administrator 100.00 90 PHP 9,000.00

Maintenance 150.00 50 PHP 7,500.00





TOTAL PHP 16,500.00



Recurring Cost PHP 6,099.60

Non-Recurring Cost PHP 3,000.00

Software Cost PHP 16,500.00

TOTAL PHP 25,599.60



Table 5.6 Cost Analysis for Year 5 of Proposed System












95

Recurring Cost




Item Quantity Unit Unit Price Price

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Sign Pen 7 packs PHP 79.99 PHP 559.93

Pencil 12 packs PHP 50.00 PHP 600.00

Pencil Eraser 25 pcs PHP 50.00 PHP 1,250.00

Receipt 25 packs PHP 85.99 PHP 2,149.75

Printer Ink (Black) 20 pcs PHP 150.00 PHP 3,000.00

Liquid Eraser 35 pcs PHP 26.50 PHP 927.50

TOTAL PHP 10,136.88







Non - Recurring Cost




Item Quantity Unit Unit Price Price

Printer 1 pc PHP 7,000.00 PHP 7,000.00

Computer Unit 1 pc
PHP
25,000.00
PHP 25,000.00

TOTAL PHP 32,000.00




Recurring Cost PHP 10,136.88

Non-Recurring Cost PHP 32,000.00

PHP 0.00

TOTAL PHP 42,136.88



Table 5.7 Cost Analysis for Year 0 of Existing System









96

Recurring Cost




Item Quantity Unit Unit Price Price

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Sign Pen 7 packs PHP 79.99 PHP 559.93

Pencil 12 packs PHP 50.00 PHP 600.00

Pencil Eraser 25 pcs PHP 50.00 PHP 1,250.00

Receipt 25 packs PHP 85.99 PHP 2,149.75

Printer Ink (Black) 20 pcs PHP 150.00 PHP 3,000.00

Liquid Eraser 35 pcs PHP 26.50 PHP 927.50

TOTAL PHP 10,136.88







Non - Recurring Cost




Item Quantity Unit Unit Price Price

Continuous Ink 1 pc PHP 3,000.00 PHP 3,000.00

Computer Unit 1 pc
PHP
28,000.00
PHP 28,000.00

TOTAL PHP 31,000.00




Recurring Cost
PHP
10,136.88

Non-Recurring Cost
PHP
31,000.00



TOTAL
PHP
41,136.88



Table 5.8 Cost Analysis for Year 1 of Existing System







97

Recurring Cost




Item Quantity Unit Unit Price Price

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Sign Pen 7 packs PHP 79.99 PHP 559.93

Pencil 12 packs PHP 50.00 PHP 600.00

Pencil Eraser 25 pcs PHP 50.00 PHP 1,250.00

Receipt 25 packs PHP 85.99 PHP 2,149.75

Printer Ink (Black) 20 pcs PHP 150.00 PHP 3,000.00

Liquid Eraser 35 pcs PHP 26.50 PHP 927.50

TOTAL PHP 10,136.88







Non - Recurring Cost




Item Quantity Unit Unit Price Price

Continuous Ink 1 pc PHP 3,000.00 PHP 3,000.00

Computer Unit 1 pc
PHP
27,000.00
PHP 27,000.00

TOTAL PHP 30,000.00




Recurring Cost
PHP
10,136.88

Non-Recurring Cost
PHP
30,000.00


PHP
-

TOTAL
PHP
40,136.88



Table 5.9 Cost Analysis for Year 2 of Existing System






98

Recurring Cost




Item Quantity Unit Unit Price Price

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Sign Pen 7 packs PHP 79.99 PHP 559.93

Pencil 12 packs PHP 50.00 PHP 600.00

Pencil Eraser 25 pcs PHP 50.00 PHP 1,250.00

Receipt 25 packs PHP 85.99 PHP 2,149.75

Printer Ink (Black) 20 pcs PHP 150.00 PHP 3,000.00

Liquid Eraser 35 pcs PHP 26.50 PHP 927.50

TOTAL PHP 10,136.88







Non - Recurring Cost




Item Quantity Unit Unit Price Price

Continuous Ink 1 pc PHP 3,000.00 PHP 3,000.00

Computer Unit 1 pc
PHP
25,000.00
PHP 25,000.00

TOTAL PHP 28,000.00




Recurring Cost 10136.88

Non-Recurring Cost 28000

0

TOTAL 38136.88



Table 5.10 Cost Analysis for Year 3 of Existing System









99

Recurring Cost




Item Quantity Unit Unit Price Price

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Sign Pen 7 packs PHP 79.99 PHP 559.93

Pencil 12 packs PHP 50.00 PHP 600.00

Pencil Eraser 25 pcs PHP 50.00 PHP 1,250.00

Receipt 25 packs PHP 85.99 PHP 2,149.75

Printer Ink (Black) 20 pcs PHP 150.00 PHP 3,000.00

Liquid Eraser 35 pcs PHP 26.50 PHP 927.50

TOTAL PHP 10,136.88







Non - Recurring Cost




Item Quantity Unit Unit Price Price

Continuous Ink 1 pc PHP 3,000.00 PHP 3,000.00

Computer Unit 1 pc
PHP
30,000.00
PHP 30,000.00

RAM
1 pc PHP 1,699.00 PHP 1,699.00

Printer 1 pc PHP 2,999.00 PHP 2,999.00

TOTAL PHP 37,698.00




Recurring Cost PHP 10,136.88

Non-Recurring Cost PHP 37,698.00



TOTAL PHP 47,834.88


Table 5.11 Cost Analysis for Year 4 of Existing System







100

Recurring Cost




Item Quantity Unit Unit Price Price

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Ballpen(Black) 15 packs PHP 54.99 PHP 824.85

Sign Pen 7 packs PHP 79.99 PHP 559.93

Pencil 12 packs PHP 50.00 PHP 600.00

Pencil Eraser 25 pcs PHP 50.00 PHP 1,250.00

Receipt 25 packs PHP 85.99 PHP 2,149.75

Printer Ink (Black) 20 pcs PHP 150.00 PHP 3,000.00

Liquid Eraser 35 pcs PHP 26.50 PHP 927.50

TOTAL PHP 10,136.88







Non - Recurring Cost




Item Quantity Unit Unit Price Price

Continuous Ink 1 pc PHP 3,000.00 PHP 3,000.00

Computer Unit 1 pc
PHP
27,000.00
PHP 27,000.00

RAM
1 pc PHP 1,699.00 PHP 1,699.00

Printer 1 pc PHP 2,999.00 PHP 2,999.00

TOTAL PHP 34,698.00




Recurring Cost PHP 10,136.88

Non-Recurring Cost PHP 34,698.00



TOTAL PHP 44,834.88


Table 5.12 Cost Analysis for Year 5 of Existing System







101

Chapter 6
DESIGN OF THE PROPOSED SYSTEM
6.1 Inputs
Name of document: Customer Data
Prepared by: Customer
Number of copies: 1
Purpose: To provide details in the registration of client.

Name of Document: Program subscription
Prepared By: Customer
Number of copies: 1
Purpose: To provide details in enrolling customer






102

Name of Document: Customer Payment status and details
Prepared by: ARMM Management
Number of copies: 1
Purpose: To provide payment status and details.

Name of Document: User logs Details
Prepared by: Customer
Number of copies: 1
Purpose: To provide time in and time out of the
customer.









103

6.2 Process
6.2.1 Register Customer
BEGIN
IF Customer is not registered in customer data THEN
Obtain Customer data from customer
IF Customer data is valid THEN
Register Customer
IF Customer is registered, not enrolled
and Inactive THEN
Enroll/Renew registered customer in
the program he/she choose.
END IF
The customer must register first before
enrolling in the gym
END IF
The customer must input a correct data
END IF
END

104

6.2.2 Generate Payment Records
BEGIN
IF Customer is now registered and enrolled in the gym
THEN
The payment details store in payment record.
IF Client pay a program fee THEN
The client receive a receipt from administrator
END IF
END IF
END
6.2.3 Generate user logs
BEGIN
IF Customer is now registered, enrolled in the program and
status is active, and a program fee THEN
The Customer can now login or enter in the gym.
END IF
END


105

6.2.4 Produce Reports
BEGIN
GET Program subscription record form program
subscription.
GET Payment records from Payment.
GET User logs records from User Logs.
END
6.3 Files
the proposed system keeps the following files of the ARMM GYM

Name of File: Customer Records
Data needed: Client ID
First name
Middle name
Last name
Fingerprint id
Email
Password

106

Name of File: Program description record
Data needed: Program id
Client id
First Name
Middle Name
Last name
Program description
Program id
Date enrolled

Name of File: Payments records
Data needed: Record id
Client id
First name
Middle name
Last name
Program information
Payment

107

Name of File: User logs
Data needed: Program id
Client id
First name
Middle name
Last name
Program information
Time in
Time out
Enrolled date
6.4 Outputs
Name of Document: Receipt
Prepared By: Administrator
Number of copies: 2
Frequency of distribution: Distributed when you enrolling or renewing the
program in the gym
Purpose: To provide the client id the program of payment for
every transaction made.
Recipient: Customer and Administrator
108


Name of the document: Client reports
Prepared By: Online Gym B-Pass System
Number of copies: Depends on the administrator
Frequency of distribution: Depending to the needs of the clients and
administrator.
Purpose: To have a summary of the client records and to
monitor the clients
Recipient: Customer and Administrator

Name of the document: Payments reports
Prepared By: Online Gym B-Pass System
Number of copies: Depends on the administrator
Frequency of the distribution: Daily, Weekly, and monthly
Purpose: To monitor the income if the gym
Recipient: Administrator



109

Name of the document: Log report
Prepared By: Online Gym B-Pass System
Number of copies: Depends on the needs.
Purpose: To monitor the logs and print it according. To
the chosen client or all the client if needed.
Recipient: Administrator and Customer


















110

CHAPTER 7
IMPLEMENTATION
7.1 Resource Requirements
7.1.1 Software Requirements
Operating System:
Windows 7 or higher version
JRE(Java Runtime environment))
Browser (any kind of browser)
Application:
7.1.2 Hardware Requirements
Processor: Dual Core or higher version
RAM: 1G or Higher
Hard Disk: at least 80 GB
Finger Print Scanner
Monitor
Network: LAN Card
Router
UTP Cable
RJ45 Connector
Keyboard
Mouse
111

7.1.3 Human Resources Requirements
7.1.3.1 The System Analyst
A system analyst investigates, analyses, plans solution, designs,
develops, evaluates, and coordinates to meet the specific requirements
that the system must satisfy. They are not normally involved in the actual
hardware or software development though they may be familiar in
operating system or other programming languages. The system analyst is
responsible for all the tasks on how the system will be developed.
A system analyst must have a broad knowledge technically, and a
logical approach to problem solving. They need to have an ability to
contribute to a team effort, have good interpersonal skills, excellent oral
and written communication skills to interact with people at all levels. A
system analyst also needs to have a degree in Information system,
computer science, business or if non IT-related subjects, a relevant
postgraduate qualification may be useful.
7.1.3.2 The Programmer
A programmer is a person who writes system software. They are
assigned to code programs to create the system, and the overall functions
and performance of the user interface, and its connection to the database
needed.
A programmer should have a background on different forms of
computer coding language such as SQL which is used for database,
112

HTML, PHP, Java and more. They compose instructions for computer
systems to perform a given action.
7.1.3.3 The Trainer
A trainer is the person who guides, coaches, or give knowledge to
another person in a particular subject matter. The main task of the trainer
for using the proposed system is to guide and teach the end user on how
to operate the system. They are the one whos responsible to teach and
educate the user which is the administrator or other personnel that will be
involved in the whole process. The programmer can also serves as the
trainer since they know the flow of the whole system.
A trainer should know how to share their knowledge in the easiest
but understandable way for the user to follow correctly.
7.1.3.4 The User
The users will be the administrator, the customer, the system
programmer, and the database manager. The administrator and the
customer will be the end users, they need to have enough knowledge how
to operate the system and the proponents are going to conduct trainings
so they will be familiar to the system. The system programmer and the
database manager is still considered as users since they are assigned to
fix bugs and update software and hardware that will be used in the
system.

113


7.2 Installation and Testing plans
7.2.1 System Installation
The proposed system is installed upon the approval of the ARMM
GYM officers as they are the ones to give the authorization to use the
system. The system is installed in two computers which are for Human
Resource Head, the Administrator and the Client. A compute will also be
placed in the database of the system. This is scheduled on September 20,
2013.
7.2.3 Conversion Plans
The proponents used the parallel conversion plan. With this kind of
plan, there is ease in comparing both systems. The established solutions
are easily shown as both systems run at the same time. This kind of plan
clarifies if the requirements are met by the new system. From the obtained
results, evaluating the system can be done quickly and efficiently.

7.2.2 Training Plans
The proponents handled just one day for training seminars. The
reason why the training is just for one day is because the Administrator in
the gym, who will access the system, is an I.T. also. So we just have to
teach him about the functionalities.
114

The objective of these training is to give knowledge to the
Administrator who will be handling the system and also give instructions
on how the system may be operated. The proponents find it important to
implement trainings so that the Administrator will be capable to handle the
system appropriately and efficiently. The training involves demonstration
on how the system works, proper handling, troubleshooting, familiarization
in using Microsoft Office Access, how database works, and maintaining
record in the database, time keeping system works and implementing
instructions or rules on how the system will work according to the
guidelines set modules. This training is not only for the two users of the
system but for those employees who handle the Attendance Monitoring.










115

Schedule of training:
Date Activity Participants Facilitator
September 20,
2013
Installation of the
system and
demonstration on
how the system
operates.
Employees of
the Human
Resource Office
and Accounting
Office
Proponents
September 21,
2013
Giving of
guidelines and
instruction on
how the system
will be
implemented
Employees of
the ARMM GYM
Proponents
Table 7.1 Schedule if Training
7.2.4 Testing
The accuracy of the system is put into a test. This proves that the
proposed system has met the requirements established to come up on an
effective attendance monitoring process. System testing is done by the
employees who are the users of system. End users had run a
comprehensive testing on the system to perform designated task. Then,
all the process on the system is checked to determine the dependability of
the system.
116

The proponents tested each module set. To make sure that all the
components of program are working properly. The proponents used a
bottom up approach of integration where all low level modules are tested
first before going up to the next level.

Date Action to be taken
September 23, 2013 The different modules are tested.
September 24, 2013 Modifications in the system are
tested.
Table 7.2 Schedule of Testing
7.3 Maintenance Plan
The system should always be under the care of programmers, system
analysts, database managers, and especially users. The software and hardware
that is applied in the system should maintain the requirements so it will not
malfunction. Maintenance plan will be implemented to identify and arrange all
required elements then repair in an orderly manner.
Users may use the system after the implementation and this will come up
with future support so that it will be uphold by actions.



117

7.3.1 Software
The system software will keep up to date and will be provided
support for bug fixes. The proponents will immediately take action depending
upon the preferred choice of the company to ensure stable function of the
system.
7.3.2 Hardware
Cable, Keyboard, mouse, fingerprint scanner, and wirings will be
replaced when theres unnecessary errors occur. The router should also be
upgraded or replaced when needed to hasten the connection.

















118


Chapter 8
Conclusion and Recommendation

8.1 Conclusion
The proponents gathered all the needed information through planning,
searching of company, conducting interview, and relying on theories that is
related into the subject in the whole process of creating the system. The
proponents created a project proposal that will help the ARMM Gym in
monitoring the attendance of their clients and in keeping the records they need
proficiently. The proposed system of the proponents has met the expectations
and needs of the ARMM Gym. This system drives out the paper works in ARMM
Gym and lessen the tasks of the office manager. It also minimizes the errors in
producing reports that is needed by the owner. To provide well organized data in
ARMM GYM Inc. , Reduce paper works, to fasten the work processes , faster
and accurate release of reports, develop a system that can automatically update
records of customer in one process, Provide security of data , and easily monitor
ARMM Gym Inc. transaction progress .In developing the Online Gym B-Pass
System, it requires a wide understanding and study in the case involving the
problems of the company, specification, and processes of the existing manual
system.
The proposed Online Gym B-Pass System includes processes that are
quite similar to the existing manual system such as (1) checking of records, (2)
119

adding and updating customer records, and (3) producing reports. The only
difference is that everything will be shortcut.
8.2 Recommendation
This part shows some enhancement that can be made by the future
researches who may be interested in making a system with a similar concept.
In the light of the findings, the following recommendations are offered by
the researches:
8.2.1 Increase of the systems ability to detect errors and data recovery. The
system does not have a backup function causing possible data loss in
case of system fault.
8.2.2 Improve system functionalities. It is recommended that the system
should be able to give a more accurate solution to the problems of the
gym.
8.2.3 Improve user interface of the system. It is highly recommended that the
interface would be less complicated for the better understanding of the
user especially for those who are not information technology literate.







120



REFERENCES
Textbooks
P. Tensor, 1995. Smart Card and Biometric time and attendance, visitor
monitoring and access control system
RFID-based Students Attendance Management System from International
Journal of Scientific & Engineering Research Volume 4, Issue 2, February-
2013. ISSN 2229-5518

Consumo, Karen Mae M., Mamangun, Mary Ann M. (2011) AN
EMPLOYEE ATTENDANCE MONITORING SYSTEM WITH PAYROLL
USING BARCODE. A proposal presented to St. Nicolas College of
Business and Technology
2nd floor, MELVI Bldg. Olongapo - Road City of San Fernando,
Pampanga
Online References
Waterfall model from http://en.wikipedia.org/wiki/Waterfall_model
Data flow diagram from http://en.wikipedia.org/wiki/Data_flow_diagram
Database from http://en.wikipedia.org/wiki/Database
Requirement Gathering and Analysis or System Planning from
http://en.wikibooks.org/wiki/Systems_Analysis_and_Design/Introduction#P
lanning
Time Office Biometric and Attendance from
http://www.timeofficesoftware.com
JC Software Development from http://www.download .com/Password-
Administrator
MyKidSecure from http://www.biometricupdate.com/201309/eportation-
launches-biometric-attendance-system-for-schools-uses-fujitsu-tech
Student Attendance Monitoring System (SAMS) from
http://www.ncl.ac.uk/quilt/assets/documents/com-rep-cfltsec-13mar-
docF.pdf
121

Attendance Monitoring System Using Biometrics for Security Staff from
http://www.studymode.com/essays/Attendance-Monitoring-System-Using-
Biometrics-For-732262.html
ActiveX from http://en.wikipedia.org/wiki/ActiveX
Fingerprint SDK from http://www.griaulebiometrics.com/en-
us/fingerprint_sdk
Integrated Automated Fingerprint Identification System (IAFIS) from
http://en.wikipedia.org/wiki/Integrated_Automated_Fingerprint_Identificatio
n_System
BioTime Edu from http://www.m3biometrics.co.uk/BioTimeEDU.aspx
MONIROTING SYSTEM FOR TRANININGS OF THE PHILIPPINE
NATIONAL HOUSING AUTHORITY from
http://essay.utwente.nl/55730/1/Scriptie_Liong.pdf
CSIT Attendance Monitoring System from
http://www.smu.edu.ph/School%20of%20CSIT/scsitnews/93-school-of-
csit-checking-of-attendance-now-computerized

Fingerprint Biometrics from
http://www.heritage.org/research/reports/2004/06/biometric-technologies-
security-legal-and-policy-implications

(2010, 08). Attendance Monitoring System. StudyMode.com. Retrieved
08, 2010, from http://www.studymode.com/essays/Attendance-Monitoring-
System-391932.html

(2011, 01). Attendance Monitoring System. StudyMode.com. Retrieved
01, 2011, from http://www.studymode.com/essays/Attendance-Monitoring-
System-546207.html

(2013)MySQL, techterms.com.
from http://www.techterms.com/definition/mysql

Java Programming from http://www.webopedia.com/TERM/J/Java.html

Student Attendance Tracking System (SATS) from
http://www.astiwz.com/project-synopsis-abstract-documentation-source-
code.php?pid=135&name=Student%20Attendance%20Tracking%20Syste
m.&project-mode=Paid

(Barry Mills:LTA 2007 A1 base 20/6/07 10:16) Attendance Monitoring Pilot
122

Project from http://www.derby.ac.uk/files/barry_mills_-
_attendance_monitoring_pilot_project.pdf