phased-release model | - It suggests that all requirements be finalized at the start of development
- It downplays the importance of prototyping
| the use of incremental development | that after requirements gathering and planning, the project should be broken into separate subprojects, or phases which can be released to customers when ready | An approach to incremental development in which, after requirements gathering and planning, the project is broken into separate subprojects, or phases | some, but not all, of the problems of the waterfall model | | process model |