CHAPTER 3

TECHNICAL BACKGROUND

This chapter focuses on the type of research approach, software development

cycle, requirements analysis, sources of data, system requirements, and tools for data

analysis.

Research Approach

Software Development Life Cycle (SDLC) is a process used by the software

industry to design, develop and test high quality software’s. The SDLC aims to produce

a high-quality software that meets or exceeds customer expectations, reaches

completion within times and cost estimates.

SDLC is a process followed for a software project, within a software organization.

It consists of a detailed plan describing how to develop, maintain, replace and alter or

enhance specific software. The life cycle defines a methodology for improving the

quality of software and the overall development process.

There are various software development life cycle models defined and designed

which are followed during the software development process. These models are also

referred as Software Development Process Models. Each process model follows a Series

of steps unique to its type to ensure success in the process of software development.
 Methods and Procedure 33

Software Development Methodology

The researchers chose RAD (Rapid Application Development) Model for it focuses

on building the application in a short period of time and the developers can plan their

work precisely. Rapid application development is a software development methodology

that uses minimal planning in favor of rapid prototyping. A prototype is a working

model that is functionally equivalent to a component of the product.

The RAD model focuses on iterative and incremental delivery of working models

to the customer. This results in rapid delivery to the customer and customer

involvement during the complete development cycle of product reducing the risk of

non-conformance with the actual user requirements. In the RAD model, the functional

modules are developed in parallel as prototypes and are integrated to make the

complete product for faster product delivery. Since there is no detailed preplanning, it

makes it easier to incorporate the changes within the development process.

RAD projects follow iterative and incremental model and have small teams

comprising of developers, domain experts, customer representatives and other IT

resources working progressively on their component or prototype. The most important

aspect for this model to be successful is to make sure that the prototypes developed

are reusable. According to James Martin, "Rapid Application Development (RAD) is

development lifecycle to give much faster development and higher-quality results than

those achieved with the traditional lifecycle".

 Methods and Procedure 34

“By utilizing a rapid application development method, designers and developers can

aggressively utilize knowledge and discoveries gleaned during the development process,

itself to shape the design and or alter the software direction entirely." (Andrew Powell-

Morse, 2016) Getting started with rapid application development generally follows a

cyclical process that includes four basic steps:

Figure 3.1 Rapid Application Development (RAD)

 Methods and Procedure 35

Requirement Analysis

Planning Requirements.

The objectives of the planning requirement phase are to establish a general

understanding of the problems that surround its development and eventual operation;

to become familiar with existing systems and; to identify the processes that will be

supported by the proposed application. During this stage, an outline of the system area

and definition of the system scope are developed. This defines the functions, goals,

expectations and data subject areas that the system will support and determines the

system’s scope.

In this phase, the researchers conducted a survey, questionnaire and interview

to the students and teachers to gather more information on what the system should do

and what the system most likely in what the procedures we should do. In this case, the

developers can easily develop and define the requirements needed for the Web based

enrollment system for San Felipe National High School.

User Design. Once the information needed is scoped out, it’s time to jump right into

development, building out the user design through various prototype iterations.

The objectives of the User design phase are to analyze in detail the activities

associated with the proposed system area; to analyze in detail the data associated with

the proposed system area; to develop the system structure in terms of the automated

and manual functions that will comprise the system; to develop proposed screen

layouts for the most important automated functions; to select the appropriate
 Methods and Procedure 36

construction approach for the system and; to prepare a work plan defining the steps

necessary for transition of the system, the effort required to perform these steps, and a

schedule by which these steps can be completed. The UD stage produces a detailed

system area model, an outline system design, and an implementation plan.

Rapid Construction. The objectives of the Construction phase are to complete the

detailed design of the proposed system; to create and test the software that

implements the proposed system; to generate a system that operates at an acceptable

level of performance; to prepare documentation necessary to operate the proposed

application; to design, develop, and test the required transition software and; to

perform the steps necessary to prepare for the conversion of the system to production

status. The design of the proposed system, initially described in the User design phase,

is completed in the construction phase, and application software to implement that

designed is developed and tested. Activities to prepare for the transition of the system

to production status are also performed. This takes the prototypes and beta systems

from the design phase and converts them into the working model.

Cutover. The objectives of the Cutover phase are to install the system in production

operation with minimal disruption of normal business activity; to maximize the

effectiveness of the system in supporting the intended business activities and; to

identify potential future enhancement. The system developed in the RC stage becomes

operational in the cutover phase. At this time, the developers prepare existing data for

the new system and train users to operate the new application. They also provide
 Methods and Procedure 37

support to resolve any problems that arise immediately after the application becomes

operational.

Sources of Data

The collected data and information from San Felipe National High School Unit

using different data collections are the researcher’s primary source of data. Zikmund

(2003) describes primary data as data gathered for the central purpose of a study.

Collecting primary data helped to enhance the researcher’s understanding and

implementation of direct evaluation of the study using a survey questionnaire and an

interview guide. For the purpose of this study.

The researchers while utilize two survey- questionnaire to be answered by the

following respondents for SFNHS.

Title/Position Frequency Total

Student 90 90%
Teacher 10 10%
Total 100 100%

Table 3.1 Respondents of the study

Survey Questionnaire
 Methods and Procedure 38

Survey questions were utilized by researchers to create a Web-based Enrolment

System for teachers and students. A questionnaire is a series of questions that a

researchers ask an individual. A survey, on the other hand, is the process of collecting,

analyzing, and interpreting data from a large number of individuals.

Questionnaire Answer Frequency Percentage

1. The Web- Based 5.Very Strongly Agree 74 74%

