CS 313 SOFTWARE ENGINEERING

LECT-03
Introduction to SDLC Models :
SDLC is an acronym for Software Development Life Cycle .
SDLC is the process of creating the software. These models are used in order for a
sequential flow of the software development process. There are advantages and
disadvantages of SDLC models. Every organization will analyze the SDLC models
before starting a project to ensure the workflow of the development process.
 Need of Software Life Cycle
Models
For More complex systems
More features
 greater complexity
More chances of error prone without proper plan/cycle.

To overcome the above criteria we need systematic approach which are nothing but
software Life Cycle Models.

3
 IBM Global Services – Testing Competency

Various Software Life Cycle Models

Software life cycle models describe various phases of the software cycle and the order
in which those phases are executed. There are tons of models, and many companies
adopt their own, but all have very similar patterns. Some of the models as follows.

• Build and fix model

 Water fall model/ Linear Sequential/ Classic Life Cycle Model

 V-Model
 Rapid Application Development (RAD) model
 Incremental Model
 Spiral Model
 Proto type model
 Fourth Generation (4GT) Techniques

5
 Build And fix Model

Software life cycle models describe phases of the software cycle and the order in which
those phases are executed. There are tons of models, and many companies adopt
their own, but all have very similar patterns. The general, basic model is shown below
Application:-

LOC is less than 100,it is suitable.

Advantages:-

FLOW COST TIME

Normal flow SAME LESS
Abnormal flow SAME HIGH

TESTING ONLY PERFORMS AT THE CLIENT SIDE

 Deliverable
• Deliverable is the output delivered to a customer or sponsor
• A deliverable could be a report, a document, a software product,
a server upgrade or any other building block of an overall
project. A deliverable may be composed of multiple smaller
deliverables
 IBM Global Services – Testing Competency

Water fall / Linear Sequential

/Classic Life Cycle Model
The "waterfall model", documented in 1970 by Royce was the first publicly documented
life cycle model. The model was developed to help with the increasing complexity of
aerospace products.
most common and classic of life cycle models referred to as a linear- sequential life
cycle model. It is very simple to understand and use. In a waterfall model, each phase
must be completed in its entirety before the next phase can begin. At the end of each
phase, a review takes place to determine if the project is on the right path and whether
or not to continue or discard the project. Unlike what I mentioned in the general model,
phases do not overlap in a waterfall model.
The least flexible and most obsolete of the life cycle models. Well suited to projects
that has low risk in the areas of user interface and performance requirements, but high
risk in budget and schedule predictability and control.

1
 IBM Global Services – Testing Competency

Water fall model

Requirements
Specification

System
design

Coding

Testing

Delivery

1
 IBM Global Services – Testing Competency

Water fall model

Advantages
Simple and easy to use.
Easy to manage due to the rigidity of the model – each phase has specific
deliverables and a review process.
Phases are processed and completed one at a time.
Works well for smaller projects where requirements are very well understood/stable.
Disadvantages
It’s difficult to define all requirements at the beginning of a project.
This is not suitable for accommodating any change.
Adjusting scope during the life cycle can kill a project
No working software is produced until late during the life cycle.
High amounts of risk and uncertainty.
Poor model for complex and large projects.
Real projects are rarely sequential.
1
 IBM Global Services – Testing Competency

Prototype model
In this model, a prototype (an early approximation of a final system or product) is built,
tested, and then reworked as necessary until an acceptable prototype is finally achieved
from which the complete system or product can now be developed.
Prototype paradigm begins with requirements gathering. Developer and customer meet
and define the overall objectives for the software, identify whatever requirements are
known, and outline areas where further definition is mandatory.
A quick design occurs which leads to the construction of prototype.
The prototype is evaluated by the customer/user and used to refine the requirements for
the software to be developed.
Iteration occurs as the prototype is tuned to satisfy the user requirements, while at the
same time enabling developer to better understand what needs to be done.

