26

METHODOLOGY

This section presents the research design, participants of the study, data gathering

procedure, sampling technique, data analysis, statistical treatment of data and research

instrument.

Research Design

The researchers followed extreme programming (XP) process as software

development methodology in the development of the system. XP is an agile software

development framework that aims to produce higher quality software, and higher quality

of life for the development team. XP is the most specific of the agile frameworks regarding

appropriate engineering practices for software development. The researchers used XP to

make the system more efficient and to meet the client’s satisfaction. Figure 2 shows the

XP diagram. The diagram illustrates the phases under XP.

www.extremeprogramming.com

Figure 2. Extreme programming diagram

 27

Planning. In this phase, data gathering took place, the researchers conduct an interview

with the principal of Western Colleges and Cavite State University Maragondon about the

system to be created. The researchers also sought information about the selected students

who will be going to test the system.

Design. The researchers designed the system structure through the following: use case

diagram, data flow diagram (DFD), entity relationship diagram (ERD) and data dictionary.

Figure 3 shows the capability of the users on how they can access the system. Manage

Accounts can be access by the Principal, Registrar, Teacher and Admin. Manage Student

Information can be access by the Principal, Registrar and Admin. Checking or viewing

Attendance can be access by the Principal, Teacher and Admin. Manage Student Rules can

be access by the Principal and Admin. Generate reports can be access by the Teacher,

Registrar and Admin. Post Announcement can be access by the Principal, Registrar and

Admin. Students can mark their attendance and parents will receive SMS notification.
 28

Figure 3. Use Case Diagram

 29

Figure 4. Context Flow Diagram

Figure 4 shows the context flow diagram of the system. It identifies the flows of
information between the user and the system. The user should have an account to access
the system.
 30

Figure 5. DFD

Figure 5 shows the DFD of the system. It shows the information about the inputs and

outputs from the system. (See Appendix 3 for DFD of the system)

Figure 6. ERD

Figure 6 shows the ERD of the system. It shows the entities of the system and their

relation to each other.

 31

Table 1. Data dictionary for tblUser.

Field Name Data Type Field Size Description Example

Id Int 10 Unique Id for all 0000000001

user.

First name Varchar 50 First Name of Reina Arenal

the user.

Last name Varchar 50 Last name the Reina

user.

Username Varchar 50 Username for all Reina123

the user

Password Varchar 50 Password of the *********

user

Position Varchar 50 Position of the Admin

account owner

Table 1 shows the tblUser. tblUser has seven fields, ID, First name, Last name,

username, password and position. ID which has 10 field sizes, its data type is Int and its

description is unique ID for all users. First Name which has 50 field sizes, its data type is

Varchar and its description is the name of the user to be inputted. Last Name which has 50

field sizes, its data type is Varchar and its description is the last name of the user. Username

which has 50 field sizes, its data type is Varchar and its description is the username for all

users. Password which has 50 field sizes, its data type is Varchar and its description is the
 32

password for all the users. Position which has 50 field sizes, its data type is Varchar and its

description is the position of the account owner.

Coding. The coding phase started after designing the system. The researchers used

C# for developing and creating the required source code for the software. The detailed and

specific documents transformed into an actual system. The ERD shows the relationship of

each entity or data of the system.

Test. After the design and coding, the researchers will conduct testing and will

perform all the activities required in the study. The system will be tested in three different

schools and will check if it is functioning correctly. The testing is implemented to detect

errors and to determine if the software is active and to make sure that the program runs

successfully. The alpha testing will be conducted in Cavite State University Naic Campus.

And the system will be tested one week in public school and one week in private school.

Releasing. The releasing phase will be process by the faculty of Information

Technology Department through their transfer program.

Participants of the study

The study will be subjected to performance evaluation. The system will be

evaluated by ten IT Experts, forty students from two different schools and ten school

officials. Table 2 shows the breakdown of the participants that will help evaluating the

system.
 33

Table 2. Breakdown of Participants

PARTICIPANTS NUMBER OF PARTICIPANTS

Students 40 (20 per School)

IT Experts 10

School Officials 10 (5 per School)

TOTAL 60

Data Gathering Procedure

The evaluation process will be performed through cluster based categories of

evaluators which includes Students and School Officials from Cavite State University

Maragondon and Western Colleges and IT Instructors of Cavite State University Naic-

Campus.

The first step in evaluating the system will be the explanation of the specific

objectives. Followed by demonstrating and presenting of the system in the participants.

Each participants are given the chance to explore and use the system demonstrated by the

researcher. One personal computer will be used and a projector. Lastly, the researchers will

distribute the evaluation forms to the participants to rate the system according to its

performance.

Sampling Technique

The researcher will use purposive sampling technique in choosing the participants.

This technique is also known as judgmental, selective, or subjective sampling, very useful
 34

in situations when you need to reach a targeted sample quickly, and where sampling for

proportionality is not the main concern ( Foley B., March 2018).

Data Analysis

Table 3 shows the rating scale that will use in the evaluation of the system. The

corresponding interpretations will use in analyzing the result of the criteria.

Table 3. Likert Scale

RATINGS INTERPRETATION

4.51-5.00 Excellent

3.51-4.50 Very Satisfactory

2.51-.3.50 Satisfactory

1.51-2.50 Fair
1.00-1.50 Poor

Statistical Treatment of Data

The following statistical procedures will be used to analyse the data that will be

gathered from software evaluation questionnaire. Mean is use to present the general

preparation of the participants on the following using the formula below. Standard

deviation is use to tell how measurements for a group are spread out from the mean.

Mean

Ʃ ni =1x i
x
= 𝑛
where
 35

x̅ = mean
n = total number of participants
Ʃ𝑖 𝑋 𝑖 = summation of participants

Standard Deviation

where

Ơ = standard deviation

xi = each value of dataset

x̅ = arithmetic mean

N = the total number of data points

Ʃ(𝐱𝐢 − 𝒙̅ )² = The sum of (𝐱𝐢 − 𝒙̅ )² for all data points

Research Instrument

The evaluation form which was the primary instrument in gathering data will be

used in this study. The evaluation forms to be use is the ITD Software Evaluation

Instrument which was based on ISO 9126 (See Appendix 6 for the sample evaluation

instrument).