Please enable JavaScript.
Coggle requires JavaScript to display documents.
SDLC Methodologies (Waterfall Model (Cons (Inflexible, Heavy on…
SDLC Methodologies
Waterfall Model
Initiation
Req. Analysis
Design
Implementation
Testing
Deployment & Maintaince
Each step cannot begin until the previous step has been completed and documented
Document-driven
Pros
easy to understand
good on documentation
Quality build in
Cons
Inflexible
Heavy on documentation
Slow
Lack of user involvement - cannot get feedback from users early enough
When to use
Clear and fixed requirements
Product definition is stable
Technology is understood
Ample resources with required expertise are available
V Model
Pros
Easy to use
Promotes testing
Avoids defects flowing down the stages
Cons
Inflexible
Heavy on documenation
Slow
Lacks of user involvement-
No prototypes, very high risk involved in meeting customers expectations
When to Use
Clear and fixed requirements
When high customer confidence is required
Ample resources with required expertise are available
Business Requirements
Interface Specifcation
System Specification
Design Specification
Low Level Design (component specification)
SourceCode/Object Code
Component testing
Component integration testing
1 more item...
Incremental/Phased Delivery
Pros
Early vision of the sytems
Customer feedback
reduces complexity
Cons
Needs a clear, complete definition of the whole system, but it can be broken down and built imcrementally
Difficult to manage
Needs good planning
When to use
Requirements of the complete system are clearly defined and understood.
Need to get product to market early
when new technology is being used (reduce the risk)
Required skill set not available
Spiral Model
Prototyping