Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Technische Universität München Agile Modeling Emitzá Guzmán."— Presentation transcript:

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

2 Technische Universität München May 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 Technische Universität München May Agile Modeling 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 Technische Universität München May Agile Modeling 4 Definition It is not a prescriptive process. Its focus is on modeling.

5 Technische Universität München May Agile Modeling 5 Agenda Introduction to Agile Modeling -Definiton -Values -Principles -Practices Characterisitics of Agile Models Agile Modeling Sessions Applying Agile Modeling: XP Conclusions

6 Technische Universität München May Agile Modeling 6 Communication

7 Technische Universität München May Agile Modeling 7 Communication

8 Technische Universität München May Agile Modeling 8 Simplicity Model enough to fulfill the present needs and worry about the future needs when they appear. Be realistic when modeling!

9 Technische Universität München May Agile 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 Technische Universität München May Agile Modeling 10 Feedback Cost of fixing defects Probability of introducing defects

11 Technische Universität München May Agile Modeling 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 Technische Universität München May Agile Modeling 12 Humility In order to recognize that one that does not know everything and that one can learn from others.

13 Technische Universität München May Agile Modeling 13 Agenda Introduction to Agile Modeling –Definiton –Values –Principles –Practices Characterisitics of Agile Models Agile Modeling Sessions Applying Agile Modeling: XP Conclusions

14 Technische Universität München May Agile Modeling 14 Principles Software is your primary goal

15 Technische Universität München May Agile Modeling 15 Principles Software is your primary goal Enabling the next effort is your secondary rule

16 Technische Universität München May Agile Modeling 16 Principles Software is your primary goal Enabling the next effort is your secondary rule Travel light

17 Technische Universität München May Agile Modeling 17 Principles Software is your primary goal Enabling the next effort is your secondary rule Travel light Assume simplicity

18 Technische Universität München May Agile Modeling 18 Principles Software is your primary goal Enabling the next effort is your secondary rule Travel light Assume simplicity Embrace change

19 Technische Universität München May Agile Modeling 19 Principles Software is your primary goal Enabling the next effort is your secondary rule Travel light Assume simplicity Embrace change Make incremental change

20 Technische Universität München May Agile Modeling 20 Principles Software is your primary goal Enabling the next effort is your secondary rule Travel light Assume simplicity Embrace change Make incremental change Model with purpose

21 Technische Universität München May Agile Modeling 21 Principles Software is your primary goal Enabling the next effort is your secondary rule Travel light Assume simplicity Embrace change Make incremental change Model with purpose Use multiple models

22 Technische Universität München May Agile Modeling 22 Principles Software is your primary goal Enabling the next effort is your secondary rule Travel light Assume simplicity Embrace change Make incremental change Model with purpose Use multiple models Seek rapid feedback

23 Technische Universität München May Agile Modeling 23 Principles Software is your primary goal Enabling the next effort is your secondary rule Travel light Assume simplicity Embrace change Make incremental change Model with purpose Use multiple models Seek rapid feedback Produce quality work

24 Technische Universität München May Agile Modeling 24 Principles Software is your primary goal Enabling the next effort is your secondary rule Travel light Assume simplicity Embrace change Make incremental change Model with purpose Use multiple models Seek rapid feedback Produce quality work Maximize customer investment

25 Technische Universität München May Agile Modeling 25 Agenda Introduction to Agile Modeling –Definiton –Values –Principles –Practices Characterisitics of Agile Models Agile Modeling Sessions Applying Agile Modeling: XP Conclusions

26 Technische Universität München May Agile Modeling 26 Practices Iterative and incremental modeling Teamwork Simplicity Validation

27 Technische Universität München May Agile Modeling 27 Iterative and Incremental Modeling Apply the right artifacts Enroll in Seminar Student chooses a seminar to enroll in System checks that the student can enroll in that seminar System calculates fees Student pays fees and is enrolled

28 Technische Universität München May Agile Modeling 28 Iterative and Incremental Modeling Apply the right artifacts

29 Technische Universität München May Agile Modeling 29 Iterative and Incremental Modeling Apply the right artifacts Create several models in parallel

30 Technische Universität München May Agile Modeling 30 Iterative and Incremental Modeling Apply the right artifacts Create several models in parallel Iterate to another artifact

31 Technische Universität München May Agile Modeling 31 Iterative and Incremental Modeling Apply the right artifacts Create several models in parallel Iterate to another artifact Modell in small increments

32 Technische Universität München May Agile Modeling 32 Teamwork Model with others –Improve communication –Build common vocabulary –Provide opportunity to learn from each other Two heads are better than one!

33 Technische Universität München May Agile Modeling 33 Teamwork Model with others Active stakeholder participation

34 Technische Universität München May Agile Modeling 34 Teamwork Model with others Active stakeholder participation Collective ownership –Promotes communication –Reduces documentation –Reduces dependancy on one single person –Better understanding of the system –Rapid feedback

