CONFIDENTIALITY

2010 BA ValueBASE LLP, The concepts and

methodologies contained herein are proprietary to BA

ValueBASE LLP. Duplication, reproduction or disclosure of

information in this document without the express written

permission of BA ValueBASE LLP is prohibited.

Software Development

Life Cycle

2011 BA ValueBASE LLP

Learning Objective

What are different Software Development Life Cycles (SDLC)

What are their Pros and Cons

What is Rational Unified Process (RUP)

How it RUP beneficial

2011 BA ValueBASE LLP

Software Development Processes

Iterative Process

Rational Unified Process (RUP)

RUP Phases & Iterations

RUP Disciplines - Bus. Modeling and Requirements

Agenda

2011 BA ValueBASE LLP

CONCEPT: SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)

2011 BA ValueBASE LLP

Creation + Approach for re-creation

Approach defines

Who

Does What

When and

How

PROCESS

Creation of software + Approach for its re-creation

Approach defines

Who - Role

Does What - Activity

When Workflow and

How - Guideline

SOFTWARE ENGINEERING PROCESS

Engineering?

2011 BA ValueBASE LLP

Code and unit test

Design

Subsystem integration

System test

Traditional Waterfall Process

Requirements analysis

V-Process Pitfalls

Define all the requirements before development starts

Customer sees the product only at the end !!

Results in expensive overruns and possible cancellation

Resource loading a big issue

Changes in requirements tough to accommodate; unplanned iterations!!

Late discovery of serious project flawsfunctionality, performance, etc.

Measures progress by assessing work-products that are poor predictors of time-to-completion

Delays and aggregates integration and testing

Software Engineering Processes

2011 BA ValueBASE LLP

Requirements

InitialPlanning

Planning

Analysis & Design

Implementation

Deployment

Test

Evaluation

ManagementEnvironment

Iterative Process

Each iteration results in an

executable release

What?

Based on Barry Boehms Spiral Model

Process consists of a sequence of incremental steps, or iterations.

Each iteration has all of the development disciplines (requirements, analysis, design, implementation, etc.)

Each iteration also has a well-defined set of objectives.

Each iteration produces a partial working implementation of the final system.

Successive iteration builds on the work of previous iterations to evolve and refine the system until the final product is complete.

Software Engineering Processes

2011 BA ValueBASE LLP

Requirements

InitialPlanning

Planning

Analysis & Design

Implementation

Deployment

Test

Evaluation

Management

Environment

Iterative Process

Code and unit test

Design

Subsystem integration

System test

Traditional Waterfall ProcessRequirements analysis

Waterfall R1 R2 R3 R4 D1 D2 D3 D4 C1 C2 C3 C4 T1 T2 T3 T4

Iterative R1 D1 C1 T1 R2 D2 C2 T2 R3 D3 C3 T3 R4 D4 C4 T4

Time >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Legend:

Rx : Requirement for use case x

Dx : Design for use case x

Cx : Coding for use case x

Tx : Testing for use case x

Comparison

2011 BA ValueBASE LLP

Architecture Validation

Waterfall R1 R2 R3 R4 AD D1 D2 D3 D4 C1 C2 C3 C4 T1 T2 T3 T4

Iterative R1 AD D1 C1 T1 R2 D2 C2 T2 R3 D3 C3 T3 R4 D4 C4 T4

Time >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Architecture problems identified

Comparison

Requirements

InitialPlanning

Planning

Analysis & Design

Implementation

Deployment

Test

Evaluation

Management

Environment

Iterative Process

Code and unit test

Design

Subsystem integration

System test

Traditional Waterfall ProcessRequirements analysis

2011 BA ValueBASE LLP

Waterfall R1 R2 R3 R4 AD D1 D2 D3 D4 C1 C2 C3 C4 T1 T2 T3 T4

Iterative R1 AD D1 C1 T1 R2 D2 C2 T1 T2 R3 D3 C3 T1 T2 T3 R4 D4 C4 T1 T2 T3 T4

Time >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Testing

Waterfall R1 R2 R3 R4 AD D1 D2 D3 D4 C1 C2 C3 C4 T1 T2 T3 T4

Iterative R1 AD D1 C1 T1 R2 D2 C2 T2 R3 D3 C3 T3 R4 D4 C4 T4

T1 T2 T3

T1 T2

T1

Time >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Test Automation

Comparison

Requirements

InitialPlanning

Planning

Analysis & Design

Implementation

Deployment

Test

Evaluation

Management

Environment

Iterative Process

Code and unit test

Design

Subsystem integration

System test

Traditional Waterfall ProcessRequirements analysis

2011 BA ValueBASE LLP

Requirements

InitialPlanning

Planning

Analysis & Design

Implementation

Deployment

Test

Evaluation

ManagementEnvironment

Iterative Process

What is it NOT?

Risk based approach!!!

GREAT PROCESS

THEN WHY RUP?

Processes

2011 BA ValueBASE LLP

CONCEPT: RATIONAL UNIFIED PROCESS (RUP)

2011 BA ValueBASE LLP

What is RUP?

It is an

Iterative

Use Case Driven

Architecture Centric

Software development process

Defines

9 Disciplines, each with

Detailed Workflow and Activities

Performed by specific Roles

Producing specific Artifacts

4 Phases, each having n iterations

