Statements (58)
| Predicate | Object |
|---|---|
| gptkbp:instanceOf |
software
|
| gptkbp:benefits |
easy to manage
inflexible to changes late testing simple to understand |
| gptkbp:canLeadTo |
cost overruns
project delays |
| gptkbp:characterizedBy |
sequential phases
|
| gptkbp:developedBy |
Winston_W._Royce
|
| gptkbp:emphasizes |
design
planning documentation |
| gptkbp:firstIntroduced |
1970
|
| gptkbp:future_plans |
deployment
maintenance system design implementation requirements analysis integration and testing |
| https://www.w3.org/2000/01/rdf-schema#label |
Waterfall model
|
| gptkbp:is_used_in |
construction projects
government projects manufacturing projects |
| gptkbp:isAttendedBy |
government agencies
engineering firms software companies consulting firms many organizations |
| gptkbp:isBasedOn |
linear progression
|
| gptkbp:isCriticizedFor |
lack of flexibility
overemphasis on documentation potential for scope creep assumption of clear requirements difficulty in accommodating changes underestimating user feedback |
| gptkbp:isEvaluatedBy |
customer satisfaction
on-time delivery budget adherence project success metrics |
| gptkbp:isFoundIn |
hardware development
system engineering traditional software engineering |
| gptkbp:isNotableFor |
projects with uncertain requirements
|
| gptkbp:isOftenUsedIn |
academic settings
training programs project management courses |
| gptkbp:isRecognizedFor |
small projects
rapidly changing projects |
| gptkbp:isSupportedBy |
project management tools
Gantt charts PERT charts |
| gptkbp:relatedTo |
V-Model
Agile methodology Spiral model |
| gptkbp:requires |
complete requirements upfront
user involvement during requirements phase |
| gptkbp:usedIn |
large projects
projects with clear requirements |