5.

3 Tools and Techniques

Tools
Microsoft Visual Studio 2010

Purpose

Microsoft Word

Microsoft Excel

Techniques

Create and design the webpage

for the user.
User able to access to own
account and do what they want to.
Make it easy for user to view and
refer more information from the
webpage.
Report that support why do the
new system needed.
More information and description
about the overall of designing the
system.
Create the Gantt chart for the
work done.

Purpose

Prototyping

Create system page such as,

home page, more information
page and the help page.

JAD

Visual Studio suit this JAD

methodology, this methodology
system originally used for
designing a computer based
system.
Faster development, improve
quality and minimize the error at
the same time.

/
/

5.1 Methodology Comparison

Spiral Lifecycle Model (CHIA CHEE KENG)

The spiral model combines the idea of iterative development with the
systematic, controlled aspects of the waterfall model. Spiral model is a
combination of iterative development process model and sequential linear
development model like waterfall model with very high emphasis on risk
analysis. It allows for incremental releases of the product, or incremental

1 | Page

refinement through iteration around the spiral.

2 | Page

Summary Table of Methodologies

Waterfall

Spiral Model

RAD

Project size

Large Scale

Medium to Large

Small

Project cost

Almost estimated

Expensive

Low

Speed

Slow

Normal

Speed

Flexibility

Rigid

Flexible

Flexible

Well documented

Yes

Normal

Minimized

Arrangement of task

Easy

Complex

Easy

Schedule

Stage by stage

Overall

Short

Risk

High risk

Low

Medium

Table 1: Comparison Table

After compared in my point of views, decision use for e-bookstore Spiral Model is
better use to in development process. Even if, Waterfall Model and RAD Model
both are good model. These are the reasons why I prefer Spiral Model on
Comparing of Methodology:

3 | Page

Comparing of Methodology
Project size

Spiral Model is better to be use in medium to large and even high-risk

project compare to Waterfall good in large size of project and RAD to be
use for small size of project only. Since e-bookstore considered is a
medium size project only.

Project Cost

Project cost for Waterfall and RAD model are much better than Spiral
model, but have to understand that if good methodology is worthy to pay
for the value.

Speed

Spiral model is medium speed because it able fast processing and

completely done in analysis, refine phase and meet the users
requirement.

Flexibility

Changing requirements can be accommodated by Spiral and

RAD. Spiral lifecycle model is allows for elements of the product
to be added in when they become available or known. This
assures that there is no conflict with previous requirements and
design.

Well-Documented

Spiral lifecycle model is normal on this point able to provide enough

documents reviews for developers compare to Waterfall, which have well
documented as have good documents review by developers and RAD not
really well on this.

4 | Page

Arrangement of task

With Spiral lifecycle model arrangement for task is complex compare to

Waterfall easy to arranging tasks can work detailed in every stage but slow
and RAD is easy arranging of tasks but not details enough on stages.

Schedule

Spiral lifecycle model is repeatedly phases in iterations compare to

Waterfall stage by stage and RAD model distributes the phases into a
series of short, iterative development cycles.

Risk

Spiral lifecycle model is the lowest risk between waterfall and RAD model
due to the methodology is a risk-driven project able to minimal risk of
project from every aspects of project.

5 | Page

5.2 Spiral Lifecycle Model

5.2.1 Purpose
Spiral Model is very widely used in the software industry as it is in synch with the
natural development process of any product as learning with maturity and also
involves minimum risk for the customer as well as the development firms.
Following are the purposes of Spiral model:

Risk evaluation is important and budget constraint

o In a project time frame sometimes might be take longer as unexpected
event occur. This case might drive to over budget problem to customer
who thought of budget in range of planning.
o Since APU is a university definitely will faces budget constraint in the
end if the project take longer time in unexpected.

Significant changes are expected in the product during the development cycle
o Spiral model allow customer who uncertain their requirements to make
changes in development cycles.
o However, APU is first steps in e-bookstore might not sure about the
requirements and keep changes after done a module.

