النتائج (
الإنجليزية) 3:
[نسخ]نسخ!
Waterfall development methodologies have the advantages of identifyingRequirements long before programming begins and limiting changes to the requirementsAs the project proceeds. The key disadvantages are that the design must beCompletely specified before programming begins, a long time elapses between theCompletion of the system proposal in the analysis phase and the delivery of systemAnd testing is treated almost as an afterthought in the implementation phase. In additionThe deliverables are often a poor communication mechanism, so importantRequirements may be overlooked in the volumes of documentation. If the project teamMisses an important requirement, expensive post-implementation programming mayBe needed. Users may forget the original purpose of the system, since so much timeHas elapsed between the original idea and actual implementation. Also, in today sDynamic business environment, a system that met the existing environmental conditionsDuring the analysis phase may need considerable rework to match the environmentWhen it is implemented. This rework requires going back to the initial phase andMaking needed changes through each of the subsequent phases in turn.
يجري ترجمتها، يرجى الانتظار ..
