Phases of Linear Sequential Model: Analysis

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 20

Phases of Linear Sequential Model

Analysis

Designing

Coding

Testing

Maintenance
& support
Software requirement analysis:
In this Phase , the requirements for the software are established through discussion
with client and are then documented.

Designing:
In this phase , the requirements are converted into design to be used in the next phase.
The design includes various elements such as database structures, software architecture
and procedures.
The design is first passes through the quality test and then documented.

Coding:
In this phase the actual coding of the software is done. The design of the previous
phase is converted into the code.

Testing:
In this phase, the output generated is checked to ensure that it matches the requirements.
The programs developed in the previous phase are checked for the logical and syntax errors.

Maintenance and Support:


The software developed needs to maintenance and support. This refers to the changes as
well as new requirements in the software after delivery.
Software Process Models: Waterfall..

Requirements
definition

System and
software design

Implementation
and unit testing

Integr ation and


system testing

Operation and
maintenance

3
Waterfall Strengths

• Easy to understand, easy to use


• Provides structure to inexperienced staff
• Milestones are well understood
• Sets requirements stability
• Good for management control (plan, staff, track)
• Works well when quality is more important than cost
or schedule
Waterfall Deficiencies
All requirements must be known upfront
Doesn’t cope well with changes required by
the client
Development teams might wait for each
other
A working version of the product is available
only late
Applicability:
When requirements are well known and few changes are
likely to be needed
Can be used also for parts of larger software systems

Requirements are very well known


Product definition is stable
Technology is understood
New version of an existing product
Porting an existing product to a new platform.
Software Process Models:
Evolutionary Development…
Concurr ent
activities

Initial
Specification
version

Outline Intermediate
Development
description versions

Final
Validation
version

7
Incremental Model (INM)

Final System
1-1 1-2 1-3 1-4

Basic process
Req. S/w Solution
1 Increment process Coding
Coding
Design Test
Analysis

Next Increment
Main characteristics:

The phases of the software construction are interleaved

Feedback from the user is used throughout the entire


process

The software product is refined through many versions


Advantages:

Deals constantly with changes


Provides quickly an initial version of the system
Involves all development teams

Disadvantages:

Quick fixes may be involved


“Invisible” process, not well-supported by documentation
The system’s structure can be corrupted by continuous
change
Special tools and techniques may be necessary
The client may have the impression the first version is very
close to the final product and thus be less patient

Applicability:

When requirements are not well understood


When the client and the developer agree on a “rapid
prototype” that will be thrown away
Good for small and medium-sized software systems
Phases of Prototyping Model
Requirement Analysis

Quick Design

Prototype Implementation

Testing

Deliver Final Product


Advantages of Prototyping
Model
The following are the advantages of Prototyping model:
• Due the interaction between the client and developer right from
the beginning , the objectives and requirements of the software
is well established.
• Suitable for the projects when client has not clear idea about his
requirements.
• The client can provide its input during development of the
prototype.
• The prototype serves as an aid for the development of the final
product.
Disadvantages of Prototyping
Model
The prototyping model has the following disadvantages.
• The quality of the software development is
compromised in the rush to present a working version
of the software to the client.
• The client look at the working version of the product
at the outset and expect the final version of the
product to be deliver immediately. This cause
additional pressure over the developers to adopt
shortcut in order to meet the final product deadline.
• It becomes difficult for the developer to convince the
client as why the prototype has to be discarded.
Rapid Application Development:

• RAD is a high speed version of linear sequential model. It is


characterized by a very short development life cycle, in which
the objective is to accelerate the development.
• The RAD model follows a component based approach.

• In this approach individual components developed by different


people are assembled to develop a large software system.
Advantages of Using RAD Model:

The RAD has following advantages:

• Due to emphasis on rapid development , it results in


the delivery of fully functional project in short time
period.
• It encourages the development of program component
reusable.
Disadvantages of Using RAD Model:

The RAD model has following disadvantages :


• It requires dedication and commitment on the part of the
developers as well as the client to meet the deadline. If either
party is indifferent in needs of other, the project will run into
serious problem.
• Its application area is restricted to system that are modular and
reusable in nature.
• It is not suitable for the applications that have a high degree of
technical risk.
• It is not suitable for the large projects because they require more
manpower for creating multiple RAD groups.
.Software Process Models: Spiral Model.
.Software Process Models: Spiral Model.

• Main characteristics:
– Also a hybrid model that support process iteration
– The process is represented as a spiral, each loop in the
spiral representing a process phase
– Four sectors per loop: objective setting, risk assessment
and reduction, development and validation, planning
– Risk is explicitly taken into consideration

19
Software Process Models: ..Spiral Model

• Advantages:
– Risk reduction mechanisms are in place
– Supports iteration and reflects real-world practices
– Systematic approach
• Disadvantages:
– Requires expertise in risk evaluation and reduction
– Complex, relatively difficult to follow strictly
– Applicable only to large systems
• Applicability:
– Internal development of large systems
20

You might also like

pFad - Phonifier reborn

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

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy