Classical Waterfall Model
Feasibility Study
- Schedule feasibility
- Economic feasibility
- Technical feasibility
A deep understand of the resource required during the development, the time that will be taken for completion and the overall cost of development.
Perform a cost/benefit analysis on the solution laid out for the problem.
Effective Business Case
- Project background
- Busine
ss opportunity - Costs
- Benefits
- Risks
Requirement Analysis
Understand the requirements of the customer
Gather all the requirements, remove inconsistencies and organise into Software Requirements Specification
Design Phase
During the design phase, the requirement specifications are considered, and we come up with an implementation idea.
Two methods - Traditional and Object Oriented Design
→ Traditional - Structured analysis - Structured design - High level design + detailed design
Classic waterfall is idealistic, assumes no defects introduced in development stages
Advantages
- Simple
- Milestones are well understood
- Requirements are well defined
Disadvantages
- Requirements must be well defined
- Linear and Sequential
- No preview
- Cannot accommodate changes easily.