You are on page 1of 2

What Are Agile Models?

Recommended Resources Agile Modeling


An agile model is a model that is just barely good Agile Alliance Home Page An Overview
enough, which implies that it exhibits the following www.agilealliance.com
traits: By Scott W. Ambler
Agile Modeling Home Page www.ambysoft.com/scottAmbler.html
1. It fulfills its purpose.
www.agilemodeling.com
2. It is understandable.
Agile Modeling (AM) is a chaordic, practice-based
3. It is sufficiently accurate.
Agile Models Distilled methodology for effective modeling of software-
4. It is sufficiently consistent.
www.agilemodeling.com/artifacts based systems. The AM methodology is a
5. It is sufficiently detailed.
collection of practices, guided by principles and
6. It provides positive value.
Modeling Style Guidelines values that can be applied by software
7. It is as simple as possible.
www.agilemodeling.com/style professionals on a day-to-day basis. AM is not a
prescriptive process, it does not define detailed
Agile Modeling Mailing List procedures for how to create a given type of model;
www.agilemodeling.com/feedback.htm instead it provides advice for how to be effective as
What Is(n’t) AM? a modeler. Think of AM as an art, not a science.
1. AM is a supplement to existing methods, it Agile Modeling FAQ
is not a complete methodology. www.agilemodeling.com/faq.htm AM has three goals:
2. AM is a way to work together effectively
to meet the needs of project stakeholders. 1. To define and show how to put into practice a
Agile Modeling (The Book)
3. AM is effective and is about being collection of values, principles, and practices
www.ambysoft.com/agileModeling.html
effective. pertaining to effective, light-weight modeling.
4. AM is something that works in practice, it 2. To explore how to apply modeling techniques
Agile Database Techniques Home Page
isn’t an academic theory. on software projects taking an agile approach
www.agiledata.org
5. AM is not a silver bullet. such as XP, Scrum, DSDM, or FDD.
6. AM is not a prescriptive process. 3. To explore how you can improve modeling
Agile Model Driven Development (AMDD)
7. AM is for the average developer, but is not following an instantiation of the Unified
www.agilemodeling.com/essays/amdd.htm
a replacement for competent people. Process such as the RUP, EUP, or AUP
8. AM is not an attack on documentation, (www.ambysoft.com/unifiedprocess).
Agile Model Driven Architecture (Agile MDA)
instead AM advises to create documents www.agilemodeling.com/essays/agileMDA.htm
that have value.
9. AM is not an attack on CASE tools.
10. AM is not for everyone.

Copyright 2001-2006 Scott W. Ambler


Ambysoft Inc., www.ambysoft.com
This version: February 10, 2006
AMDD Values Practices
Agile Model Driven Development (AMDD) is the The Values of AM Core Practices of AM
agile version of Model Driven Development - Communication - Active Stakeholder Participation
(MDD). The figure below overviews the - Courage - Apply The Right Artifact(s)
fundamentals of AMDD: - Feedback - Collective Ownership
- At the beginning of a project invest some time to - Humility - Create Several Models in Parallel
do some initial modeling, particularly to explore the - Simplicity - Create Simple Content
fundamental requirements and to identify a potential - Depict Models Simply
architectural approach. - Display Models Publicly
- During development cycles you will typically - Iterate To Another Artifact
model for several minutes and then implement for Principles - Model in Small Increments
several hours or even days until you need to do - Model With Others
some more modeling. Core Principles of AM - Prove it With Code
- The AM practices of Model With Others and - Assume Simplicity - Single Source Information
Collective Ownership are effectively model reviews - Embrace Change - Use the Simplest Tools
in process, removing the need for formal reviews. - Enabling the Next Effort is Your
Secondary Goal
- Incremental Change Supplementary Practices of AM
- Maximize Stakeholder Investment - Apply Modeling Standards
- Model With a Purpose - Apply Patterns Gently
- Multiple Models - Discard Temporary Models
- Quality Work - Formalize Contract Models
- Rapid Feedback - Update Only When It Hurts
- Software is Your Primary Goal
- Travel Light

Supplementary Principles of AM
- Content Is More Important Than
Representation
- Open and Honest Communication

Copyright 2001-2006 Scott W. Ambler


Ambysoft Inc., www.ambysoft.com
This version: February 10, 2006

You might also like