In Royce's original waterfall model, the following phases are followed in order:
System and software requirements: captured in a product requirements document
Analysis: resulting in models, schema, and business rules
Design: resulting in the software architecture
Coding: the development, proving, and integration of software
Testing: the systematic discovery and debugging of defects
Operations: the installation, migration, support, and maintenance of complete systems
Thus the waterfall model maintains that one should move to a phase only when its preceding phase is reviewed and verified.
Various modified waterfall models (including Royce's final model), however, can include slight or major variations on this process.[3] 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.
In Royce's original waterfall model, the following phases are followed in order:System and software requirements: captured in a product requirements documentAnalysis: resulting in models, schema, and business rulesDesign: resulting in the software architectureCoding: the development, proving, and integration of softwareTesting: the systematic discovery and debugging of defectsOperations: the installation, migration, support, and maintenance of complete systemsThus the waterfall model maintains that one should move to a phase only when its preceding phase is reviewed and verified.Various modified waterfall models (including Royce's final model), however, can include slight or major variations on this process.[3] 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.
การแปล กรุณารอสักครู่..