Csc532: Term Paper Presentation topic: Agile Modeling Presented By: polam sunitha. Agile modeling

Download 4,6 Kb.
Date conversion15.02.2017
Size4,6 Kb.

CSC532:Term Paper Presentation

  • TOPIC:
  • Agile Modeling
  • Presented By:



  • Communication
  • Simplicity
  • Feedback
  • Courage
  • Humility


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



  • Goals of Agile Modeling
  • The Scope of Agile Modeling
  • It focuses only on effective modeling and documentation.
  • Figure1. AM enhances other software processes.

Agile Model-Driven Development

  • Figure2: The AMDD lifecycle

Test –Driven Development (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.


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


  • Beck 2003,Astels 2003,Martin,Newkirk and Kess 2003,Scott Ambler
  • Scott Ambler, rethinking software development,
  • Agile Alliance (2001b). Principles: The Agile Alliance.
  • Christel, M.G. & Kang, K.C. (1992). Issues in Requirements Elicitation. Software Engineering Institute (SEI) Technical Report CMU/SEI-92-TR-12.
  • XP with Acceptance-Test Driven Development: A rewrite project for a resource optimization system Johan Anderson, Geoff Bache, and Peter Sutton Carmen Systems articles/ctrt0302.pdf

The database is protected by copyright © 2016
send message

    Main page