confidentiality © 2010 ba valuebase llp, the concepts and methodologies contained herein are...

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.

Business Analysis – Level II

SOFTWARE DEVELOPMENT LIFE CYCLE

Business Analysis – Level II

SOFTWARE DEVELOPMENT LIFE CYCLE

© 2011 BA ValueBASE LLP

CONCEPT: SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)

CONCEPT: SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)


“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?Engineering?


Code and unit test

Design

Subsystem integrationSubsystem integration

System test

Traditional Waterfall Process

Requirements analysis 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 flaws–functionality, performance, etc.

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

Delays and aggregates integration and testing

Software Engineering ProcessesSoftware Engineering Processes


Requirements

InitialPlanning

Planning

Analysis & Design

Implementation

Deployment

Test

Evaluation

ManagementEnvironment

Iterative Process

Each iteration results in an

executable release

What? Based on Barry Boehm’s 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 ProcessesSoftware Engineering Processes


Requirements

InitialPlanning

Planning

Analysis & Design

Implementation

Deployment

Test

Evaluation

Management

Environment

Iterative Process

Code and unit test

Design


System test

Traditional Waterfall ProcessRequirements analysis

Requirements 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

ComparisonComparison


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

ComparisonComparisonRequiremen

ts

InitialPlanning

Planning

Analysis & Design

Implementation

Deployment

Test

Evaluation

Management

Environment

Iterative Process

Code and unit test

Design


System test





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


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

T1 T2T1

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

Test Automation

ComparisonComparisonRequiremen

ts

InitialPlanning

Planning

Analysis & Design

Implementation

Deployment

Test

Evaluation

Management

Environment

Iterative Process

Code and unit test

Design


System test




Requirements

InitialPlanning

Planning

Analysis & Design

Implementation

Deployment

Test

Evaluation

ManagementEnvironment

Iterative Process

What is it NOT?

Risk based approach!!!

GREAT PROCESS

THEN WHY RUP?

ProcessesProcesses


CONCEPT: RATIONAL UNIFIED PROCESS (RUP)

CONCEPT: RATIONAL UNIFIED PROCESS (RUP)


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 ProcessRational Unified Process


RUP Best Practices Develop Iteratively Manage Requirements Use Component Architecture Model Visually Continuously Verify Quality Manage Change



In an iteration, you walk through all disciplines.



CONCEPT: RUP – PHASES AND ITERATIONSCONCEPT: RUP – PHASES AND ITERATIONS


Planned (Technical) Visibility Points

INCEPTION ELABORATION CONSTRUCTION TRANSITION

PreliminaryIteration

ArchitectureIteration #1

Architecture Iteration #2

Development Iteration #1



TransitionIteration #1

TransitionIteration #2

Acceptanceor End of Life

Product 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 IterationsRUP Phases and Iterations


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

Elaboration - Address project’s 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 PhasesRUP Phases


CONCEPT: BASICS OF AGILECONCEPT: BASICS OF AGILE


Agile ManifestoAgile Manifesto

Definitely Valuable

More Valuable


Guiding Principles behind Agile ManifestoGuiding Principles behind Agile Manifesto1. Our highest priority is to satisfy the customer through early and continuous delivery of

valuable software

2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage

3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale

4. Business people and developers must work together daily throughout the project

5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done

6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation

7. Working software is the primary measure of progress

8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely

9. Continuous attention to technical excellence and good design enhances agility

10.Simplicity--the art of maximizing the amount of work not done--is essential

11. The best architectures, requirements, and designs emerge from self-organizing teams

12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly


Where does Agile Fit?Where does Agile Fit?

Agile works well with complicated,complex projects that need to adapt to changes

Waterfall works with well defined and unchanging projects


CONCEPT: APPROACH TO REQUIREMENTS ENGINEERING

CONCEPT: APPROACH TO REQUIREMENTS ENGINEERING


ValueREAPER – Requirements Engineering Approach for Predictable and Enhanced ResultsValueREAPER – 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


ValueREAPER – BABOK V2.0 AlignmentValueREAPER – 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


Elicitation

Req.Analysis


Elicitation

Req.Analysis


Solution Assessment and Validation

Elicitation

Req.Analysis


Solution Assessment and Validation

UNDERLYING BA COMPETENCIES

BA

BO

K V

2.0

KN

OW

LED

GE A

REA

S

CONSISTENT PREDICTABLE ITERATIVE

confidentiality © 2010 ba valuebase llp, the concepts and methodologies contained herein are...

Documents

e n t enviro n

ba valuebase llp code

e n t iterative process

ba valuebase llp concept

use case x comparison

requirements tough

business analysis level

final system