Reference For Unified Process-Iterative Model Only

REQUIREMENTS ENGINEERING
& MANAGEMENT(SWE2003)
Prof. R.Kiruba Thangam

SITE
VIT University
Kiruba_Winter 2015-16 1
Requirements & Software Life
Cycle
Effective requirements
management
 Can occur only within the context of a
reasonably well defined software
process.
Software Process
 Software Process defines the full set of
activities the team must execute to
deliver the final software product
Software Team
 Team’s development process defines
who is doing what,when and how.
Process model selection
 Requirements
 Team’s ability
 Budget
 Time
Waterfall Model
Waterfall Model
 Widely followed in 1970s and 80’s.
 Medium to large scale projects
Waterfall model
 Software activities proceed logically
through a sequence of steps.
 Each step bases its work on the activities
of the previous step.
 Design logically follows requirements,
coding follows design and so on.
Waterfall model
 Recognize the need for feedback loops
between stages.
 Acknowledge that design affects
requirements.
 Develop prototype system in parallel
with requirement analysis and design
activities.
SPIRAL MODEL
SPIRAL MODEL
Serves as a role model for those who believe success follows
a more risk-driven and incremental development path.
It provides a sensible road map that helps address some

of the requirements challenges.
13
. SPIRAL MODEL
•Some refer to this as the process of creating instant legacy
code, progress being measured by our newfound ability to
create unmaintainable and incomprehensible code two to
three times as fast as with earlier methods!
14
SPIRAL MODEL
 The spiral model starts with requirements planning and
concept validation, followed by one or more prototypes to
assist in early confirmation of our understanding of the
requirements for the system.
Development is initially driven by a series of risk driven

prototypes then a structured waterfall-like process is used
to produce the final system.
Starts with requirements planning and concept

validation.
15
Advantage :
 Availability of multiple feedback

opportunities with the users and customers.
In today's environment, we typically do not have
the luxury of time for full concept validation and two
or three prototypes, followed by a rigorous
waterfall methodology.
Iterative approach
 The iterative approach introduced by

Kruchten [1995]
 Effective in wide variety of project tyes
 Exhibit number of advantages over
waterfall and Spiral model
In the traditional software development process
models, time moves forward through a series of
sequential activities, with requirements preceding
design, design preceding implementation, and so
on.
Iterative approach
 Decoupled from the logical software
activities that occur in each phase.
 Allows us to revisit various activities like

requirements, design, and
implementation.
Life cycle phases
INCEPTION ELABORATION CONSTRUCTION TRANSITION
Time
22
Inception Phase
 Focused on Understanding the business
case for the project,scope and feasibility
of an implementation.
 Problem analysed
 Vision for solution– created
 Estimation for Schedule,Budget and
Risk done.
Elaboration Phase
 Requirements -Refined
 Architecture established
 Feasibility prototype developed &
demonstrated
Construction Phase
 Implementation
 Coding
 Architecture and Design fully developed
Transition Phase
 Beta testing
 Users/ maintainers trained on the
application
 Given to user community for usage.
 Project undergoes multiple iterations

within each phase.
Iterations
 An iteration is a sequence of activities
with an established plan and evaluation
criteria, resulting in an executable of
some type.
 Each Iteration is designed to mitigate

risks in that stage of during
development.
Disciplines
 The activities associated with the
development of the s/w are organized into
set of disciplines.
 Each discipline consists of a logically
related set of activities and each defines
how the activities must be sequenced to
produce a viable work product.
 In each iteration, the team spends as much
time as appropriate in each discipline.
Disciplines of the Iterative approach
Mini-waterfall
 An iteration can be regarded as mini-
waterfall through the activities of
requirements, analysis ,design and so
on.
 It is tuned to the specific needs of that
iteration.
Advantages:
 Better adaptability to requirements
change
 Better scope management

Reference For Unified Process-Iterative Model Only

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Reference For Unified Process-Iterative Model Only

Uploaded by

Copyright:

Available Formats

REQUIREMENTS ENGINEERING

Prof. R.Kiruba Thangam

It provides a sensible road map that helps address some

Development is initially driven by a series of risk driven

Starts with requirements planning and concept

 Availability of multiple feedback

 The iterative approach introduced by

 Allows us to revisit various activities like

INCEPTION ELABORATION CONSTRUCTION TRANSITION

 Project undergoes multiple iterations

 Each Iteration is designed to mitigate

You might also like