Scribd
Upload
143 views26 pages

SDLC Detailed

SDLC

Uploaded by

Shalesh Gabhane
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
143 views26 pages

SDLC Detailed

SDLC

Uploaded by

Shalesh Gabhane
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 26

OHT 7.

Chapter 7.1

Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.2

Chapter 7

Software development methodologies:


- The software development life cycle (SDLC) model
- The prototyping model
- The spiral model
- The object-oriented model
Factors affecting intensity of SQA activities
Verification, validation and qualification
Development and quality plans for small and for internal
projects
A model for SQA defect removal effectiveness and cost
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.3

Introduction

We will start off talking about (in some


cases reviewing) popular development
models
Will switch to discussion how SQA
activities are handled within the
development process, and
Factors that need to be considered before
applying these activities
So, why this approach?
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.4

Introduction

Why discuss the models?


Answer: They represent the framework of a
disciplined approach to development.
Have milestones, deliverables, constraints, etc.
SQA must take place in conjunction with the
completing of these activities or looking at the
work products produced from these activities.
Need to understand the models before we can
produce plans that are integrated into these
Galin, SQA from theory to implementation
Pearson Education Limited 2004
models.

1. Classic and Other Software Development


Methodologies

OHT 7.5

Will discuss

The Software Development Life Cycle (SDLC)


The prototyping model
The spiral model
The OO model

Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.6

The SDLC

The classic mode.

Still in WIDE use today.


Captures the major building blocks in development
Linear sequence
Highly structured; plan-driven; Heavy-weight process
Product delivered for evaluation and deployment at the
end of development and testing
Big bang approach
Used for major projects of length
But serves as a framework for other models
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.7

Prototyping Model

Replaces some of the parts of the SDLC with an


evolutionary and iterative process.
Software prototypes are repeatedly provided to
customer for evaluation and feedback.
Primarily iterate design and implementation.
Development team provided requirements.

Ultimately, the product reaches a satisfactory


completion.
Then, the remainder of the process is carried out in
the context of another model, such as SDLC
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.8

Spiral Model

Uses an iterative approach designed to address each phases in


development by obtaining customer comments and change, risk
analysis, and resolution.
The spiral model typically has a spiral for each of the traditional
development phases.
Within a cycle, specific engineering (design, development, etc.)
can take place using any other models, like SDLC, prototyping,..
The Spiral Model (Barry Boehm) is a risk-centered development
model where each spiral includes major risk activities /
assessments.
Was developed after SDLC in response to delayed risk in SDLC
As the SDLC, it is considered a heavy-weight, plan-driven
methodology and is highly structured.

Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.9

The Object-Oriented Model

Emphasis here is re-usability via reusable objects


and components.

Component-based software development.


For non-available components, developer may

prototype needed modules,


use an SDLC approach,
purchase libraries of objects,
develop his own, etc.

Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.10

Now, in a bit more detail

Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.11

The SDLC
Requirements Definition:
done by customers
Analysis: analyze
requirements to form an
initial software model
Design: Detailed definition
of inputs/outputs and
processes including data
structures, software
structure, etc.

Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.12

The SDLC
Coding: Design
translated into code.
Coding includes SQA
activities such as
inspections, unit tests and
integration tests
Many takeoffs from this:
These tests done by
developers: individual
(unit), group or team
(integration tests.)

Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.13

The SDLC
System Tests: Goal: to
discover errors / correct
errors to achieve an
acceptable level of quality.
Carried out by developers
prior to delivery.
Sometimes acceptance
tests carried out by
customer or in conjunction
with developer

Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.14

The SDLC
Installation / Conversion:
After testing, system is
installed and/or replaces an
existing system;
Requires software / data
conversion
Important to not interrupt
daily activities during
conversion process.

Install incrementally, run in


parallel; turn switch and
live with it, etc.
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.15

The SDLC
Operations and
Maintenance:
Hopefully done for years.
Maintenance:
Corrective
Adaptive
Perfective

Lots of variations to the


classic SDLC many in
response to problems.
Notice the feedback loops?
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.16

Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.17

Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.18

The Prototyping Model

One main idea behind prototyping is for the


development of fast prototypes and
customer availability for feedback.
Often prototyping tools are used to help
Developers respond to feedback and add
additional parts as application evolves into
an acceptable product.
Recognize this process can be inserted into
the SDLC or other models.
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.19

REQUI REMENTS
DETERMINATION
BY CUSTOMER
PROTOTYPE
DESIGM
PROTOTYPE
I MPLEMENTATION
PROTOTYPE
EVALUATI ON
BY CUSTOMER
REQUIREMENTS
FULFILLED ?
YES
SYSTEM TESTS AND
ACCEPTANCE TESTS
SYSTEM CONVERSI ON

NO

REQUI REMENTS FOR


CORRECTI ONS, CHANGES
AND ADDITIONS

A good approach for small to


medium-sized projects.
Very important: customer involvement.

SYSTEM OPERATION
AND MAI NTENANCE
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.20

Prototyping Model - more

Advantages (book)
Shorter development process
Substantial savings in development resources (time)
Better fit to customer requirements and reduced risk of
project failure
Easier and faster user comprehension of new system

Disadvantages
Less flexibility and adaptability to changes and
additions
Reduced preparation for unexpected instances of failure
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.21

The Spiral Model

A heavy-weight, plan-driven, highlystructured approach for large projects.


Especially designed for those with higher
chances of failure.
Combines iterative model, emphasizes risk
assessment, customer participation,
prototyping, and more
Definitely an iterative process.
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.22

Can see each spiral


includes:
Planning

Risk Analysis / Resolution


Engineering activities
(design, code, test)
Customer Evaluation
(errors, changes, new
requirements)
Source: After Boehm 1988 ( 1988 IEEE)
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.23

Revised Spiral Model provides


customer with improved chances
for changes;
developer better chances to stay
within budget and time.
Done by increased emphasis on
customer participation and
on engineering activities.
Extra sections in spiral
dedicated to customer actions
and developer engineering
Source: After Boehm 1998 ( 1988 IEEE)

Galin, SQA from theory to implementation

Pearson Education Limited 2004

The Object-Oriented Model

OHT 7.24

Easy integration of existing software modules (objects /


components) into newly developed software systems.
Process begins with OOA and OOD
Then, acquire suitable components from reusable software
component libraries (or purchase them).
Otherwise, develop as needed.
Can involve adding to repertoire of library components.
Economy: integrating reusable components; much lower cost
than developing
Improved quality using tested components
Shorter development times: integration of reusable software
components.
Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.25

Galin, SQA from theory to implementation

Pearson Education Limited 2004

OHT 7.26

Now, onto
Factors Affecting the Intensity of Quality
Assurance Activities within the Development
Process

Galin, SQA from theory to implementation

Pearson Education Limited 2004

You might also like