BUSINESS ANALYST TRAINING

Feb - 2014
 DAY 2
System Development Life Cycles

 Waterfall Model

 V Shaped Model

 Incremental Model

 Spiral Model
WATERFALL MODEL
1. Requirement Analysis 4. Integrate

2. Design 5. Test

3. Code 6. Deploy
WATERFALL STRENGTHS & WEAKNESSES
Strengths: Weaknesses:
 Easy to Understand & Use  Know all Requirements

 Good for Inexperienced Staff  Frozen Deliverables

 Well Understood Milestones  False Impressions

 Requirements Stability  Doesn’t Support Changes

 Better Management Control  No Customer Reviews

 Quality Focused  All Integrations at the end

 Increases Cost & Schedule

WHEN TO USE WATERFALL
 Requirements are very well known

 Things are stable

 Technology is understood

 Requirement of a new version

 Porting / Migrating an existing product

V MODEL
V MODEL STRENGTHS & WEAKNESSES
Strengths: Weaknesses:
 Simple and Easy  Very rigid and inflexible

 Early Planning & Designing

 No prototypes
 Higher chances of success
 No Customer Involvement
 Proactive Defect Tracking
 Changes are costly
 Avoids flowing of the defects

 Better for small projects

WHEN TO USE V MODEL
 Requirements are very well known

 Experienced staff is available

 High confidence of customer

 Porting / Migrating an existing product

INCREMENTAL MODEL
INCREMENTAL MODEL STRENGTHS & WEAKNESSES
Strengths: Weaknesses:
 Quick and Early  Requires good planning

 More Flexible
 Requires good designing
 Less Costly
 Clear vision of system
 Accommodate changes

 Easier to Test and Debug  Total Cost > Waterfall

 Customer Involvement

 Lowers Delivery Cost

 Risk Management is easier

WHEN TO USE INCREMENTAL MODEL
 Requirements are very well known

 Fewer requirements are not clear

 Inexperienced Staff

 Time is less

 Adopting a new technology

 High risk is associated with system and goals

SPIRAL MODEL (PROTOTYPING + ITERATIVE)
SPIRAL APPROACH PHASES
 Customer Communication

 Planning

 Risk Analysis

 Requirement Gathering & System Design

 Development & Releases

 Customer Evaluation & Feedback

SPIRAL STRENGTHS & WEAKNESSES
Strengths: Weaknesses:
 Early indication of risks  Requires more time

 Better visibility
 Time Planning
 Rapid Prototyping
 Objectives Resetting
 Requirement Prioritization

 Defects can be tolerable  Risk Analysis

 User can be involved

 Complex at times
 Frequent user feedback
 Resource availability
 Costs can be reduced
WHEN TO USE SPIRAL
 Prototyping is required

 Cost & Risk Evaluation is important

 Average to High Risk projects

 Long Term projects due to potential changes

 Unclear vision for requirements

 Requirements are complex

 Overall new product development

 Users are not sure about requirements

 Major changes are expected

THANK YOU