CSC 532 Term Paper Presentation TOPIC Agile Modeling
- Slides: 14
CSC 532: Term Paper Presentation TOPIC: Agile Modeling Presented By: POLAM SUNITHA.
AGILE MODELING ►A practice-based methodology for effective modeling and documentation of software-based systems ► Agile modeling is not a perspective process
Values ► Communication ► Simplicity ► Feedback ► Courage ► Humility
Principles ► Assume simplicity while modeling ► Embrace changes while you are working as requirements do change over time ► Incrementally change your system to enable agility
Principles Ø Obtain rapid feedback Ø Model with a purpose and need multiple models Ø Content is more important than representation
Practices ► Create several models in parallel ► Apply the right artifacts ► Model in small increments
► Goals ► The ► It of Agile Modeling Scope of Agile Modeling focuses only on effective modeling and documentation.
Figure 1. AM enhances other software processes.
Agile Model-Driven Development Figure 2: The AMDD lifecycle
Test –Driven Development (TDD) Figure 3. Steps of TDD
Comparisions of TDD and AMDD ► TDD shortens the programming feedback loop whereas AMDD shortens the modeling feedback loop. ► TDD provides detailed specification (tests) whereas AMDD can provide traditional specifications (data models). ► TDD “speaks” to programmers whereas AMDD speaks to data professionals
► TDD is non-visually oriented whereas AMDD is visually oriented ► TDD provides concrete evidence that your software works whereas AMDD supports your team, including stakeholders, in working toward a common understanding. ► TDD promotes the development of high-quality code whereas AMDD promotes high-quality communication with your stakeholders and other developers.
Conclusion ► TDD should be seen as complementary to Agile Model. Driven Development (AMDD) approaches and the two can and should be used together ► TDD does not replace traditional testing, instead it defines a proven way to ensure effective unit testing. ► From the design point of view AMDD is different from traditional development approaches but still leads to an effective modeling approach.
References ► ► ► www. agilemodeling. com/essays/amdd. htm Beck 2003, Astels 2003, Martin, Newkirk and Kess 2003, Scott Ambler http: //www. agiledata. org/essays/TDDAMDD Scott Ambler, rethinking software development, http: //www. osellus. com/seminar/1 a. pdf Agile Alliance (2001 b). Principles: The Agile Alliance. www. agilealliance. org/principles. html Christel, M. G. & Kang, K. C. (1992). Issues in Requirements Elicitation. Software Engineering Institute (SEI) Technical Report CMU/SEI-92 -TR-12. www. sei. cmu. edu http: //www. sei. cmu. edu/pub/documents/sei. documents. pdf XP with Acceptance-Test Driven Development: A rewrite project for a resource optimization system Johan Anderson, Geoff Bache, and Peter Sutton Carmen Systems www. carmen. se/research_development/ articles/ctrt 0302. pdf
