Download
csc532 term paper presentation n.
Skip this Video
Loading SlideShow in 5 Seconds..
CSC532:Term Paper Presentation PowerPoint Presentation
Download Presentation
CSC532:Term Paper Presentation

CSC532:Term Paper Presentation

125 Vues Download Presentation
Télécharger la présentation

CSC532:Term Paper Presentation

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. CSC532:Term Paper Presentation TOPIC: Agile Modeling Presented By: POLAM SUNITHA.

  2. AGILE MODELING • A practice-based methodology for effective modeling and documentation of software-based systems • Agile modeling is not a perspective process

  3. Values • Communication • Simplicity • Feedback • Courage • Humility

  4. Principles • Assume simplicity while modeling • Embrace changes while you are working as requirements do change over time • Incrementally change your system to enable agility

  5. Principles • Obtain rapid feedback • Model with a purpose and need multiple models • Content is more important than representation

  6. Practices • Create several models in parallel • Apply the right artifacts • Model in small increments

  7. Goals of Agile Modeling • The Scope of Agile Modeling • It focuses only on effective modeling and documentation.

  8. Figure1. AM enhances other software processes.

  9. Agile Model-Driven Development Figure2: The AMDD lifecycle

  10. Test –Driven Development (TDD) Figure 3. Steps of TDD

  11. 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

  12. 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.

  13. 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.

  14. 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/1a.pdf • Agile Alliance (2001b). 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/ctrt0302.pdf