1. Agile Modelling in Software Engineering Audrey Nemeth, Vladimir Borisov

2. AM Values CommunicationCommunication SimplicitySimplicity FeedbackFeedback CourageCourage HumilityHumility Source: http://www.agilemodeling.com/values.htm

3. AM Principles Assume SimplicityAssume Simplicity Embrace ChangeEmbrace Change Enabling the Next Effort is Your Secondary GoalEnabling the Next Effort is Your Secondary Goal Incremental ChangeIncremental Change Maximize Stakeholder InvestmentMaximize Stakeholder Investment Source: http://www.agilemodeling.com/principles.htm

4. AM Principles Model With a PurposeModel With a Purpose Multiple ModelsMultiple Models Quality WorkQuality Work Rapid FeedbackRapid Feedback Software Is Your Primary GoalSoftware Is Your Primary Goal Travel LightTravel Light

5. AM Principles Content is More Important Than RepresentationContent is More Important Than Representation Open and Honest CommunicationOpen and Honest Communication (Supplementary)

6. AM Practices Active Stakeholder ParticipationActive Stakeholder Participation Apply the Right Artifact(s)Apply the Right Artifact(s) Collective OwnershipCollective Ownership Create Several Models in ParallelCreate Several Models in Parallel Create Simple ContentCreate Simple Content Depict Models SimplyDepict Models Simply Source: http://www.agilemodeling.com/practices.htm

7. AM Practices Display Models PubliclyDisplay Models Publicly Iterate to Another ArtifactIterate to Another Artifact Model in Small IncrementsModel in Small Increments Model With OthersModel With Others Prove it With CodeProve it With Code Single Source InformationSingle Source Information Use the Simplest ToolsUse the Simplest Tools

8. How AM Practices Fit Together Source: http://www.agilemodeling.com/essays/practicesFitTogether.htm

9. What is AM used for? You are taking an agile approach to development in generalYou are taking an agile approach to development in general You plan to work iteratively and incrementallyYou plan to work iteratively and incrementally The requirements are uncertain or volatileThe requirements are uncertain or volatile The primary goal is to develop softwareThe primary goal is to develop software The active stakeholders are supportive and involvedThe active stakeholders are supportive and involved The development team is in control of its destinyThe development team is in control of its destiny The developers are responsible and motivatedThe developers are responsible and motivated Adequate resources are available for the projectAdequate resources are available for the project

10. AM in Software Development Projects AM is meant to be tailored into other, full-fledged methodologies, enabling you to develop a software process which truly meets your needs.

11. Agile Model Driven Development

12. AM in eXtreme Programming The three most common misconceptions are that software designers: don’t modeldon’t model don’t documentdon’t document if they do model, only use modeling artifacts of UMLif they do model, only use modeling artifacts of UML www.extimeprogramming.com

13. AM in Unified Process In the RUP there are three disciplines that encompass modeling activities for a single project – Business Modeling, Requirements, and Analysis & Design – and the EUP adds Enterprise Business Modeling and Enterprise Architecture

14. AM in Feature-Driven Development

15. How to Save Time in Modellingin Modelling –Design models that are just barely good enough –For a given model, use the simplest tool –Effective developers make use of multiple models in Documentationin Documentation –Unit tests form much of the detailed design documentation –When dealing with a part of the software that is really complicated, either document it thoroughly or redesign it to make it simpler