2.0 Methodology of The Study

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 8

2.

0 Methodology of the study


The proponents decided to use the waterfall model as
the method of creating the proposed system. Waterfall
approach was first SDLC model to be used widely in Software
engineering to ensure the success of the project. it is
a sequential design process, used in software development
processes, in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases of
conception,
initiation, analysis, design,construction, testing,production/im
plementation and maintenance.
The Phases of Waterfall Model

The first phase is the Requirements. Its purpose of the requirements phase is
to define what a system should do and the constraints under which it must
operate. This phase starts with gathering the high-level requirements and
refining them according to project goals. These requirements define the
major functions of the intended application or system. Major function

includes critical processes to be managed, including mission critical inputs,


outputs, and reports.
In the first phase, the proponents of the system have come up with DCNAS
(Enrollment System) after summing up all members idea. The proponents
decided to choose the Mary Divine Grace School because the proposed
system will greatly help the said school to further improves their enrollment
system. The proponents conduct an interview to the parents of some
students since they are one who knows how the schools enrollment system
works and theyre also the one who enrolls the kids.
The second phase is the user design. It is continuous interactive process that
allows user to understand, modify, and eventually approve a working model
of the system that meets their needs. During this phase, users interact with
system analysts and develop models and prototype that represent all the
system processes, inputs, and outputs.
In the second phase, the proponents finally interact with the school
administrator. They talks about the system processes, inputs and outputs.
The proponents should be willing to accept all the suggestions of the school
admin to improve the system.
The third phase is the implementation. Is when the end user of your software
is foremost in your mind. During this phase you create the documentation
and tools the customer uses to make informed decisions about how to deploy
your software securely.
In the third, the proponents are creating the system. The end user will be
suggesting some information that is useful in improving the system. It
includes also the design and layout of the system, the transaction that the
system will cover, and even the coding of the system.
The fourth phase is the verification. This is obviously one of the stages of
software testing and involves testing the software against requirements and
use cases. It also includes fixing any defects found as determined by
the software testing life cycle.
In the fourth phase, the proponents will test the system and detect some
major issues that will affect the working capability of the system.
The fifth and final phase is the maintenance. This includes making small
changes in the software to meet the changing requirements of the customer.

It would also include improving on errors that went undetected earlier and
thereby improving on the overall efficiency of the software.
In the last phase, the system is being tested if it will run successfully. If there
is any error or mistake, the proponents will fix it so that it can be used in the
operation.

3.0 Data Gathering Procedures and Output


Interview
An interview is a conversation between two or more people
where questions are asked by the interviewer to elicit facts or statements
from the interviewee.
Gathering information will be helpful to the proponents to finally create
the system. Proponents conduct an interview as they make an enrollment
system for the Mary Divine Grace School. They ask the parents of the
students and administration of the said school.
The following information has been gathered by the means of an
interview

Description of the current system


Personnel
Hardware Set-up
Software Set-up
Problems Encountered
Expectations

Research
It is a systematic investigation and study of materials and sources in
order to establish facts and reach new conclusions.
As way of gathering data, the proponents decided to use the internet
as a means of their sources for information. Using the new technologies like
can greatly help researchers because most of the things today can be easily
found in the internet. The proponent conducted research in the internet by
the aim of using different studies and articles that might help in the
proposed system.

4.0 Documentation of the Current System


Company Background
Description of the Current System
Hardware Set-up
Software Set-up
Personnel
5.0 The Proposed System
System Overview
Some Feature of this System:

Systems Development Life Cycle


In its variant forms, remains one of the oldest and yet still
widely used methods of software development and acquisition
methods in the information technology (IT) arena. It is a
conceptual model used in project management that describes the
stages involve in an information system development project,
from an initial feasibility through the maintenance of the
completed application. It follows a cycle of phases which in the
end will to the development of the system desired.
Requirements
The purpose of the requirements phase is to define what a
system should do and the constraints under which it must
operate. This phase starts with gathering the high-level
requirements and refining them according to project goals. These
requirements define the major functions of the intended
application or system. Major function includes critical processes to
be managed, including mission critical inputs, outputs, and
reports.

Design and Architecture


The design phase starts with approve requirements as its
initial input. Design elements are built for each requirement or
requirements set. Design elements describe the software
functions and features in detail. It usually includes functional
diagrams, screen layouts, business rule, business process
diagrams, and an Entity Relationship Diagram with a full data
dictionary.
Development and Coding
The goal of the coding phase is to translate the design of the
system into code in a given programming language. For a given
design, the aim of this phase is to implement the design in the
best possible Coding
The goal of the coding phase is to translate the design of the
system into code in a given programming language. For a given
design, the aim of this phase is to implement the design in the
best possible Coding
The goal of the coding phase is to translate the design of the
system into code in a given programming language. For a given
design, the aim of this phase is to implement the design in the
best possible Coding
The goal of the coding phase is to translate the design of the
system into code in a given programming language. For a given
design, the aim of this phase is to implement the design in the
best possible Coding
The goal of the coding phase is to translate the design of the
system into code in a given programming language. For a given
design, the aim of this phase is to implement the design in the
best possible manner.
Quality assurance and testing

The testing phase actually

Sources:

https://www.google.com.ph/?
gfe_rd=cr&ei=mVArV87pEYmP8Qf6xaeoBA#q=the+waterfall+mo
del

You might also like