cst 438: week 7

This week I learned the differences between Agile and Plan & Document (Waterfall) processes.

Agile is iterative. Work happens in short cycles that include requirements, design, coding, and testing. Requirements can change between iterations, so the system evolves over time. It focuses on working software over heavy documentation, and testing is continuous throughout development.

Plan & Document is linear. It follows fixed phases, which are requirements (SRS), design (UML, database, architecture), implementation, testing, deployment, and maintenance. Everything is planned upfront, and requirements are expected to be complete before development starts.

I also learned that PD relies heavily on documentation like SRS, ER diagrams, class diagrams, and project plans. Agile uses lighter documentation and more direct communication styles.

A key difference between both of them is handling change and iterations. In Agile, change is expected and easier to manage. In PD, changes after the requirements phase are costly in terms of resources because they tend to impact design, code, and testing overall. Also, PD tends to give clearer upfront estimates for time and cost, while Agile works on ongoing estimates per sprint and doesn’t lock in a full timeline early.