|Reference||/Scacchi, 2001/ Process Models in Software Engineering|
Incremental Development and Release:|
Developing systems through incremental release requires first providing essential operating functions, then providing system users with improved and more capable versions of a system at regular intervals /Basili, 1975/. This model combines the classic software life cycle with iterative enhancement at the level of system development organization. It also supports a strategy to periodically distribute software maintenance updates and services to dispersed user communities. This in turn accommodates the provision of standard software maintenance contracts. It is therefore a popular model of a software evolution used by many commercial software firms and system vendors. This approach has also been extended through the use of software prototyping tools and techniques, which more directly provide support for incremental development and iterative release for early and ongoing user feedback and evaluation /Graham, 1989/.
Elsewhere, the Cleanroom software development method at use in IBM and NASA laboratories provides incremental release of software functions and/or subsystems (development through stepwise refinement) to separate in-house quality assurance teams that apply statistical measures and analyses as the basis for certifying high-quality software systems /Selby, 1987/, /Mills, 1987/.
|Rationales||The author classifies Incremental Development as one of the traditional software life cycle models|
|Reference||/VM 1997/ V-Model 97, Lifecycle Process Model.|
Synonym: Incremental Prototyping
Incremental development of a System (or of system parts) on the basis of on the whole known user requirements.
|GDPA Online Last Updated 02.May.2002 Updated by Webmaster Last Revised 02.May.2002 Revised by Webmaster|