Enrolment system has a 4.Strongly Agree 22 22%

user- friendly interface 3.Agree 4 4%

2.Strongly Disagree 0 0%

1.Disagree 0 0%
2. The system is easy to use 5.Very Strongly Agree 70 70%

4.Strongly Agree 28 28%

3.Agree 2 2%

2.Strongly Disagree 0 0%

1.Disagree 0 0%
3. The Web- based 5.Very Strongly Agree 72 72%

enrolment system can create 4.Strongly Agree 22 22%

student profile fields 3.Agree 6 6%

including demographic data. 2.Strongly Disagree 0 0%

1.Disagree 0 0%
4. Information are organized 5.Very Strongly Agree 67 67%

and well presented 4.Strongly Agree 30 30%

3.Agree 3 3%
 Methods and Procedure 39

2.Strongly Disagree 0 0%

1.Disagree 0 0%
5. The system shows Master 5.Very Strongly Agree 76 76%

list of enrolled students 4.Strongly Agree 20 20%

3.Agree 4 4%

2.Strongly Disagree 0 0%

1.Disagree 0 0%
6. Enrollment System enroll 5.Very Strongly Agree 73 73%

new students efficiently 4.Strongly Agree 23 23%

3.Agree 3 3%

2.Strongly Disagree 1 1%

1.Disagree 0 0%
7. The system can input and 5.Very Strongly Agree 79 79%

display grades 4.Strongly Agree 19 19%

3.Agree 2 2%

2.Strongly Disagree 0 0%

1.Disagree 0 0%
8. The system can generate 5.Very Strongly Agree 67 67%

report quickly 4.Strongly Agree 28 28%

3.Agree 4 4%

2.Strongly Disagree 1 1%

1.Disagree 0 0%
9. Students can print their 5.Very Strongly Agree 78 78%

grades 4.Strongly Agree 20 20%

 Methods and Procedure 40

3.Agree 2 2%

2.Strongly Disagree 0 0%

1.Disagree 0 0%
10. system can display the 5.Very Strongly Agree 68 68%

subjects and schedules of the 4.Strongly Agree 31 31%

students after registering
3.Agree 1 1%

2.Strongly Disagree 0 0%

1.Disagree 0 0%
11. The system instantly 5.Very Strongly Agree 71 71%

responds the command from 4.Strongly Agree 26 26%

user
3.Agree 3 3%

2.Strongly Disagree 0 0%

1.Disagree 0 0%
12. The system can process 5.Very Strongly Agree 79 79%
transaction quickly 4.Strongly Agree 17 17%

3.Agree 4 4%

2.Strongly Disagree 0 0%

1.Disagree 0 0%

Table 3.2 Online survey for teachers & students at SFNHS

System Requirements
 Methods and Procedure 41

In this section presents the over all software and hardware requirements of the

Web based enrollment system of San Felipe National High School.

Software Requirements

Development Tools a programming tool or software development tool is a

computer program that software developers use to create, debug, maintain, or

otherwise support other programs and applications. The term usually refers to relatively

simple programs, that can be combined to accomplish a task, much as one might use

multiple hands to fix a physical object. The most basic tools are a source code editor

and a compiler or interpreter, which are used ubiquitously and continuously. Other tools

are used more or less depending on the language, development methodology, and

individual engineer, often used for a discrete task, like a debugger or profiler. Tools

may be discrete programs, executed separately – often from the command line – or

may be parts of a single large program, called an integrated development environment

(IDE). In many cases, particularly for simpler use, simple ad hoc techniques are used

instead of a tool, such as print debugging instead of using a debugger, manual timing

(of overall program or section of code) instead of a profiler, or tracking bugs in a text

file or spreadsheet instead of a bug tracking system.

CPU architecture 32 bit, 64 bit

Supporting Operating System Windows 7, 8, 10
 Methods and Procedure 42

Database Mysql
Local Server Xampp

Table 3.3 Software requirements in the Web based Enrollment System of SFNHS.

Hardware Requirements

This Recommendation lists minimum requirements that allow Users for network

connectivity and other basic functions for processing data, record keeping, and in Web

based enrollment system.

Hard Disk Drive Minimum of 20 GB or more

RAM Minimum of 2 GB
Processor Intel Core i3 (sixth generation or newer)
Monitor 13-inch or 15-inch LCD monitor
Keyboard Standard Keyboard
Mouse Standard Mouse
Ethernet Connection (LAN) OR a wireless adapter (Wi-Fi)
Printer Standard Printer

Table 3.4 Hardware requirements in the Web based Enrollment System of SFNHS.

Roles of Users / User Levels

Role User Level

Student 2
Teacher 3
 Methods and Procedure 43

Administrator 1

Table 3.5 Roles of Users and User Level in the Web based Enrollment System of

SFNHS.

Tools for Data Analysis

This section depicts the data analysis used by the researchers to analyze data col

lected.

Entity Relation Diagram (ERD) is a sort of flowchart that shows how to process

of the enrollment system, and research, ERD are most commonly used to build or

debug relational databases. This Web-based Enrollment system database was made

based on student enrolling requirements. The system can encode enrollees’

information. The registrar admin can have access to the enrollees’ status and

information for important transaction. They can handle the data needed in managing

enrollment and enrollees information as well as the transactions made. The features

included in the system ER diagram were the security and monitoring of the enrollees

transactions and enrollment status. These features were also listed and recorded in

reports that served as the history of transactions done in the system.

Methods and Procedure 44
 Methods and Procedure 45

Figure 3.2 Entity Relationship Diagram (ERD) in the Web based Enrollment

System of SFNHS