CHAPTER 3

RESEARCH DESIGN AND METHODOLOGY

This chapter contains the research methodology of the study in which the
researchers applied in developing the “SPC Appointment System”.The
researchers adopted the Modified Waterfall Model in developing the System
Development Life Cycle (SDLC). The Agile methods will consist of the following
phases; Requirements Gathering and Analysis phase, Design phase,
Development phase, Testing phase, Evaluation phase and the Deployment
phase.
(See Figure 3.1)

Figure 3.1 Modified Waterfall Model of SDLC

3.1 Requirements Gathering and Analysis Phase

In order to develop the SPC Appointment System, the researchers
gathered information that will be used to determine the problems relating to
Appointment System. The researchers will prepared a letter of intent addressed
to the head of the faculty of Registrar, Cashier and Accounting office of Southern
Philippine College (SPC) to conduct an interview with the personnel of the school
through online. After the request has been granted, the researchers used online
forms to formulate a minimum of (10) item questionnaire. The questionnaire was
given to the school faculty of (3) specific offices which are the Registrar, Cashier
and Accounting for them to answer and help the researchers identify the
problems. Also, the researchers will conduct a phone interview for the data
gathering. Thus, the data that have been gathered from the client was used to
analyze the requirements needed to improve and develop the system.

3.2 Design Phase

Based on the acquired data during the gathering and analysis phase, the
researchers conceptualize the design needed as well as the features and system
functionality for the development of the “SPC Appointment System”.

Conceptual Design Phase:

The conceptual design phase consists of the Context level diagram
(CLD), Data flow diagram (DFD), Use Case Diagram (UCD), and Activity
Diagram that helped the researchers to visualize the system data flow. The
Context Level Diagram illustrates the general overview of the relationship
between the users and the system. The Data Flow Diagram will be utilized to
show the detailed information of each major process and sub-process of the
system. Use case diagram will also be used to identify the interactions of the
users on each functionality of the system. Lastly, the activity diagram will be
used to describe the possible steps of the system's flow, as well as the
possible functionalities of each user module.
 FIGURE 3.2 Context Level Diagram

Figure 3.2 shows the context level diagram of the SPC Appointment
System with entities that play important role in the system’s development
such as the student, registrar, cashier and accounting.
First, the student needs to register by providing valid information
before logging in to the system. After accessing the system, the student can
view the (3) available offices which are the registrar, cashier and accounting
for the students to make an inquiry. After the student make the choice
between the (3) offices, the student will need to add details of its information
to transact and for the staff to find the files so that they can provide the
concerns of the student.
Second, when the student chose the registrar, the registrar will need
the student information, like the name of the student or the ID number, which
is the common information in terms of getting the grades of the student.
 Third, when the student chose the cashier, the cashier will also need
the student information to provide the remaining balance of the student.
Lastly, when the student chose the accounting, this office also need
the basic student information to give the status of the scholarship of the
student or to submit a promissory note.

Database Design Phase:

The database design phase consists of the Logical and Physical
Entity Relationship Diagram (ERD) and the Data Dictionary. The Entity-
Relationship Diagram (ERD) will be shown to determine the relationships of
each entity needed in generating the data. The Logical Entity-Relationship
Diagram will be used in defining the system's data requirements to generate
the reports and entities needed. Also, an actual database design will be used
in the Physical Entity- Relationship Diagram based on the entities and
relationships depicted in the Logical Entity-Relationship Diagram.
Additionally, the data dictionary provides information about the specific data
of the tables, such as names, descriptions and format.

User Interface Design Phase:

The User Interface consists of a High-Fidelity prototype that shows
the actual design with the features and functionalities of each user from the
system.

3.3 Development Phase

In the development of the SPC Appointment system, the researchers
used a three-tier architecture design (See Figure 3.3) since the system would be
a web-based application. Using a three- tier architecture would be flexible as
each layer operates on its base, can be developed concurrently, and can be
updated without affecting other layers. A three-tier architecture design includes a
presentation tier, an application tier, and a database tier that were used for each
user module, such as a buyer, seller, and administrator.
3.4 Testing Phase
After the development phase, the researchers would be going to
conducta usability test to evaluate and measure the system’s functionality and
overall effectiveness. The researchers would used the System Usability Scale
(SUS) (See Appendix C) for the participant to gather information. SUS is used to
assess and identify system usability and is a very simple scale to provide to
participants that evaluate usability and learnability effectively. The system is open
to any necessary adjustments, enhancements, and improvements that was
required after the evaluation.

3.5 Evaluation Phase

After the testing phase, the researchers had conducted a usability test to
assess and gauge the system's overall performance, consistency, and degree of
accuracy. The researchers would used the System Usability Scale (SUS) for the
participant to gather information and evaluate user interaction with the system to
evaluate its performance and responsiveness. SUS is used to assess and
identify system usability and is a very simple scale to provide to participants that
evaluate usability and learnability effectively. The system is open to any
necessary adjustments, enhancements, and improvements that was required
after the evaluation.

3.6 Deployment Phase

In this phase, by following the period of evaluation which is the system
functionality and responsiveness would be asses. The researchers would be
going to deploy the system online for the students of Southern Philippine College
(SPC). The system's deployment would be determined by the head of the
faculties approval, if the head in charge approves the system's use. After fixing
the bugs and errors during the testing phase and completing evaluation by the
clients, the researcher would deploy the Save All SPC Appointment System.