Chapter 3 v2

CHAPTER 3
Methodology
3.1. Overview
Methodology is the process used to develop the system
proposed. To develop a system, we need to follow the steps from
the
method
that
we
choose.
For
this
system,
System
Development Lifecycle (SDLC) has been chosen as the guideline

to develop this system. The method used is Waterfall model as
the steps to develop this system. In this chapter, we will discuss
about the model used to develop this system.
3.2. SDLC
SDLC is a term that used in development process that
describes a process for planning, analysis, designing testing and
deploying for system. In this project, SDLC is used as a guideline
to develop Thesis Storing System (TSS). In development of TSS,
SDLC is used to make sure that the development of the system
will not lost in track. Development process will be more
systematic from planning phase to the implementation phase.
3.3. Waterfall Model

37
Waterfall model is a process used in developing the project in

software development process. The flow of steps that flowing
steadily downwards that makes this method called waterfall.
Starting
with
requirement,
then
continue
on
design,
implementation, integration and system testing and lastly to the

operation and maintenance. This process will continue to
develop until last step. If the error traced, then the step will
repeat to the error and the development will continue until
maintenance phase again and again. That is waterfall model.
Figure 3.3: Waterfall model
38
Table 3.3: Goals, Tasks and Output in Waterfall Model

Phase
Requirement and analysis
Goals, Task and Output

Goals:
To identify the problems that
occurs before developing.

To identify the method suitable
for developing.
To search for the requirement
needed
for
developing
the
system
Tasks:
Define
problem
statements,
objectives, and scope for the
system.
Compare the advantage and
disadvantages
based
on
the
existing system.
Identify tools needed for the
development.
Outputs:
Problem statements, objectives

and scope for the system are
39
carried out.
Literature review as stated in
chapter 2.
System
requirement
specification in identified.
System design
Goals:
To design the system based on
requirement gained.
To determine the appropriate
system
architecture
development.
To design diagrams
for
for
the
system.
Tasks:
Design the system based on

requirement and make sure the
design
is
suitable
implementation
in
next
phase.
Design the architecture for the
system.
Design
diagrams
development phase.
Outputs:
40
the
for
for
Architecture
and
design
diagrams are carried out for

next phase.
Goals:
To implement the design carried
out from previous phase.

To
develop
the
functional
requirement and non-functional
requirement for the system.

To develop system based on the
design carried out.
Tasks:
Implementation
Create the functionality for the
system.
Transfer all the design in the
previous phase to the codes.

Identify the error of the source
codes before proceeding to the
next phase.
Outputs:
System developed.
Error of the source codes is
modified.
41
Goals:
To test the system developed in
previous phase.
To trace bug in the system.
Tasks:
Integrate all units and tested.

Testing
system
by
insert
dummy data as input and the
System testing
outcome for the input.

Repair any error occur during
testing.
Outputs:
Complete
the
development
process.
Goals:
Launching system in practical

use (not necessary)
Maintenance
Tasks: Outputs: -
42
3.4. Benefits of using waterfall model

For each model for development process, there will be
advantages and disadvantages in the development. In this
section, we will discuss about the benefits of using it.
For this model, it is simple and easy to understand
for better use.

It is suitable
development
for
phase
small
project
process
which
has
the
specific
deliverables and a review process.

In this model, phases do not overlap with each other
cause of the phases that completed one at a time.
3.5. Summary
In this chapter, it is stating the method that used to develop
OBE Manager. This OBE Manager use waterfall model in order to
guide the developing of the application.
43

Chapter 3 v2

Uploaded by

Copyright:

Available Formats

Chapter 3 v2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 3 v2

Uploaded by

Copyright:

Available Formats

CHAPTER 3

Development Lifecycle (SDLC) has been chosen as the guideline

3.3. Waterfall Model

Waterfall model is a process used in developing the project in

implementation, integration and system testing and lastly to the

Figure 3.3: Waterfall model

Table 3.3: Goals, Tasks and Output in Waterfall Model

Goals, Task and Output

To identify the problems that

occurs before developing.

objectives, and scope for the

Problem statements, objectives

To design the system based on

Design the system based on

diagrams are carried out for

To implement the design carried

out from previous phase.

requirement for the system.

Create the functionality for the

previous phase to the codes.

To test the system developed in

Integrate all units and tested.

outcome for the input.

Launching system in practical

3.4. Benefits of using waterfall model

For this model, it is simple and easy to understand

for better use.

deliverables and a review process.

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.