Technische Universität München Agile Modeling Emitzá Guzmán

Agile Modeling

Technische Universität München

Agile ModelingEmitzá Guzmán

May 9 2008 Agile Modeling


2

Agenda

• Introduction to Agile Modeling- Definiton- Values- Principles- Practices

• Characterisitics of Agile Models

• Agile Modeling Sessions

• Applying Agile Modeling: XP

• Conclusions



3

Definition

• Methodology for modeling and documenting effectively software-based systems.

• Collection of values, principles and practices that can be applied on a software project.



4

Definition

• It is not a prescriptive process.

• Its focus is on modeling.



5

Agenda• Introduction to Agile Modeling

- Definiton- Values- Principles- Practices




• Conclusions



6

Communication



7

Communication



8

Simplicity

Model enough to fulfill the present needs and worry about the future needs when they appear.

Be realistic when modeling!



9

Feedback

• Only way to determine if the work we have done is correct.

• Ways to obtain feedback:– Develop model as a team– Review the model with the target audience– Implement the model– Acceptance testing

• Obtain feedback from the beginning of the project.



10

Feedback

Cost of fixing defects

Probability of introducing defects



11

Courage

In order to:– Make decisions such as system architecture or development

language.– Recognize that one can make mistakes.– To trust that one can overcome future problems in the future

-> Enabling simplicity.



12

Humility

In order to recognize that one that does not know everything and that one can learn from others.



13

Agenda

• Introduction to Agile Modeling– Definiton– Values– Principles– Practices




• Conclusions



14

Principles

• Software is your primary goal



15

Principles


• Enabling the next effort is your secondary rule



16

Principles



• Travel light



17

Principles



• Travel light

• Assume simplicity



18

Principles



• Travel light


• Embrace change



19

Principles



• Travel light


• Embrace change

• Make incremental change



20

Principles



• Travel light


• Embrace change


• Model with purpose



21

Principles



• Travel light


• Embrace change



• Use multiple models



22

Principles



• Travel light


• Embrace change




• Seek rapid feedback



23

Principles



• Travel light


• Embrace change





• Produce quality work



24

Principles



• Travel light


• Embrace change





• Produce quality work

• Maximize customer investment



25

Agenda





• Conclusions



26

Practices

• Iterative and incremental modeling

• Teamwork

• Simplicity

• Validation



27

Iterative and Incremental Modeling

• Apply the right artifacts

Enroll in Seminar

•Student chooses a

seminar to

enroll in

•System ch

ecks that th

e student c

an

enroll in th

at seminar

•System ca

lculates f

ees

•Student pays f

ees and is

enrolled



28





29



• Create several models in parallel



30




• Iterate to another artifact



31




• Iterate to another artifact

• Modell in small increments



32

Teamwork

• Model with others

– Improve communication

– Build common vocabulary

– Provide opportunity to learn from each other

Two heads are better than one!



33

Teamwork


• Active stakeholder participation



34

Teamwork



• Collective ownership– Promotes communication– Reduces documentation– Reduces dependancy on one single person– Better understanding of the system– Rapid feedback



35

Teamwork



• Collective ownership

• Display models publicly



36

Simplicity

• Create simple content



37

Simplicity


• Depict models simply



38

Simplicity


• Depict models simply

• Use the simplest tools



39

Validation

• Consider testability

– How should the software be tested?

– Test often and test early



40

Validation

• Consider testability

• Prove it with code



41

Agenda





• Conclusions



42

Characteristics of Agile Models

• Fulfill its purpose



43



• Understandable



44



• Understandable

• Sufficiently accurate



45



• Understandable


• Sufficiently consistent



46



• Understandable



• Sufficiently detailed



47



• Understandable




• Provide positive value



48



• Understandable




• Provide positive value

• As simple as possible



49

Agenda





• Conclusions



50

Agile Modeling Sessions

• Duration:

– At the beginning of a project: hours or daysMore than 2 or 3 days put your product at risk.

– During the construction of the projectBrainstorm Sessions: 10 to 20 minutes.



51

Agile Modeling Sessions

• 3 Key rules:

– Create several models in the same session with different artifacts.

– Just enough people.

– Just formal enough.



52

Brainstorm Sessions

• Stand-up meetings around a whiteboard or a table preferred.

• Focused on a single topic (a small chunk of requirements)

• Stop modeling once goal is fulfilled.



53


– Definiton– Values– Principles– Practices




• Conclusions



54

Applying Agile Modeling: XP

• Exploration Phase

XP concentrates on System Metaphores, but that does not mean that other diagrams can not be created



55


• Planning Phase

Team and customers agree on date in which the smallest implementation will be done-brainstorm of tasks

Task cardsSketches of logic of taskUser Interface



56


• Iteration to release Phase

Stand up meetings: developers discuss problems around a whiteboard, drawing sketches to enhance communicationModeling!



57


• Productionizing Phase

AM done when errors are discovering and Modeling has to be done to work through the problem.



58


– Definiton– Values– Principles– Practices




• Conclusions



59

Conclusions

• Agile Modeling can be used in a software process in order to enhance modeling.

• In order to say you are Agile Modeling you need to follow all of the Principles and Practices of Agile Modeling.



60

References

• www.agilemodeling.com.

• Agile Modeling. Scott Ambler. Wiley Computer Publishing.

• www.extremeprogramming.org

Agile Modeling


Thank you for your attention!

?

Agile Modeling


Exercise



63

System Metaphor



64

System Architecture



65

Exercise: Reminder

• Flow charts



66

Exercise: Reminder

• CRC Cards

What a class knows or doesHelp with the class

responsabilities



67

Exercise: Reminder

• Use Cases

Actor

Action that provides a measurable value

Association



68

Exercise: Reminder

• CRC Model



69

Reminder: Exercise

• User Interfaces

Documents

Technische Universität München Agile Modeling Emitzá Guzmán