14
An example of a prototype is the first model of a new robot. An original object or
form which is a basis for other objects, forms, or for its models and generalizations.
An early sample or model built to test a concept or process. The prototype had loose
wires and rough edges, but it worked.

1) In software development, a prototype is a rudimentary working model of a product

or information system, usually built for demonstration purposes or as part of the
development process. In the systems development life cycle (SDLC) Prototyping
Model, a basic version of the system is built, tested, and then reworked as necessary
until an acceptable prototype is finally achieved from which the complete system or
product can now be developed.
2) In prototype-based programming, a prototype is an original object; new objects are
created by copying the prototype.
3) In hardware design, a prototype is a "hand-built" model that represents a
manufactured (easily replicable) product sufficiently for designers to visualize and test
the design.
prototyping model
CS 313 SOFTWARE ENGINEERING

LECT-04
 IBM Global Services – Testing Competency

Prototype model
Begin
Listen to Build
Prototype
Client/user

Client
evaluates the
prototype
Prototype used for
Understanding the requirements for the user interface
Examining feasibility of a proposed design approach
Disadvantages
Users treat the prototype as the solution
A prototype is only a partial solution
18
EVOLUTIONARY PROCESS MODELS
Incremental MODEL + Iterative model
Iterative Model
 IN THIS MODEL THE WHOLE PRODUCT
IS DEVELOPED STEP BY STEP
Advantages:
• We can track the error or defects in early stages.
• We can get the reliable user feedback when we presenting
sketches and blueprint of the product to users for their
feedback, we are effectively asking them to imagine how the
product will work.
• Less time in documenting ,more time in design.

Disadvantages:-
Costly system design _Requirements of the system are must be
clearly defined and understood for entire life cycle(very first)
When To Use Iterative model:

• Requirements of the system are must be clearly

defined and understood.
• When the project is big.
• Major ; however, some details can evolve with
time.
 IBM Global Services – Testing Competency

Incremental model
This model does not attempt to start with full specification of requirements. Multiple
development cycles take place here, making the life cycle a ―multi-waterfall‖ cycle.
Cycles are divided up into smaller, more easily managed iterations. Each iteration
passes through the requirements, design, implementation and testing phases.
A working version of software is produced during the first iteration, so you have working
software early on during the software life cycle. Subsequent iterations build on the
initial software produced during the first iteration.

Key Points
 Development and delivery is broken down into increments
 Each increment delivers part of the required functionality
 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
 Requirements for later increments can continue to evolve

23
 IBM Global Services – Testing Competency

Incremental model (contd.)

Increment 1

System Delivery of 1st

Analysis Coding Testing
Design Increment

System Delivery of 2nd

Increment 2 Analysis Coding Testing
Design Increment
No. of increments

System Delivery of 3rd

Analysis Coding Testing
Increment 3 Design Increment

Time

25
 IBM Global Services – Testing Competency

Incremental model (contd.)

Advantages

• Generate working software quickly and early during the software life cycle.
• This model is more flexible- less costly to change scope and requirements.
• It is easier to test and debug during a smaller iteration.
• In this model customer can respond to each built.
• Lower initial delivery cost.
• Easier to manage risk because risky piece are identified and handle during it had
iteration.

Disadvantages

Needs good planning and design.

Needs a clear and complete definition of the whole system before it can be broken
down and built incrementally
Total cost is higher than waterfall.
When to use incremental model:
• This model can be used when the requirements of
the compplete system are clearly defined and
understood
• Major requirements must be defined :some details
can evolve with time.
• There is need to launch the product early in market.
• A new technology is being used.
• Resources with needed skill set are not available.
Cs 313 software engineering

Lect -05
 IBM Global Services – Testing Competency
