Your SlideShare is downloading. ×
WebSig24/7 "IA" 20060929
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

WebSig24/7 "IA" 20060929

1,989
views

Published on

WebSig24/7のIA分科会での講演「明日から実践できるIA」プレゼン資料

WebSig24/7のIA分科会での講演「明日から実践できるIA」プレゼン資料

Published in: Business

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,989
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
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. IA bookslope 1
  • 2. 2
  • 3. http://bookslope.jp/blog/ 3
  • 4. 4
  • 5. 5
  • 6. 6
  • 7. quot;The Web as Platformquot; by Tim O'Reilly 7
  • 8. 8
  • 9. quot;Strategic Positioning: The Web as Platformquot; 9
  • 10. 2 IA Infomation Architecture Infomation Architect 10
  • 11. by Peter Merholz by Andrew Dillon by Peter Merholz 11
  • 12. 12
  • 13. 13
  • 14. 14
  • 15. 15
  • 16. 16
  • 17. by Peter Merholz by Andrew Dillon by Peter Merholz 17
  • 18. 18
  • 19. 19
  • 20. Strategic Tactical 20
  • 21. “the nine pillars of successful web teams” by Jesse James Garrett 21
  • 22. 22
  • 23. Site Strategy Abstract Design Concrete Design 23
  • 24. 24
  • 25. Site Strategy Abstract Design Concrete Design 25
  • 26. 26
  • 27. 27
  • 28. IA 2 28
  • 29. IA 29
  • 30. 30
  • 31. 31
  • 32. quot;The Elements of User Experiencequot; by Jesse James Garrett 32
  • 33. The Elements of User Experience Jesse James Garrett jjg@jjg.net A basic duality: The Web was originally conceived as a hypertextual information space; 30 March 2000 but the development of increasingly sophisticated front- and back-end technologies has fostered its use as a remote software interface. This dual nature has led to much confusion, as user experience practitioners have attempted to adapt their terminology to cases beyond the scope of its original application. The goal of this document is to define some of these terms within their appropriate contexts, and to clarify the underlying relationships among these various elements. Concrete Completion Web as software interface Web as hypertext system Visual Design: visual treatment of text, Visual Design Visual Design: graphic treatment of interface graphic page elements and navigational elements (the quot;lookquot; in quot;look-and-feelquot;) components Interface Design: as in traditional HCI: Navigation Design: design of interface design of interface elements to facilitate elements to facilitate the user's movement Interface Design Navigation Design user interaction with functionality through the information architecture Information Design Information Design: in the Tuftean sense: Information Design: in the Tuftean sense: designing the presentation of information designing the presentation of information to facilitate understanding to facilitate understanding Interaction Information Interaction Design: development of Information Architecture: structural design time Design Architecture application flows to facilitate user tasks, of the information space to facilitate defining how the user interacts with intuitive access to content site functionality Functional Content Functional Specifications: quot;feature setquot;: Content Requirements: definition of detailed descriptions of functionality the site content elements required in the site Specifications Requirements must include in order to meet user needs in order to meet user needs User Needs: externally derived goals User Needs: externally derived goals User Needs for the site; identified through user research, for the site; identified through user research, ethno/techno/psychographics, etc. ethno/techno/psychographics, etc. Site Objectives Site Objectives: business, creative, or other Site Objectives: business, creative, or other internally derived goals for the site internally derived goals for the site task-oriented information-oriented Abstract Conception This picture is incomplete: The model outlined here does not account for secondary considerations (such as those arising during technical or content development) that may influence decisions during user experience development. Also, this model does not describe a development process, nor does it define roles within a user experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today. © 2000 Jesse James Garrett http://www.jjg.net/ia/ 33
  • 34. Useful Usable Desirable Findable Accessible Credible 34
  • 35. 35
  • 36. 36
  • 37. User Experience Design User Experience Design Information Architecture Human Computer Interaction User Interface Design Interaction Design Human Factors Engineering Usability 37
  • 38. 38
  • 39. 39
  • 40. 40
  • 41. 41
  • 42. 42
  • 43. 43
  • 44. 44
  • 45. 45
  • 46. 46
  • 47. 47
  • 48. 48
  • 49. 49
  • 50. 50
  • 51. 51
  • 52. Adobe Acrobat 52
  • 53. 53
  • 54. 54
  • 55. 55
  • 56. Information Architect 56
  • 57. Thank U. 57