Escolar Documentos
Profissional Documentos
Cultura Documentos
Conceptualize
Specify
Retire
Design
Maintain
Deliver Code
Test
1
Classical Waterfall Model
Classical waterfall model divides
life cycle into phases:
feasibility study,
requirements analysis and
specification,
design,
coding and unit testing,
integration and system testing,
maintenance.
2
Classical Waterfall Model
Feasibility Study
Req. Analysis
Design
Coding
Testing
Maintenance
3
Relative Effort for Phases
Phases between feasibility
study and testing 60
known as development 50
Relative Effort
phases.
40
Among all life cycle phases 30
maintenance phase
consumes maximum effort. 20
10
Among development
phases, 0
Maintnce
Req. Sp
Design
Test
Coding
testing phase consumes the
maximum effort.
4
Classical Waterfall Model
(CONT.)
5
Feasibility Study
Economic
feasibility
(also called
cost/benefit
feasibility)
6
Feasibility Study
Main aim of feasibility study:determine whether
developing the product is
financially worthwhile
technically feasible.
First roughly understand what the customer
wants:
different data which would be input to the system,
processing needed on these data,
output data to be produced by the system,
various constraints on the behavior of the system.
7
Activities during Feasibility
Study
Work out an overall understanding
of the problem.
Formulate different solution
strategies.
Examine alternate solution
strategies in terms of:
resources required,
cost of development, and
development time.
8
Activities during Feasibility
Study
Perform a cost/benefit analysis:
to determine which solution is the
best.
you may determine that none of
the solutions is feasible due to:
high cost,
resource constraints,
technical reasons.
9
Requirements Analysis and
Specification
Aim of this phase:
understand the exact
requirements of the customer,
document them properly.
Consists of two distinct
activities:
requirements gathering and
analysis
requirements specification. 10
Goals of Requirements
Analysis
Collect all related data from the
customer:
analyze the collected data to
clearly understand what the
customer wants,
find out any inconsistencies and
incompleteness in the
requirements,
resolve all inconsistencies and
incompleteness. 11
Requirements Gathering
14
Requirements Analysis (CONT.)
Engineers doing
requirements analysis and
specification:
are designated as analysts.
15
Design
Design phase transforms
requirements specification:
into a form suitable for
implementation in some
programming language.
16
Design
In technical terms:
during design phase, software
architecture is derived from the
SRS document.
Two design approaches:
traditional approach,
object oriented approach.
17
Traditional Design Approach
18
Structured Analysis
Activity
Identify all the functions to be
performed.
Identify data flow among the
functions.
Decompose each function
recursively into sub-functions.
Identify data flow among the
subfunctions as well.
19
Structured Analysis (CONT.)
21
Object Oriented Design
Object structure
further refined to obtain the
detailed design.
OOD has several advantages:
lower development effort,
lower development time,
better maintainability.
23
Implementation
Purpose of implementation
phase (coding phase):
translate software design into
source code.
24
Implementation
26
Integration and System
Testing
Different modules are integrated in
a planned manner:
modules are almost never integrated
in one shot.
Normally integration is carried out
through a number of steps.
During each integration step,
the partially integrated system is
tested.
27
Integration and System
Testing
M1 M2
M3 M4
28
System Testing
Corrective maintenance:
Correct errors which were not discovered
during the product development phases.
Perfective maintenance:
Improve implementation of the system
enhance functionalities of the system.
Adaptive maintenance:
Port software to a new environment,
e.g. to a new computer or to a new operating system.
31
Iterative Waterfall Model
Classical waterfall model is
idealistic:
assumes that no defect is
introduced during any
development activity.
in practice:
defects do get introduced in almost
every phase of the life cycle.
32
Iterative Waterfall Model
(CONT.)
33
Iterative Waterfall Model
(CONT.)
34
Iterative Waterfall Model
(CONT.)
Feasibility Study
Req. Analysis
Design
Coding
Testing
Maintenance
35
Iterative Waterfall Model
(CONT.)
36
Phase containment of
errors
37
Prototyping model
38
Prototyping Model
Before starting actual
development,
a working prototype of the system
should first be built.
A prototype is a toy implementation
of a system:
limited functional capabilities,
low reliability,
inefficient performance.
39
Prototype model
An early approximation of a final system
or product) is built, tested, and then reworked
as necessary until an acceptable prototype is
finally achieved.
The prototyping model is applied when
detailed information related to input and output
requirements of the system is not available. In
this model, it is assumed that all the
requirements may not be known at the start of
the development of the system. 40
Prototyping Model (CONT.)
41
42
Prototyping Model (CONT.)
Build Prototype
Customer
Requirements satisfied
Customer
Gathering Evaluation of Design
Quick Design
Prototype
Implement
Refine
Requirements Test
Maintenance
Prototyping Model (CONT.)
46
Types of Prototypes
Functional Prototypes
Display Prototypes
Miniatures
Throwaway prototype
47
Functional prototypes are designed to imitate the functions of the
actual product as closely as possible no matter how different they
look from the actual product. These types of prototypes are
produced for the products which are dependent on the function
rather than the display.
Display prototypes are designed with more focus on the look and
feel of the product rather than the functions.
Miniatures are smaller versions or the basic versions of the product
focused on both the functional aspect as well as the display aspect.
Miniatures are usually developed by the 3D printing of the product.
48
Prototyping Model (CONT.)
51
When to use Prototype
model:
53
Evolutionary Model (CONT.)
C
A AB A
B
55
56
Advantages of Evolutionary
Model
Users get a chance to experiment with a
partially developed system:
much before the full working version is
released,
Helps finding exact user requirements:
much before fully working system is developed.
Core modules get tested thoroughly:
reduces chances of errors in final product.
57
Disadvantages of
Evolutionary Model
Often, difficult to subdivide
problems into functional units:
which can be incrementally
implemented and delivered.
evolutionary model is useful for
very large problems,
where it is easier to find modules for
incremental implementation.
58
Evolutionary Model with
Iteration
Many organizations use a
combination of iterative and
incremental development:
a new release may include new
functionality
existing functionality from the
current release may also have
been modified.
59
Evolutionary Model with
iteration
Several advantages:
Training can start on an earlier release
customer feedback taken into account
Markets can be created:
for functionality that has never been
offered.
Frequent releases allow developers to
fix unanticipated problems quickly.
60
Spiral Model
Proposed by Boehm in 1988.
Each loop of the spiral represents a
phase of the software process:
the innermost loop might be concerned with
system feasibility,
the next loop with system requirements
definition,
the next one with system design, and so on.
There are no fixed phases in this model,
the phases shown in the figure are just
examples.
61
Spiral Model (CONT.)
62
Spiral Model (CONT.)
Customer
Evaluation of Develop Next
Prototype Level of Product
63
64
65
Objective Setting (First
Quadrant)
67
Spiral Model (CONT.)
70
Comparison of Different Life Cycle
Models (CONT.)
73
When to use Spiral model: