CST 438 Week 7 Learning Journal
Agile & PD Comparison
When engineering software for a customer, a team can use a variety of different methods to bring the software to life. Two of these methods are the Agile method and the Plan and Document (PD) method. While they both can help develop software to meet the needs of a customer, their processes differ in various ways.
The Agile method uses iteration to develop the software in short cycles and involves continuous customer interaction, which allows for flexibility in change. The design of the software evolves as iterations are completed. Its documentation is in the form of stories written using Behavior Driven Development (BDD), meaning that the stories describe how the user will interact with the software.
In contrast, PD is more of a sequential process and flows more like a waterfall rather than in iterations. While the PD method also uses BDD for its use cases, it focuses on heavy documentation and involves less frequent customer interaction than the Agile method. In this method, a Software Design Document (SDD) is created before the coding begins. The software is detailed heavily in the SDD, which means that any change after the SDD is finalized would involve substantial rework, making it costly in time and resources.
Comments
Post a Comment