Scribd
Upload
3 views

Software Processes Model

The document outlines various software process models including the Waterfall model, Evolutionary development, Component-based software engineering, Process iteration, Incremental delivery, Spiral development, and Extreme programming. Each model is described with its objectives, stages, and advantages, emphasizing the importance of iteration and customer involvement in software development. Additionally, it mentions other agile processes such as LEAN, SCRUM, FDD, and TDD.

Uploaded by

storesandrana
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
3 views

Software Processes Model

The document outlines various software process models including the Waterfall model, Evolutionary development, Component-based software engineering, Process iteration, Incremental delivery, Spiral development, and Extreme programming. Each model is described with its objectives, stages, and advantages, emphasizing the importance of iteration and customer involvement in software development. Additionally, it mentions other agile processes such as LEAN, SCRUM, FDD, and TDD.

Uploaded by

storesandrana
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 14

Software Processes Model

1-Waterfall model

Requirements
definition

System and
software design

Implementa tion
and unit testing

Integration and
system testing

Operation and
maintenance
2-Evolutionary development Model

A) Exploratory development
• Objective is to work with customers and to evolve
a final system from an initial outline specification.
• Should start with well-understood requirements
and add new features as proposed by the
customer.

B) Throw-away prototyping
• Objective is to understand the system
requirements.
• Should start with poorly understood requirements
to clarify what is really needed.
Evolutionary development

Concurrent
activities

Initial
Specification version

Outline Intermediate
Development versions
description

Final
Validation version
3-Component-based software engineering


Based on systematic reuse where systems are
integrated from existing components or COTS
(Commercial-off-the-shelf) systems.

Process stages
• Component analysis;
• Requirements modification;
• System design with reuse;
• Development and integration.

This approach is becoming increasingly used
as component standards have emerged.
Reuse-oriented development

Requirements Component Requirements System design


specification analysis modification with reuse

Development System
and integ
ration validation
4-Process iteration

System requirements ALWAYS evolve in the
course of a project so process iteration where
earlier stages are reworked is always part of
the process for large systems.

Iteration can be applied to any of the generic
process models.

Two (related) approaches
• Incremental delivery;
• Spiral development.
4a-Incremental delivery

Rather than deliver the system as a single delivery, the
development and delivery is broken down into
increments with each increment delivering part of the
required functionality.

User requirements are prioritised and the highest
priority requirements are included in early increments.

Once the development of an increment is started, the
requirements are frozen though requirements for later
increments can continue to evolve.
Incremental development

Define outline Assign requirements Design system


requirements to increments architectur
e

Develop system Validate Integrate Validate


increment increment increment system
Final
system
System incomplete
Incremental development advantages


Customer value can be delivered with each
increment so system functionality is available
earlier.

Early increments act as a prototype to help
elicit requirements for later increments.

Lower risk of overall project failure.

The highest priority system services tend to
receive the most testing.
4b-Spiral development

Process is represented as a spiral rather than
as a sequence of activities with backtracking.

Each loop in the spiral represents a phase in
the process.

No fixed phases such as specification or
design - loops in the spiral are chosen
depending on what is required.

Risks are explicitly assessed and resolved
throughout the process.
Spiral model of the software process
Determine objectives,
Evaluate alternatives,
alternatives and
identify, resolve risks
constraints Risk
analysis

Risk
analysis

Risk
Opera-
analysis
Prototype 3 tional
Prototype 2 protoype
Risk
REVIEW analysis Proto-
type 1
Requirements plan Simulations, models, benchmarks
Life-cycle plan Concept of
Operation S/W
requirements Product
design Detailed
Requirement design
Development
plan validation Code
Unit test
Integration Design
V&V Integration
and test plan
Plan ne xt phase test
Acceptance
Service test Develop, verify
next-level product
Spiral model sectors

Objective setting
• Specific objectives for the phase are identified.
• Project risks are identified

Risk assessment and reduction
• Risks are assessed and activities put in place to reduce the
key risks (e.g. if requirements are inappropriate, prototype system may be developed.

Development and validation
• A development model for the system is chosen which can be
any of the generic models.

Planning
• The project is reviewed and the next phase of the spiral is
planned.
5-Extreme programming

An approach of development based on the development
and delivery of very small increments of functionality.

Relies on constant code improvement, user involvement
in the development team and Pair-Programming.
OTHERS AGILE PROCESS

LEAN

SCRUM

FDD (FEATURE DRIVEN DEVELOPMENT)

TDD (TEST DRIVEN DEVELOPMENT)

You might also like