RISK based approach

Rational Unified Process

2011 BA ValueBASE LLP

RUP Best Practices

Develop Iteratively

Manage Requirements

Use Component Architecture

Model Visually

Continuously Verify Quality

Manage Change

Rational Unified Process

2011 BA ValueBASE LLP

In an iteration,

you walk

through

all disciplines.

Rational Unified Process

2011 BA ValueBASE LLP

CONCEPT: RUP PHASES AND ITERATIONS

2011 BA ValueBASE LLP

Planned (Technical) Visibility Points

INCEPTION ELABORATION CONSTRUCTION TRANSITION

Preliminary

Iteration

Architecture

Iteration #1

Architecture

Iteration #2

Development

Iteration #1

Development

Iteration #2

Development

Iteration #3

Transition

Iteration #1

Transition

Iteration #2

Acceptance

or End of LifeProduct Sufficiently

Mature for Customers

to Use

(Build the solution)

Architectural Baseline

(Understand the solution)

Scope and Business

Case Agreement

(Understand the problem)

Planned (Business) Decision Points

RUP Phases and Iterations

2011 BA ValueBASE LLP

Inception Phase Get In

Identify Stakeholders

Define the problem obtain concurrence from stakeholders

Establish Projects scope - obtain concurrence from stakeholders

Identify high level requirements - obtain concurrence from stakeholders

Identify potential project risks and their mitigation

Define candidate system architecture

Estimate cost and schedule - obtain concurrence from stakeholders

Set Up supporting environment for the project, e.g. hardware, software, resources, etc.

RUP Phases

2011 BA ValueBASE LLP

Elaboration Phase Get Smart

Validate and baseline Vision and Requirements

Validate (POC) and baseline System Architecture

Refine Environment

Baseline detailed plan for Construction Phase

RUP Phases

2011 BA ValueBASE LLP

Construction Phase Get IT Done

Achieve adequate quality

Achieve useful versions of the application

Minimize development costs by optimizing resources

RUP Phases

2011 BA ValueBASE LLP

Transition phase Get OUT

Achieve user self supportability

Achieve Stakeholder concurrence that deployment baselines are complete and consistent with the evaluation criteria of the vision

Achieve final product baseline in a rapid and cost effective manner

RUP Phases

2011 BA ValueBASE LLP

Inception - What to build, Who wants it, Why do they want it, What value does it provides to them

Elaboration - Address projects highest risks, Demonstrate technical feasibility

Construction - Build software, Deliver working software to the customer at end of each iteration within construction phase

Transition - Prepare to deploy software, Develop Documentation, Training, Customer support

Inception Elaboration Construction Transition

Lifecycle Objective Milestone

Lifecycle Architecture

Milestone

Initial Operational Capability Milestone

Product Release

time

RUP Phases

2011 BA ValueBASE LLP

CONCEPT: APPROACH TO REQUIREMENTS ENGINEERING

2011 BA ValueBASE LLP

ValueREAPER Requirements Engineering Approach for Predictable and Enhanced Results

PLAN DISCOVER SCOPE DETAIL REVIEW TRANSITION ASSESS

To plan the BA Approach

Artifacts: Requirements Management Plan

Interfaces: Sponsor, EA, PM

To understand Business Needs

Artifacts: Process Maps, Problem Statement, Prioritized Business Requirements

Interfaces: SMEs, EA/SA, PM

To develop Solution Reqs.

Artifacts:Pr. SH Reqs., Scope Model, Use Case Model, Domain Model, Traceability Matrix

Interfaces: SMEs, Users, IA, SA, DA, PM

To detail Solution Reqs.

Artifacts: Pr. Soln. Reqs. Use Cases, UI Design, Bus. Rules, Reports Traceability Matrix

Interfaces: SMEs, IA, DA, PM

To verify & validate Solution Reqs.

Artifacts: Review Log, Sign Off Record

Interfaces: Sponsor, SMEs, PM

To transition Impl. team

Artifacts: Issue Log, Traceability Matrix

Interfaces: PM, IA, DA, SA, TL, Dev, QA

To validate developed solution

Artifacts: Change Request Tracker, Impact Analysis, Acceptance Criteria

Interfaces: SMEs, QA, TL, Dev, PM

UNDERLYING BA COMPETENCIES

CONSISTENT PREDICTABLE ITERATIVE

2011 BA ValueBASE LLP

ValueREAPER BABOK V2.0 Alignment

PLAN DISCOVER SCOPE DETAIL REVIEW TRANSITION ASSESS

Enterprise Analysis

Elicitation

Business Analysis Planning and Monitoring

Enterprise Analysis

Elicitation

Business Analysis Planning and Monitoring

Enterprise Analysis

Elicitation

Req.Analysis

Req. Management and Comm.

Elicitation

Req.Analysis

Req. Management and Comm.

Elicitation

Req.Analysis

Req. Management and Comm.

Elicitation

Req.Analysis

Req. Management and Comm.

Solution Assessment and Validation

Elicitation

Req.Analysis

Req. Management and Comm.

Solution Assessment and Validation

UNDERLYING BA COMPETENCIES

BA

BO

K V

2.0

KN

OW

LED

GE A

REA

S

CONSISTENT PREDICTABLE ITERATIVE

2011 BA ValueBASE LLP26

Thank You