business analysis – level ii software development life cycle
DESCRIPTION
Business Analysis – Level II SOFTWARE DEVELOPMENT LIFE CYCLE. CONCEPT: software development life cycle ( sdlc ). Engineering?. “ Creation ” + “Approach for re-creation ” Approach defines Who Does What When and How. PROCESS. “Creation of software ” + “Approach for its re-creation ” - PowerPoint PPT PresentationTRANSCRIPT
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
© 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 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 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 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 Processes
© 2011 BA ValueBASE LLP
Requiremen ts
InitialPlanning
Planning
Analysis & Design
Implementation
Deployment
Test
Evaluation
Manag ementEnviro nment
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 xDx : Design for use case xCx : Coding for use case xTx : 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
ComparisonRequiremen ts
InitialPlanning
Planning
Analysis & Design
Implementation
Deployment
Test
Evaluation
Manag ementEnviro nment
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 T4T1 T2 T3
T1 T2T1
Time >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Test Automation
ComparisonRequiremen ts
InitialPlanning
Planning
Analysis & Design
Implementation
Deployment
Test
Evaluation
Manag ementEnviro nment
Iterative Process
Code and unit test
Design
Subsystem integration
System test
Traditional Waterfall ProcessRequirements analysis
© 2011 BA ValueBASE LLP
Requirements
InitialPlanning
PlanningAnalysis & Design
Implementation
Deployment
Test
Evaluation
ManagementEnvironment
Iterative Process
What is it NOT?Risk based approach!!!
GREAT PROCESSTHEN 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 CentricSoftware 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
PreliminaryIteration
ArchitectureIteration #1
Architecture Iteration #2
Development Iteration #1
Development Iteration #2
Development Iteration #3
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 Iterations
© 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 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 Phases
© 2011 BA ValueBASE LLP
CONCEPT: BASICS OF AGILE
© 2011 BA ValueBASE LLP
Agile Manifesto
Definitely Valuable
More Valuable
© 2011 BA ValueBASE LLP
Guiding 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 project5. Build projects around motivated individuals. Give them the environment and support they
need, and trust them to get the job done6. 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 agility10.Simplicity--the art of maximizing the amount of work not done--is essential11. 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
© 2011 BA ValueBASE LLP
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
© 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 ASSESSTo 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 ASSESSEnterprise 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
BABO
K V2
.0 K
NO
WLE
DG
E AR
EAS
CONSISTENT PREDICTABLE ITERATIVE
© 2011 BA ValueBASE LLP24
Thank You