Spiral - model
Presented by Boehm in 1985. The spiral model is focused on risk management.
This model of development combines the features of the prototyping model and the
waterfall model. The spiral model is favored for large, expensive, and complicated
projects.
The spiral model is similar to the incremental model, with more emphases placed on risk
analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and
Evaluation. A software project repeatedly passes through these phases in iterations
(called Spirals in this model). The baseline spiral, starting in the planning phase,
requirements is gathered and risk is assessed. Each subsequent spiral builds on the
baseline spiral.
Requirements are gathered during the planning phase. In the risk analysis phase, a
process is undertaken to identify risk and alternate solutions. A prototype is produced at
the end of the risk analysis phase.
Software is produced in the engineering phase, along with testing at the end of the
phase. The evaluation phase allows the customer to evaluate the output of the project to
date before the project continues to the next spiral.
In the spiral model, the angular component represents progress, and the radius of the
spiral represents cost. 29
 IBM Global Services – Testing Competency

Spiral – model (contd.)

Planning Risk
Analysis

Go/No-Go
Decision

Evaluation Development

30
 IBM Global Services – Testing Competency

Spiral – model (contd.)

Advantages
High amount of risk analysis.
Risks are explicitly assessed and resolved throughout the process
Focus on early error detection and design flaws.
Good for large and mission-critical projects.
Software is produced early in the software life cycle.
Disadvantages
Can be a costly model to use.
Risk analysis requires highly specific expertise.
Project’s success is highly dependent on the risk analysis phase.
Doesn’t work well for smaller projects.

32
When to use this model:

• When cost and risk evaluation is important.

• For medium to high risk project
• Users unsure of their of their needs
• Requirements are complex
• In research and exploration where significant changes are
expected
 IBM Global Services – Testing Competency

Rapid Application Development (RAD)

model
RAD model makes heavy use of reusable software components with an extremely short
development cycle.
The RAD is a linear sequential software development process that emphasizes an
extremely short development cycle. The RAD software model is a "high speed"
adaptation of the linear sequential model in which rapid development is achieved by
using a component-based construction approach. Used primarily for information systems
applications, the RAD approach encompasses the following phases
Business modeling
Data modeling
Process modeling
Application generation
Testing
RAD process emphasizes reuse many of the program components have already been
tested, which minimizes the testing and development time.

34
Rapid Application Development
(RAD) model
CS 313 SOFTWARE ENGINEERING

LECT-07
Software requirements Analysis &
specification
 Requirements engineering
One large
document

processing

User expectation for a new or modified product

CS 313 SOFTWARE ENGINEERING

LECT-08
Requirements :describe “what” of a system not the
“how”
types of requirements

Type 1 Type 2
known functional

Non
Unkown
functional

undreamed
 • Stackholder believes to be implemented
known

• Forgotten by the stackholders right now

unknown

• Stackholder may not be able to think of new requirements due to limited

knowledge.
undreamed
Requirement Elicitation
Requirement Analysis
Requirement Documentation
Requirement review
 IBM Global Services – Testing Competency

V - model
 Another variant of the waterfall model — the V-model — associates each development
activity with a test or validation at the same level of abstraction. Each development
activity builds a more detailed model of the system than the one before it, and each
validation tests a higher abstraction than its predecessor.

 The least flexible and most obsolete of the life cycle models. Well suited to projects that
has low risk in the areas of user interface and performance requirements, but high risk
in budget and schedule predictability and control.

5
 IBM Global Services – Testing Competency

V - model
System System
Requirements
Test Plan Testing

High Level Integration Integration

Design Test Plan Testing

Low level Module Level Module Level

Design Test Plan Testing

Code &
Unit test

5
 IBM Global Services – Testing Competency

V - model
Advantages
 Simple and easy to use.
 Each phase has specific deliverables.
 Higher chance of success over the waterfall model due to the development of test
plans early on during the life cycle.
 Works well for small projects where requirements are easily understood.
Disadvantages
 Very rigid, like the waterfall model.
 Little flexibility and adjusting scope is difficult and expensive.
 Software is developed during the implementation phase, so no early prototypes of the
software are produced.
 Model doesn’t provide a clear path for problems found during testing phases.

56