Requirements are complex and need evaluation to get clarity and reduce risk
of project
o One of the main reasons Spiral Model to be used in development
process able to clarify of project and minimal risk of the project to
guarantee the project success by evaluation the project.
o By the methodology, able to provide higher rate of success in project.
Thus, APU not to waste times and costs on the project to build a new
project.

6 | Page

5.2.2 Structure of Spiral Lifecycle Model

The Spiral Model has four phases, which relatedly passes through these phases in
iterations in a project:

7 | Page

Identification
o Firstly, this phase start with questionnaire, interview and document
review in baseline of Spiral model. Questionnaire will be distributing
survey form to current user and public users understand what type
of system would user prefer. For interview, programmer will go and
interview customer with recording video to take deeper of customer
needs. For document review, will do review on current document as
report to clarify what user needs. Questionnaire, interview and
document review will do in every subsequent phase of module and
continuous running between customers until end of spiral will
deploy in identified market to test requirements of system.

Design
o This phase starts with basic prototype design with in the baseline
spiral like blueprint of the design by continuous communicated with
customer until confirmed the requirement. Once customer
confirmed the prototype design will do advance design and final
design, for example architecture design, logical design of module,
physical product design and final design in the subsequent spirals.

Construct or Build
o This phase refers to final design of modules at every spiral. In the
baseline spiral when the product is just though of and the design is
being developed a Proof of Concept is developed in this phase to
get customer feedback continuous until meet theirs requirement
and build the details model that highly clarity on requirement
module by module.

Evaluation and Risk Analysis

o After done a module will do risk analysis includes identifying,
estimating, and monitoring technical feasibility and management
risks, such as schedule slippage and cost overrun. After testing the
build, at the end of first iteration, customer evaluates the software
and provides feedbacks.

8 | Page

5.2.3 Scope of Spiral Lifecycle Model

Spiral Model will use for development of website link with database after
considered about project requirement. To build a stable and low risk website in
order to fulfill customer need.

5.2.4 Reasons of Choosing Spiral Lifecycle Model

Changing requirements can be accommodated

o

Requirements can be captured more accurately

o

Customer wont know what their needs in early of process by changing

of requirements; programmer able can meet the customer need.

Better risk management

o

Customer able to change the module during development process

unlike waterfall model after completed the phase cant do any changes
on it.

Development can be divided into smaller parts and more risky parts
can develop earlier to reduce risk of project.

User can see system early

o Basic functions and prototype of system will be present to user in early
stage for confirmation of project requirements.

Allows extensive use of prototype

o

9 | Page

Customer by looking on prototype able to know clearly what their need

and feedback on it.

5.1.2 Waterfall Model (FONG WAI YIP)

The waterfall model is known as a design process refer to the sequential SDLC
model which used in software development processes, in which progress is seen
as flowing downwards (like a waterfall) through the phases of Conception,
Initiation which is mean by planning, continue by analysis, design, testing,
implementation and maintenance. All of these phase should be completed then
only the rest of the phase will go on. If one of the phases went wrong, the phase
will go back to the previous phases. Below figure show Waterfall model diagram :

Figure 2 : Waterfall Diagram

5.1.3 Recommendations
After the comparison between the three of methodology which stated on the
above of comparison table, I recommend the waterfall model to be used as a
methodology in the development of this e-bookstore system. There are the few of
the reason why my decision is make to this waterfall model after looking at the
few of the components that stated on the table comparison. Since, the waterfall
model are still the save here, the well documented which can gather the more
information, therefore, the task will be easy to arrange and furthermore this
model will follow the stage to stage until the previous is done then only the next
stage will begin. So, for this waterfall model it could not have any problem when
any stage goes wrong, there are possible to go back to the previous stage when
needed.
5.2 Waterfall Model
The waterfall model is known as a design process refer to the sequential SDLC
model which used in software development processes, in which progress is seen
as flowing downwards (like a waterfall) through the phases of Conception,
Initiation which is mean by planning, continue by analysis, design, testing,
implementation and maintenance. All of these phase should be completed then

10 | P a g e

only the rest of the phase will go on. If one of the phases went wrong, the phase
will go back to the previous phases.

11 | P a g e

