Summarize in a few sentences what you have learned this week.
In this week’s readings we learned about some of the differences between the Waterfall and Agile development philosophies, and in particular, how each has a unique perspective on how documentation should be used.
The Waterfall model tends to view the software development cycle in a rigid manner – the client produces a specifications document that details what they want out of a system; the developers interpret this specification document to determine which features are desired, why they are desired, and if they are feasible; and then a requirements specification document is created to more formally define the system-to-be-built.
The Agile model, on the other hand, interprets this sequence of client specifications → developer analysis → requirements specification within a looser framework. One of the core ideas of Agile is that it is impossible to define every aspect of what a system should do upfront. In this way, Agile focuses much more on an iterative process, where progress is made towards building the system, and this progress is reevaluated periodically to ensure that all the desired outcomes are being achieved, and that said outcomes truly satisfy the requirements of the client.
No comments:
Post a Comment