Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Six Blind Men And An Elephant

Like the blind men in the familiar parable, business analysts are at risk of drawing false conclusions about requirements when they rely on a single perspective. This presentation illustrates the importance of using multiple model views to get a complete picture of the required solution.

  • Be the first to comment

Six Blind Men And An Elephant

  1. 1. Six Blind Men and an Elephant<br />Using Multiple Models to Get a Complete View of Requirements<br />Gary Bellamy<br />
  2. 2. The Fable<br /><br />Gary Bellamy<br />
  3. 3. An Elephant is like a Wall!<br /><br />Gary Bellamy<br />
  4. 4. An Elephant is like a Spear!<br /><br />Gary Bellamy<br />
  5. 5. An Elephant is like a Snake!<br /><br />Gary Bellamy<br />
  6. 6. An Elephant is like a Tree!<br /><br />Gary Bellamy<br />
  7. 7. An Elephant is like a Fan!<br /><br />Gary Bellamy<br />
  8. 8. An Elephant is like a Rope!<br /><br />Gary Bellamy<br />
  9. 9. Multiple Views<br /><br />Gary Bellamy<br />
  10. 10. What is a Model?<br /><br />Gary Bellamy<br />
  11. 11. Model Formats<br />BODY<br />EAR<br />TUSK<br />LEG<br />TAIL<br />TRUNK<br /><br />Gary Bellamy<br />
  12. 12. Why Model?<br /><ul><li>Describe situation or define problem
  13. 13. Define domainboundaries and components
  14. 14. Describe thought processes and action flows
  15. 15. Categorize and create hierarchies
  16. 16. Show components and their relationships
  17. 17. Show business logic</li></ul><br />Gary Bellamy<br />
  18. 18. Model Views<br />Control<br />Source: EBG Consulting<br /><br />Gary Bellamy<br />
  19. 19. Behavior View<br />UML: Use Case Diagram (and Specification)<br />ID: UC1<br />Name: Submit Registration<br />Description: Registrant reviews event information and, based on interest and availability, preregisters for the event.<br />Precondition: Promotional email received<br />Basic Flow:<br />Registrant checks topic<br />Registrant checks speaker<br />Registrant Likes topic and speaker<br />Registrant checks availability at event date and time<br />Registrant is available <br />Registrant notifies registrar of intent to attend event.<br />Post-condition<br />Registrant is pre-registered<br />Exception 1:<br />Registrant does not like topic <br /><br />Gary Bellamy<br />
  20. 20. Behavior View<br />UML: Activity Diagram<br /><br />Gary Bellamy<br />
  21. 21. Behavior View<br />Business Process Modeling <br />Notation (BPMN)<br /><br />Gary Bellamy<br />
  22. 22. Behavior View<br />UML: Sequence Diagram<br /><br />Gary Bellamy<br />
  23. 23. Structure View<br />UML: Class Diagram<br /><br />Gary Bellamy<br />
  24. 24. Structure View<br />Entity Relationship Diagram<br /><br />Gary Bellamy<br />
  25. 25. Dynamics View<br />UML: State Machine Diagram<br /><br />Gary Bellamy<br />
  26. 26. Dynamics View<br />Data Flow Diagram<br /><br />Gary Bellamy<br />
  27. 27. Control View<br />Structured English<br /><br />Gary Bellamy<br />
  28. 28. Control View<br />Decision Table<br /><br />Gary Bellamy<br />
  29. 29. Control View<br />Decision Tree<br /><br />Gary Bellamy<br />
  30. 30. Model Levels<br /><br />Gary Bellamy<br />
  31. 31. Scope Level<br />Context Diagram<br /><br />Gary Bellamy<br />
  32. 32. Scope Level<br />UML: Business Use Case Diagram<br /><br />Gary Bellamy<br />
  33. 33. Scope Level<br />UML: Business Use Case Diagram<br /><br />Gary Bellamy<br />
  34. 34. Scope Level<br />UML: Domain Model<br /><br />Gary Bellamy<br />
  35. 35. Don’t capture requirements blindly<br /><br />Gary Bellamy<br />