• Like
  • Save
What an information architect could learn from Plato
Upcoming SlideShare
Loading in...5
×

What an information architect could learn from Plato

  • 3,354 views
Uploaded on

What I've learned from Plato, being an information architect...

What I've learned from Plato, being an information architect...

More in: Design , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,354
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
7

Embeds 0

No embeds

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. WHAT AN IA COULD LEARNFROM PLATOBARCAMP HASSELT#BCHASSELT - OCTOBER 22, 2011WOUTER WALGRAEVE - NASCOM
  • 2. HI!I AM WOUTER WALGRAEVE AND I WORK AT NASCOM
  • 3. PLATOINFORMATION ARCHITECT
  • 4. ALLEGORY OF THE CAVE PLATO’S THEORY OF FORMS
  • 5. PLATO NEOINFORMATION ARCHITECTINFORMATION ARCHITECT
  • 6. WHAT DO YOU SEE?
  • 7. WHAT DO YOU SEE?
  • 8. ALL OBJECTS WE RECOGNIZE AS “CHAIRS”
  • 9. A CHAIRTHE CHAIR
  • 10. A THINGTHE OBJECT
  • 11. EVERYTHING WE SEE IS  AN INSTANCE OF  AN OBJECT
  • 12. PERCEPTION OF AN  OBJECT IS LAYERED IN   MATERIAL STRUCTURE VIEW
  • 13. OBJECTTRANSLATED INTO IT LINGO…   DATA LOGICS INTERFACE
  • 14. THAT’S THE CORE OF  OBJECT ORIENTATIONAND  MULTI-TIER THINKING
  • 15. OBJECTCONCEPT   VALUES LOGICS INTERFACE
  • 16. INSTANCE:CLASS UML (KINDA) STYLE   ATTRIBUTES BUSINESS METHODS INTERFACE METHODS
  • 17. OBJECT » APPLICATION WITH OBJECTS, WE MODEL APPLICATIONS.  
  • 18. APPLICATION 3-TIER THINKING   DATA BUSINESS LOGICS USER INTERFACE
  • 19. OBJECT » APPLICATION »SERVICE ORIENTED ARCHITECTURE APPLICATIONS LIVE IN SERVICE ORIENTED ARCHITECTURES  
  • 20. SOA3-TIER THINKING   DATABASE API WEBAPPS
  • 21. SOA 3-TIER THINKING   DATA, VALUESDATABASE RELATIONSHIPS TABLES, RECORDS… 3-TIER THINKING   SQL API PHP, ROR REST, SOAP 3-TIER THINKING   JSON, XMLWEBAPP JS HTML, CSS, JS
  • 22. OBJECT MATERIAL STRUCTURE VIEWALL OUR IT BEST PRACTICE DESIGN PATTERNS ARE BASED ON PLATO’S OBJECT MODEL THINKING  
  • 23. OBJECT ORIENTATION ININFORMATION ARCHITECTURE
  • 24. THESE ARE ALL BLOCKS.ARE THEY ORDERED BY SHAPE, COLOR OR HEIGHT?  
  • 25. BLOCKTHIS IS OUR OBJECT.  
  • 26. HEIGHT BLOCKCOLOR SHAPE WITH ITS TAXONS.  
  • 27. HEIGHT 1 2 3 4 5 BLOCK RED RECTANGLE YELLOW BLUE SQUARE TRIANGLE GREEN ROUNDCOLOR SHAPE AND ITS TAXON TERMS.  
  • 28. YOU CAN DEFINE AN   OBJECT USING  TAXONOMY
  • 29. HEIGHT 1 2 3 4 5 BLOCK RED RECTANGLE YELLOW BLUE SQUARE TRIANGLE GREEN ROUNDCOLOR SHAPEYOU CAN FILTER A SET OF OBJECTS BY NAMING A TAXON TERM.  
  • 30. “SHOW ME ALL THE BLUE,ROUND BLOCKS OF HEIGHT 2”  
  • 31. HEIGHT 1 2 3 4 5 BLOCK RED RECTANGLE YELLOW BLUE SQUARE TRIANGLE GREEN ROUNDCOLOR SHAPEWHEN YOU COMBINE THEM, YOU CREATE A FACET OF OBJECTS.
  • 32. CAN YOU IDENTIFY OTHER TAXONS?  
  • 33. HEIGHT 1 2TYPE 3 MATERIAL 4 5 PAINTED WOOD BLOCK RED RECTANGLE YELLOW BLUE SQUARE TRIANGLE GREEN ROUND COLOR SHAPE A TAXONOMY CAN ALWAYS BE EXPANDED WITH OTHER TAXONS, ADDING MORE DETAILS & IDENTIFYING ELEMENTS TO THE OBJECT.  
  • 34. SO,  INFORMATION ARCHITECTURE IS  DEFINING HOW YOU LOOK AT OBJECTS AND THAT’S WHAT I LEARNED FROM…  
  • 35. PLATOINFORMATION ARCHITECT
  • 36. API  vs  prototypes  &  applica2es   LIKED IT?
  • 37. TWITTER ME:@WOUTERWALGRAEVELINKEDIN:…/WOUTERWALGRAEVE
  • 38. WHUFFIESTOHTTP://WWW.FLICKR.COM/PHOTOS/ELVIS1967HTTP://WWW.FLICKR.COM/PHOTOS/GALESSAHTTP://WWW.FLICKR.COM/PHOTOS/MADDCOVV
  • 39. NASCOMINFO@NASCOM.BE@NASCOM ON TWITTER