WebSig24/7 "IA" 20060929
621 views | 0 comments | 0 favorites | embeds (Stats)
WebSig24/7のIA分科会での講演「明日から実践できるIA」プレゼン資料
More Info
This slideshow is Public
Views: 621 Comments: 0 Favorites: 0 Downloads: 0
View Details:
621 on Slideshare
from embeds
from embeds
Loading...
Flash Player 9 (or above) is needed to view slideshows. We have detected that you do not have it on your computer. To install it, go here.
Presentation Transcript
- Slide 1: IA bookslope 1
- Slide 2: 2
- Slide 3: http://bookslope.jp/blog/ 3
- Slide 4: 4
- Slide 5: 5
- Slide 6: 6
- Slide 7: \"The Web as Platform\" by Tim O'Reilly 7
- Slide 8: 8
- Slide 9: \"Strategic Positioning: The Web as Platform\" 9
- Slide 10: 2 IA Infomation Architecture Infomation Architect 10
- Slide 11: by Peter Merholz by Andrew Dillon by Peter Merholz 11
- Slide 12: 12
- Slide 13: 13
- Slide 14: 14
- Slide 15: 15
- Slide 16: 16
- Slide 17: by Peter Merholz by Andrew Dillon by Peter Merholz 17
- Slide 18: 18
- Slide 19: 19
- Slide 20: Strategic Tactical 20
- Slide 21: “the nine pillars of successful web teams” by Jesse James Garrett 21
- Slide 22: 22
- Slide 23: Site Strategy Abstract Design Concrete Design 23
- Slide 24: 24
- Slide 25: Site Strategy Abstract Design Concrete Design 25
- Slide 26: 26
- Slide 27: 27
- Slide 28: IA 2 28
- Slide 29: IA 29
- Slide 30: 30
- Slide 31: 31
- Slide 32: \"The Elements of User Experience\" by Jesse James Garrett 32
- Slide 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 \"look\" in \"look-and-feel\") 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: \"feature set\": 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
- Slide 34: Useful Usable Desirable Findable Accessible Credible 34
- Slide 35: 35
- Slide 36: 36
- Slide 37: User Experience Design User Experience Design Information Architecture Human Computer Interaction User Interface Design Interaction Design Human Factors Engineering Usability 37
- Slide 38: 38
- Slide 39: 39
- Slide 40: 40
- Slide 41: 41
- Slide 42: 42
- Slide 43: 43
- Slide 44: 44
- Slide 45: 45
- Slide 46: 46
- Slide 47: 47
- Slide 48: 48
- Slide 49: 49
- Slide 50: 50
- Slide 51: 51
- Slide 52: Adobe Acrobat 52
- Slide 53: 53
- Slide 54: 54
- Slide 55: 55
- Slide 56: Information Architect 56
- Slide 57: Thank U. 57
SlideShare brings the cloud to PowerPoint and your desktop... 