Many industries use variations on these project stages. For example, when working on a brick and mortar design and construction, projects will typically progress through stages like Pre-Planning, Conceptual Design, Schematic Design, Design Development, Construction Drawings (or Contract Documents) and Construction Administration.
In software development, this approach is often known as the waterfall model. For example, one series of tasks after another in linear sequence. In software development many organisations have adapted the Rational Unified Process (RUP) to fit this methodology, although RUP does not require or explicitly recommend this practice.
Waterfall development works well for small, well-defined projects, but often fails in larger projects of undefined and ambiguous nature. The Cone of Uncertainty explains some of this as the planning made on the initial phase of the project suffers from a high degree of uncertainty. This becomes especially true as software development is often the realisation of a new or novel product.
In projects where requirements have not been finalized and can change, requirements management is used to develop an accurate and complete definition of the behavior of software that can serve as the basis for software development.
While the terms may differ from industry to industry, the actual stages typically follow common steps to problem solving - "defining the problem, weighing options, choosing a path, implementation and evaluation."
In software development, this approach is often known as the waterfall model. For example, one series of tasks after another in linear sequence. In software development many organisations have adapted the Rational Unified Process (RUP) to fit this methodology, although RUP does not require or explicitly recommend this practice.
Waterfall development works well for small, well-defined projects, but often fails in larger projects of undefined and ambiguous nature. The Cone of Uncertainty explains some of this as the planning made on the initial phase of the project suffers from a high degree of uncertainty. This becomes especially true as software development is often the realisation of a new or novel product.
In projects where requirements have not been finalized and can change, requirements management is used to develop an accurate and complete definition of the behavior of software that can serve as the basis for software development.
While the terms may differ from industry to industry, the actual stages typically follow common steps to problem solving - "defining the problem, weighing options, choosing a path, implementation and evaluation."
