Agile Modeling
- The purpose of modeling (sketching UML, …) is primarily to understand, not to
- document.
- It implies a number of practices and values, including:
- – Adopting an agile method does not mean avoiding any modeling. Many agile methods, such as Feature-Driven Development, Dynamic systems development method (DSDM), and Scrum, normally include significant modeling sessions.
- – The purpose of modeling and models is primarily to support understanding and communication, not documentation
- – Don’t model or apply the UML to all or most of the software design.
- – Use the simplest tool possible
- – Don’t model alone, model in pairs (or triads)
- – Create models in parallel.
- – Know that all models will be inaccurate, and the final code or design different sometimes dramatically different—then the model. Only tested code demonstrates the true design
- – Use “good enough” simple notation
- – Developers themselves should do the OO design modeling
No comments:
Post a Comment