Class waterfall
Upcoming SlideShare
Loading in...5
×
 

Class waterfall

on

  • 425 views

 

Statistics

Views

Total Views
425
Views on SlideShare
425
Embed Views
0

Actions

Likes
0
Downloads
8
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Class waterfall Class waterfall Presentation Transcript

  • Waterfall Model
  • Waterfall Model SDLC approach Became popular in 1970 Phases are organised in Linear Order Output of one phase is input for next phase
  • Waterfall Model Phases  Proposal Definition  Feasibility Study  Requirements Analysis  System Design  Coding & Testing  Implementation  System Maintenance
  • Waterfall Model Proposal Definition Feasibility Study R equirements Analysis S ystem Design Coding & Testing Implementation System maintenance
  • Strengths of Waterfall Model Easy to understand, easy to use Systematic for inexperienced staff Milestones are well understood
  • Strengths of Waterfall Model Sets requirements stability Good for management control (plan, staff, monitor, control) Works well when quality is more important than cost or schedule
  • Limitations-Waterfall Model Every phase is considered as a distinct phase All requirements must be known before hand Deliverables created for each phase are considered frozen – reduces flexibility
  • Limitations-Waterfall Model Can give a false impression of progress Little opportunity for customer to preview the system (until it may be too late)
  • Limitations-Waterfall Model  For a new system determining requirements is a difficult job  So freezing requirements before design is not practical  Might be desirable to built only a part of it  Later enhance as and when needed
  • Limitations-Waterfall Model Freezing requirements requires choice of H/W In large projects, technology changes when the system is completed
  • Limitations-Waterfall Model Difficulty of accommodating change after the process is underway One phase has to be complete before moving onto the next phase Integration is one big bang at the end
  • Limitations-Waterfall Model  Inflexible partitioning of the project into distinct stages makes it difficult to change as per customer requirements.  Requirements should be well-understood so that changes are fairly limited during the design process
  • When to use? Requirements are very well known Product definition is stable Technology is understood
  • When to use? New version of an existing product Porting an existing product to a new platform.
  • Thank You!!