Statements (60)
| Predicate | Object |
|---|---|
| gptkbp:instance_of |
gptkb:Software_Development
|
| gptkbp:benefits |
easy to manage
inflexible to changes late testing simple to understand |
| gptkbp:characterized_by |
sequential phases
|
| gptkbp:developed_by |
gptkb:Winston_W._Royce
|
| gptkbp:emphasizes |
gptkb:Documentation
|
| gptkbp:first_introduced |
gptkb:1970
|
| https://www.w3.org/2000/01/rdf-schema#label |
Waterfall model
|
| gptkbp:is_associated_with |
traditional project management
|
| gptkbp:is_based_on |
linear progression
|
| gptkbp:is_compared_to |
gptkb:Agile_methodology
gptkb:Spiral_model |
| gptkbp:is_criticized_for |
lack of flexibility
overemphasis on documentation potential for scope creep assumes requirements are well understood delayed delivery of product difficulties in accommodating changes lack of iterative feedback loops not accommodating user feedback risk of project failure |
| gptkbp:is_documented_in |
design documents
test plans project management plans requirements specifications |
| gptkbp:is_evaluated_by |
customer satisfaction
quality of deliverables time to market budget adherence project success rate |
| gptkbp:is_often_accompanied_by |
lessons learned
post-mortem analysis |
| gptkbp:is_part_of |
software engineering practices
project management methodologies |
| gptkbp:is_tested_for |
deployment
maintenance system design implementation requirements analysis integration and testing |
| gptkbp:is_used_in |
construction projects
manufacturing industries healthcare projects government projects telecommunications projects defense projects aerospace projects |
| gptkbp:originated_in |
software engineering
|
| gptkbp:requires |
complete requirements upfront
|
| gptkbp:suitable_for |
dynamic projects
non-iterative projects projects with evolving requirements |
| gptkbp:used_in |
large projects
projects with clear requirements |
| gptkbp:bfsParent |
gptkb:ISO/_IEC_24744
gptkb:UML_1.0 gptkb:Agile_Manifesto |
| gptkbp:bfsLayer |
6
|