Most medium and large projects will include a detailed set of procedures and controls, which regulate every process on the project. The actual project organization needs to be highly structured. In common practice, waterfall methodologies result in a project schedule with 20–40% of the time invested for the first two phases, 30–40% of the time to coding, and the rest dedicated to testing and implementation. For example, a problem found in the early stages (such as requirements specification) is cheaper to fix than the same bug found later on in the process (by a factor of 50 to 200). Time spent early in the software production cycle can reduce costs at later stages. These variations included returning to the previous cycle after flaws were found downstream, or returning all the way to the design phase if downstream phases deemed insufficient. Various modified waterfall models (including Royce's final model), however, can include slight or major variations on this process. Thus the waterfall model maintains that one should move to a phase only when its preceding phase is reviewed and verified.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |