CHAPTER III

Method and Procedures

This chapter involves system design details using standard models. It

also covers analysis, research mechanism, surveys and proposed evaluation of
the system.

System Design/Development Life Cycle

The Systems Development Life Cycle (SDLC), or Software Development

Life Cycle in systems engineering and software engineering, is the process of
creating or altering systems, and the models and methodologies that people use to
develop these systems. The concept generally refers to computer or information
systems. In software engineering the SDLC concept underpins many kinds of
software development methodologies. These methodologies form the framework
for the planning and controlling the creation of an information system.

1
The Waterfall Model

2
Project Identification

In the first phase, the proponents identify the problem and analyze the
requirements of the entire study. As they gathered different researches for a more
useful and unique project, they conclude that a website is a good choice for this
study, because on this new era, modern technologies and internet sets as a big
influence to our daily lives. And with that, the proponents end up deciding to build a
website which is focused on offering Gadgets and Accessories online.

Planning

In this given phase, the proponents did several discussion and consultations
on how to pursue their chosen project, from the timeline up to the role of each
team members.

Analysis (commonly known as Requirement Gathering & Analysis)

The goal of systems analysis is to gather and review all the possible
requirements of the system to be developed . This step involves breaking down
the system in different pieces and drawing diagrams to analyze the situation,
analyzing project goals, breaking down what needs to be created and attempting
to engage users so that definite requirements can be defined. Requirements
gathering involve several researches and consultations.

Design

Design phase is basically defining the overall system architecture of the

proposed system. At this stage, design functions and operations are described in
detail. Layouts or commonly known as mock-up designs should be a part of this
phase plus the defined functionalities. Also, this stage associates the rules and
3
process diagrams to fully furnish the ‘bone’ of the system and will be ready for the
development proper.

Debugging (commonly known as Development phase)

At this stage, proponents should make the ‘design’ live into action. Sketches
and layouts should turn as a real system based on the specifications and rules that
they’ve designed. The proponents should start to kick-in their technical abilities and
get their hands dirty on doing such coding process. At this stage, debugging occurs
on numerous times as it is needed or as long as there’s any errors to be acquired.
And opt, before the system implementation, the proponents must assure that the
whole system is working well by doing the last check or so called unit testing.

Implementation

When the program was already check and met all the requirements that are
needed for it, it would now ready for this phase. In implementing a system, the
proponents must explain the whole project on their target users.

Software Maintenance

Software maintenance is the modification of a software product after

delivery to correct faults. It also offers providing enhancements as requested by
the target users and as the modern technology grows.

Methods of Research

Listed below are the research approaches that the proponents tried for the
design phase.

4
Internet Research

The proponents did several research and reviews via internet to gather
significant information that could help them building their proposed system. They
go to different blogs and forums of web developers or analyst who offers good
reviews and tips on how to create a better website and what it should offer to the
target users. From there, they achieved to get some techniques that to implement
to build a more user-friendly website.

Consultation

The proponents’ consults from the people they have seen on Forums and
asked for some questions, clarifications, tips & tricks plus pros/cons of building a
website. On that consultation, the proponents get a deeper understanding on how
important the design phase is.

Interview Questionnaire

Each of the members of the team provides interview questions for the target
users of the system. The idea is to gather comments from the target users from the
manual way of doing gadget shopping up to using the proposed website.

Survey

The proponents will use the said ‘Interview Questionnaire’ on this phase.
This is known as a good technique to gather information and feedbacks from
different people or respondents. Usually, the survey involves the expectations of
target users and their comments on what is being presented.

5
 This will also help the proponents to understand and see how the users
takes the system.

Population, Sample Size and Sample Techniques

The proponents used 100 random target users from their colleagues, known
friends, family members and some experts in web development around Bulacan.

Description of respondents

The respondents of the study are on different age & places in Bulacan.
However, each of the selected respondents are known as technology geeks or a
fan of social Medias and e-commerce sites.

Statistical Treatment of Data

The proponents will use the below formula on getting the survey result.

Formula:
n = N / 1 + N * (0.05)²

Description:
e = acceptable sampling error
N = Population Size
n = Sample Size

95% confidence level and 5% are assumed

6
Arithmetic Mean
On the other hand, for the evaluation of the system, the proponents use
Arithmetic Mean to represent the ratings and feedbacks. The arithmetic mean is
sometimes referred to as the average or simply as the mean.

Formula:
p = (x/n) * 100

Description:
p = percentage
x = given score or ratings
n = total number of respondents

Survey for Software Evaluation

The proponents decided to use survey questionnaires for the software
evaluation for a better understanding of user’s feedback.

Table 1. Survey Question for 100 points

Numerical Scale Descriptive Scale
91% – 100% Excellent
81% – 90% Very Good
71% – 80% Good
61% – 70% Fair
50% –60% Poor