Chapter-3 Class Scheduling
Chapter-3 Class Scheduling
DEVELOPMENTAL RESEARCH
This chapter describes and discusses how the proponents gathered the
necessary data and information used in the entire study. It describes who would
be the respondents . This also shows the research method used, statistical
treatment data, population and sample size, sampling technique used,
respondents of the study, procedure of data collection and instruments used, and
used software developmental tool.
Figure 4: The 6-Phase Design and Development Research Approach (Peffers et al,
(2007) expanded on Nunamaker et al. (1991) and Hevner et al. (2004)
Steps in Design and Development of Class Scheduling tool for PHCM
1. Identify the problem
The proponents identified the problem by starting with the current issue in the
Perpetual Help College of Manila and recent problem-solution to how blind can read
bibles and make an easy way for blind persons.
The Proponents Research on different studies addressing the reading of the blind
citizens was studied and considered. After the review of related literature, the
proponent decided to develop a Class Scheduling tool for Perpetual Help College of
Manila: A Web Application and Mobile Application
2. Describe the objectives
The proponents formulated the general and specific objectives by starting to know
the existing structure of the scheduling of Perpetual Help College manila
The proponents also studied different mobile and web programming language and
other platforms to develop the Class Scheduling tool for Perpetual Help College of
Manila: A Web Application and Mobile Application.
3. Design & Develop the artifact
These phase included three factors. Building a conceptual framework, designing the
system architecture and building a prototype for testing and evaluation(hevner, 2004,
Nunamaker et al, 1991).
The proponent created the conceptual framework using Input Process and Output
(IPO) diagram. Different diagrams are created to support the system architecture
presented by the proponents. A hierarchical chart was created by the proponents to
show the program flow of the mobile application.
4. Test the Artifact
In this phase, the proponents used black box testing to check the functionalities and
requirements established during design and development phases.
5. Evaluate Testing results
The proponents evaluated the Class Scheduling tool for Perpetual Help College of
Manila: A Web Application and Mobile Application level of acceptance based from
ISO 9126 (International Standards Organization)
6. Communicate the testing results
In this phase, the proponents derived its results and conclusions from the interpreted
data and previous studies related to the proposed Mobile application
PROJECT DEVELOPMENT
Gantt Chart of Activities
Statistical Tools
The statistical description and analysis of data were treated using the
following formula:
A. For finding the weighted mean, the researchers used the formula below,
where:
WM = weighted mean
f = frequency
N = total population
Sampling Technique
The proponents used the simple random sampling technique in gathering the
respondents. The simple random sampling technique is a subset of individuals chosen
from a large set of population. Each individual is chosen randomly and entirely by chance,
such that each individual has the same probability of being chosen at any stage during
the sampling process. In this technique, each member of the population has an equal
chance of being selected as subject. The entire process of sampling is done in a single
step with each subject selected independently of the other members of the population.
The proponents collected a simple random sample where each unit of the target
population is assigned a number. A set of random numbers is then generated and the
units having those numbers are included in the sample.
Likert’s Scale – The Likert’s Scale was used to interpret items in the questionnaires.
These responses were based on the respondents. This scale will help the proponents to
get an accurate result on the scores given by the respondents during the survey. Likert
scales (named after their creator, American social scientist Rensis Likert) are quite
popular because they are one of the most reliable ways to measure opinions, perceptions,
and behaviors.
Compared to binary questions, which give you only two answer options, Likert-type
questions will get you more granular feedback about whether your product was just “good
enough” or (hopefully) “excellent.” They can help decide whether a recent company outing
left employees feeling “very satisfied,” “somewhat dissatisfied,” or maybe just neutral.This
method will let you uncover degrees of opinion that could make a real difference in
understanding the feedback you’re getting. And it can also pinpoint the areas where you
might want to improve your service or product.
The proponents used the Likert’s Scale to interpret items in the questionnaires.
These responses were based on the respondents. This scale will help the proponents to
get an accurate result on the scores given by the respondents during the survey. The
scale will have 5 ranks or ratings where in 5 is the highest and 1 is considered to be the
lowest rating a respondent could give the proposed project. The range and interpretation
of the five point scale are shown in the tables.
The needed data for this study was collected from surveys from people and People
that uses the old Scheduling System of Perpetual Help College of Manila. The proposed
system entitled “Class Scheduling Tool” is all about necessary information with regard to
Class Scheduling for Perpetual help College of Manila. The proponents also had an
interview from the Perpetual Help College of Manila which it discussed about the current
state of Class Scheduling of how to avoid the conflict of schedule. We asked other
information in regards of this study as an addition through gathering data. The proposed
system entitled “Class Scheduling Tool for Perpetual Help College of Manila: A Web
Application and Mobile Application” is all about necessary information with regards to
Class Scheduling on Web Application with A Mobile Application.
The proponents went to Perpetual Help College of Manila and seek permission to
conduct a study, survey and interview. As proof, the proponents presented the request
letter addressed to the Over All Coordinator and Director of the Perpetual help College of
Manila, Dr. Rosalina R. Pangilinan. Upon approval, the proponents proceeded to the
Perpetual Help College of Manila Office of the Director where Dr. Pangilinan’s Office is
located. Upon arrival, the School Director’s Assistant welcomed the proponents and said
that Mrs. Corazon B. Salvador is around and available and willing to entertain interviews.
The proponents proceeded to The School Director, Dr. Pangilinan. Upon interview, the
proponents presented the study, demonstrated how the system works and explained the
significance of the study. Once the interview was done, School Director, Dr. Pangilinan
approved the proponents’ study and gave some advice, tips, and knowledge as an
improvement of the proponents’ study. The proponents also asked permission to perform
a survey to deans of Perpetual Help College of Manila. Upon approval, the proponents
distributed the survey questionnaires to deans of Perpetual Help College of Manila. The
survey questionnaires were answerable based on ISO 9126 in terms of functionality,
reliability, usability, maintainability, and portability in regards of using a mobile phone in
Class Scheduling tool. Questionnaires were retrieved together with their answers within
the same day.
Design Phase – In this second phase, included three factors naming Building a
conceptual framework, Designing the system architecture and lastly, Building a prototype
for testing and evaluation. The proponents created the conceptual framework using the
(IPO) or the Input, Output, and Process Diagram which it can be seen at figure 2. The
proponents created a System Architecture to show the program flow of the mobile
application which it can be seen at figure 8. The proponents studied the specifications
from the first phase and prepared the system design. The components of this phase also
include decisions about information architecture and applied technologies such as
programming languages, class libraries, and program sequences. The result of the
program design is usually recorded in diagrams describing the theoretical behavior of the
software. The proponents specified what will be the technical design requirements, such
as programming language, data layers, database file structure and defining the overall
system architecture.
The proponents created a System Architecture and used to help people
understand or simulate the system model represents which it gives a bird-eye view of the
system. The System Architecture is the conceptual model that defines the structure,
behavior, and more views of a system. A system architecture description is a formal
description and representation of a system, organized in a way that supports reasoning
about the structures and behaviors of the system.
Testing Phase – With the coding of the application is complete, in this fourth phase
the testing of the written code now comes into scene. The proponents tested if there are
any flaws in the designed application. The proponents tested the developed application
to check the functionalities and requirements established during the design and
development phase and to see if there are any bugs and errors that needs to be fix or to
change in the application. Software testing is a process of executing a program or
application with the intent of finding the software bugs. It can also be stated as the process
of validating and verifying that the application meets the scope and technical
requirements that guided in its design and development
Maintenance Phase – Once the developed application is done, it is now ready for
deployment to live in the client environment but there are some issues and problems that
usually come up. In which this issues need to be solve and requires enhancement in the
application; hence this never ending fifth and last phase referred as maintenance.
Software maintenance is the modification of a software product after delivery to correct
faults, to improve performance or other attributes. A common perception of maintenance
is that it merely involves fixing defects.