5.2.1 Purpose of choosing Waterfall model

In order to make the development of e-bookstore system to become a successful
system, waterfall model seem to be a suitable model to achieve the goal and
become a successful system;

Able to focus and meet the requirements for the customer. Since, before
come out with a system, based on the waterfall model, the first stage shall
be start on planning part, which the gathering of information will be go
first, to understand the customer and get to know what the customer
actually need and want, therefore, from the stage of planning would be
easy to focus and understand better before continue with the analysis
stage.
Reduce the chance of getting error. From this part which mean by reduce
the chance to getting the problem or mistake from each of the stages. For
this waterfall model, the stage will continue go through one by one before
done with one another, so it could follow the stage and when anything
goes wrong, it could be easy to get back to the previous stage.
Convenience of getting information. Since, the waterfall model is the one
of the model that require many of the information before start to develop
and come out with a better system, therefore, the more information can be
gather, the more successful system will be based on the research or
survey form from the customer.
Task will be easy to manage. For this waterfall model, each of the stage will
have different task to be complete then only the other stage can be
continue, therefore, the task could be easy to manage by different part of
stages.

5.2.2 Scope of Waterfall Model

There are few of the stages that used in this entire system :
Initiation part :

Planning part to gather the information from the customer.

Initiation part :

Analyze and combine the information to come out with the final
result.

Design :

The physical and logical design.

Develop and
test :

Develop system and test system to ensure the system work

perfectly.

Implementation :

Implementation will be conducted to make sure the user able to

use the system and understand how the system work by tested
the user.

Maintenance :

Fully test the system to make sure there are no any error before
deliver to end user.

12 | P a g e

5.2.3 Stages of Waterfall model

From the waterfall diagram which shown in the figure 2 have 6 stages, the stage
start with the planning, continue by analysis, design, testing, implementation and
maintenance as well. The following is the stages of waterfall model;

13 | P a g e

Initiation Objectives: This stage will be known as information

gathering of new system. A new system should have a new
requirement that usually after a better understand from the internal
user and external user which the information will be combine
together to come out with a final report and based on the
information to come out with the better system.
Analysis based on the information that gather: This stage will be
analyze the information that combine together and make the final
decision to choose which should be able to meet customer need in
order to continue with the designing part. To better understand the
need of the customer, therefore, this analysis part will be useful in
this stage.
Design: In this stage, there can be physical design and logical
design part. Physical design which is represent as how the data flow
in and out to transform data, usually the physical design could be
define as user interface design, data design or process design of
the system. For logical design, usually define as coding part in the
system which mean how data is given as an input into a system,
how it is process and how it is displayed as output.
Develop and test. In this stage, after complete the development of
system, the system should be tested to confirm whether the system
is work without any error and make sure the requirements of
customer are meet. All of these should be confirmed in order to
proceed to the next stage.
Implementation. For this part, the system is installed and made
operational in the production environment after the end user accept
testing to test the system whether the system is perfect and run
without any error, the developer will stay with the end user to assist
the end user if there are anything goes wrong with the system and
yet if there are any requirement doesn't meet or fail to.
Maintenance. In this part, this will be the last part to test the
system before the system will deliver to the end user. So, the
system will be fully tested to make sure the system is perfectly run
without error and all of the function should be work included the
database as well.

5.2 Format for Methodology Comparison (Ahamed Nashath)

RAD
Comparison Factors

Description

Explanation

Project Size

Small Scale

This methodology has a

small scale of project size.

Project Cost

Low

RAD has the requirements

that are needed to the
system for a lowest
maintenance cost.

Speed

Speed

This meets the requirements

of the user in a short period
of time period.

Flexibility

Flexible

There are no any conflicts

with the previous design and
requirements.

Well documented

Minimized

This system provides a

minimum level of
documents.

Arrangement of task

Easy

Model arrangement is a
complex task but using RAD
it makes easy is every
stages but doesnt give
details in stages.

Schedule

Short

RAD model distributes series

of short and iterative
development cycles.

Risk

Low

This model helps to minimize

risk in every aspect of the
project.

14 | P a g e

15 | P a g e