35 Technische Universität München May Agile Modeling 35 Teamwork Model with others Active stakeholder participation Collective ownership Display models publicly

36 Technische Universität München May Agile Modeling 36 Simplicity Create simple content

37 Technische Universität München May Agile Modeling 37 Simplicity Create simple content Depict models simply

38 Technische Universität München May Agile Modeling 38 Simplicity Create simple content Depict models simply Use the simplest tools

39 Technische Universität München May Agile Modeling 39 Validation Consider testability –How should the software be tested? –Test often and test early

40 Technische Universität München May Agile Modeling 40 Validation Consider testability Prove it with code

41 Technische Universität München May Agile Modeling 41 Agenda Introduction to Agile Modeling –Definiton –Values –Principles –Practices Characterisitics of Agile Models Agile Modeling Sessions Applying Agile Modeling: XP Conclusions

42 Technische Universität München May Agile Modeling 42 Characteristics of Agile Models Fulfill its purpose

43 Technische Universität München May Agile Modeling 43 Characteristics of Agile Models Fulfill its purpose Understandable

44 Technische Universität München May Agile Modeling 44 Characteristics of Agile Models Fulfill its purpose Understandable Sufficiently accurate

45 Technische Universität München May Agile Modeling 45 Characteristics of Agile Models Fulfill its purpose Understandable Sufficiently accurate Sufficiently consistent

46 Technische Universität München May Agile Modeling 46 Characteristics of Agile Models Fulfill its purpose Understandable Sufficiently accurate Sufficiently consistent Sufficiently detailed

47 Technische Universität München May Agile Modeling 47 Characteristics of Agile Models Fulfill its purpose Understandable Sufficiently accurate Sufficiently consistent Sufficiently detailed Provide positive value

48 Technische Universität München May Agile Modeling 48 Characteristics of Agile Models Fulfill its purpose Understandable Sufficiently accurate Sufficiently consistent Sufficiently detailed Provide positive value As simple as possible

49 Technische Universität München May Agile Modeling 49 Agenda Introduction to Agile Modeling –Definiton –Values –Principles –Practices Characterisitics of Agile Models Agile Modeling Sessions Applying Agile Modeling: XP Conclusions

50 Technische Universität München May Agile Modeling 50 Agile Modeling Sessions Duration: –At the beginning of a project: hours or days More than 2 or 3 days put your product at risk. –During the construction of the project Brainstorm Sessions: 10 to 20 minutes.

51 Technische Universität München May Agile Modeling 51 Agile Modeling Sessions 3 Key rules: –Create several models in the same session with different artifacts. –Just enough people. –Just formal enough.

52 Technische Universität München May Agile Modeling 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 Technische Universität München May Agile Modeling 53 Agenda Introduction to Agile Modeling –Definiton –Values –Principles –Practices Characterisitics of Agile Models Agile Modeling Sessions Applying Agile Modeling: XP Conclusions

54 Technische Universität München May Agile Modeling 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 Technische Universität München May Agile Modeling 55 Applying Agile Modeling: XP Planning Phase Team and customers agree on date in which the smallest implementation will be done- brainstorm of tasks Task cards Sketches of logic of task User Interface

56 Technische Universität München May Agile Modeling 56 Applying Agile Modeling: XP Iteration to release Phase Stand up meetings: developers discuss problems around a whiteboard, drawing sketches to enhance communication Modeling!

57 Technische Universität München May Agile Modeling 57 Applying Agile Modeling: XP Productionizing Phase AM done when errors are discovering and Modeling has to be done to work through the problem.

58 Technische Universität München May Agile Modeling 58 Agenda Introduction to Agile Modeling –Definiton –Values –Principles –Practices Characterisitics of Agile Models Agile Modeling Sessions Applying Agile Modeling: XP Conclusions

59 Technische Universität München May Agile Modeling 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 Technische Universität München May Agile Modeling 60 References Agile Modeling. Scott Ambler. Wiley Computer Publishing.

61 Technische Universität München Agile Modeling Thank you for your attention! ?

62 Technische Universität München Agile Modeling Exercise

63 Technische Universität München May Agile Modeling 63 System Metaphor

64 Technische Universität München May Agile Modeling 64 System Architecture

65 Technische Universität München May Agile Modeling 65 Exercise: Reminder Flow charts

66 Technische Universität München May Agile Modeling 66 Exercise: Reminder CRC Cards What a class knows or does Help with the class responsabilities

67 Technische Universität München May Agile Modeling 67 Exercise: Reminder Use Cases Actor Action that provides a measurable value Association

68 Technische Universität München May Agile Modeling 68 Exercise: Reminder CRC Model

69 Technische Universität München May Agile Modeling 69 Reminder: Exercise User Interfaces


Download ppt "Technische Universität München Agile Modeling Emitzá Guzmán."

Similar presentations


Ads by Google