Interactions 09 Object Oriented Approach To Design--OAD
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Interactions 09 Object Oriented Approach To Design--OAD

  • 32,734 views
Uploaded on

Interaction 09 presentation. The title was Object-oriented design: A technique for designing and documenting complex business rules and rich interactions. A write up of this technique can be found......

Interaction 09 presentation. The title was Object-oriented design: A technique for designing and documenting complex business rules and rich interactions. A write up of this technique can be found at oad.humansize.com

More in: Design , Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • From my point of view this approach is object-based rather than object-oriented. Nonetheless very interesting. Thanks.

    http://en.wikipedia.org/wiki/Object-based
    Are you sure you want to
    Your message goes here
  • I am documenting the details behind this at http://oad.humansize.com/
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
32,734
On Slideshare
32,604
From Embeds
130
Number of Embeds
12

Actions

Shares
Downloads
538
Comments
2
Likes
47

Embeds 130

http://www.slideshare.net 40
http://bitpakkit.blogspot.com 28
http://jbaeck.posterous.com 15
http://www.linkedin.com 14
https://twitter.com 10
http://bitly.com 8
http://www.stereoprototype.com 7
http://us-w1.rockmelt.com 2
http://joho3001.soup.io 2
http://www.lmodules.com 2
http://www.firstpeoplesplus.com 1
http://bitpakkit.blogspot.de 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. A WIREFRAMING AND SPECIFICATIONS TECHNIQUE FOR RICH INTERACTIONS AND COMPLEX BUSINESS LOGIC For
more
details
go
to
OAD.humansize.com
 © 2009 TandemSeven Nick Iozzo (niozzo_at_tandemseven.com) 1
  • 2. WHAT DO I MEAN BY COMPLEX? THIS SCREEN IS COMPRISED OF 10MODULES. THESE MODULES HAVE THE FOLLOWING NUMBER OF CONDITIONS, RESPECTIVELY: 4, 26, 10, 6, 3, 5, 3, 7, 3, 3. Over 17 Million possible layouts to this screen!
  • 3. TOPICS •  WHAT IS OOD •  IS IT FOR YOU? •  MORPHOLOGY OF FLOWS •  MORPHOLOGY OF MODULES •  BENEFITS OF OOD •  QUESTIONS
  • 4. TOPICS •  WHAT IS OOD •  IS IT FOR YOU? •  MORPHOLOGY OF FLOWS •  MORPHOLOGY OF MODULES •  BENEFITS OF OOD •  QUESTIONS
  • 5. OBJECT-ORIENTED? 
  • 6. Conceptually, This is How it is Object-Oriented
  • 7. SYNTAX OF OOD SCREEN MAP MODULE FUNCTIONAL SPECIFICATIONS WIREFRAME MODULE STATES
  • 8. WHEN TO USE OOD •  USE IT AFTER CONCEPTS ARE COMPLETE –  IN A RUP WORLD, SPEC OUT ALL SCREENS –  IN AN AGILE WORLD, SPEC OUT MODULES BY ITERATION
  • 9. TOPICS •  WHAT IS OOD •  IS IT FOR YOU? •  MORPHOLOGY OF FLOWS •  MORPHOLOGY OF MODULES •  BENEFITS OF OOD •  QUESTIONS
  • 10. Confusion
  • 11. Distant team members?
  • 12. Requirements a mouth of numbers?
  • 13. Bureaucracy
  • 14. Language Barrier
  • 15. Localization
  • 16. Large teams?
  • 17. TOPICS •  WHAT IS OOD •  IS IT FOR YOU? •  MORPHOLOGY OF FLOWS •  MORPHOLOGY OF MODULES •  BENEFITS OF OOD •  QUESTIONS
  • 18. NOT A FLOW CHART
  • 19. SCREEN MAP
  • 20. INFORMATION ARCHITECTURE
  • 21. TOPICS •  WHAT IS OOD •  IS IT FOR YOU? •  MORPHOLOGY OF FLOWS •  MORPHOLOGY OF MODULES •  BENEFITS OF OOD •  QUESTIONS
  • 22. Amazon Example
  • 23. Amazon Example
  • 24. Amazon Example
  • 25. Amazon Example
  • 26. Amazon Example
  • 27. Amazon Example
  • 28. Amazon Example
  • 29. Amazon Example
  • 30. Amazon Example
  • 31. Amazon Example
  • 32. Amazon Example
  • 33. Amazon Example
  • 34. Amazon Example
  • 35. Amazon Example
  • 36. Amazon Example
  • 37. Amazon Example
  • 38. Amazon Example
  • 39. AMAZON.COM AS A FAMILIAR EXAMPLE
  • 40. SYNTAX OF OOD SCREEN MAP MODULE FUNCTIONAL SPECIFICATIONS WIREFRAME MODULE STATES
  • 41. EXAMPLE WIREFRAME VIEW
  • 42. MODULE STATES
  • 43. A DIFFERENT MODULE •  DESIGN FOR THESE HYPOTHETICAL BUSINESS RULES –  LOGGED IN USERS SEE ALL POSSIBLE CONTENT –  NOT LOGGED IN, BUT CAN BE IDENTIFIED VIA COOKIE –  UNKNOWN USER
  • 44. CLUMSY WAY TO DO THIS
  • 45. USING NESTED MODULE
  • 46. USING SUB-MODULES
  • 47. REFERENCED MODULES
  • 48. REFERENCED MODULES
  • 49. ERRORS
  • 50. NUMBERING CONVENTIONS WITHIN OOD HOME100.10 STATE 20 STATE ID MODULE ID UNIQUE NUMBER WITHIN THIS SECTION. ALONG WITH THE SECTION NAME, THIS DEFINES THE SCREENID SECTION NAME
  • 51. TOPICS •  WHAT IS OOD •  IS IT FOR YOU? •  MORPHOLOGY OF FLOWS •  MORPHOLOGY OF MODULES •  BENEFITS OF OOD •  QUESTIONS
  • 52. BENEFITS OF OOD •  HELPS BRIDGE MANY DIFFICULTIES PROJECT TEAMS FACE •  IT CAN BE USED TO EASILY DESCRIBE COMPLEX BUSINESS REQUIREMENTS OR RICH INTERACTIONS. •  YOU CAN FULLY DESCRIBE AND DESIGN ALL STATES A SCREEN CAN BECOME. •  COMPLEXITY IS REDUCED THROUGH DECOMPOSITION •  UNIVERSAL REFERENCES AND IDS ARE CREATED THAT CAN BE USED BY ALL TEAMS IN THE PROJECT
  • 53. BENEFITS OF OOD •  HELPS BRIDGE MANY DIFFICULTIES PROJECT TEAMS FACE •  IT CAN BE USED TO EASILY DESCRIBE COMPLEX BUSINESS REQUIREMENTS OR RICH INTERACTIONS. •  YOU CAN FULLY DESCRIBE AND DESIGN ALL STATES A SCREEN CAN BECOME. •  COMPLEXITY IS REDUCED THROUGH DECOMPOSITION •  UNIVERSAL REFERENCES AND IDS ARE CREATED THAT CAN BE USED BY ALL TEAMS IN THE PROJECT
  • 54. BENEFITS OF OOD •  HELPS BRIDGE MANY DIFFICULTIES PROJECT TEAMS FACE •  IT CAN BE USED TO EASILY DESCRIBE COMPLEX BUSINESS REQUIREMENTS OR RICH INTERACTIONS. •  YOU CAN FULLY DESCRIBE AND DESIGN ALL STATES A SCREEN CAN BECOME. •  COMPLEXITY IS REDUCED THROUGH DECOMPOSITION •  UNIVERSAL REFERENCES AND IDS ARE CREATED THAT CAN BE USED BY ALL TEAMS IN THE PROJECT
  • 55. BENEFITS OF OOD •  HELPS BRIDGE MANY DIFFICULTIES PROJECT TEAMS FACE •  IT CAN BE USED TO EASILY DESCRIBE COMPLEX BUSINESS REQUIREMENTS OR RICH INTERACTIONS. •  YOU CAN FULLY DESCRIBE AND DESIGN ALL STATES A SCREEN CAN BECOME. •  COMPLEXITY IS REDUCED THROUGH DECOMPOSITION •  UNIVERSAL REFERENCES AND IDS ARE CREATED THAT CAN BE USED BY ALL TEAMS IN THE PROJECT
  • 56. BENEFITS OF OOD •  HELPS BRIDGE MANY DIFFICULTIES PROJECT TEAMS FACE •  IT CAN BE USED TO EASILY DESCRIBE COMPLEX BUSINESS REQUIREMENTS OR RICH INTERACTIONS. •  YOU CAN FULLY DESCRIBE AND DESIGN ALL STATES A SCREEN CAN BECOME. •  COMPLEXITY IS REDUCED THROUGH DECOMPOSITION •  UNIVERSAL REFERENCES AND IDS ARE CREATED THAT CAN BE USED BY ALL TEAMS IN THE PROJECT
  • 57. QUESTIONS?
  • 58. TOPICS •  WHAT IS OOD •  IS IT FOR YOU? •  MORPHOLOGY OF FLOWS •  MORPHOLOGY OF MODULES •  BENEFITS OF OOD •  QUESTIONS