IMS3801 Tutorial 12: Information Architecture

Information architecture is the art and science of shaping information and knowledge for use… through planning, interface design and construction, and aesthetics.

eWEEK list of top applications for enterprise portals December 6 1999

1.Knowledge bases and learning tools

2.Business process support

3.Customer-facing sales, marketing and services

4.Collaboration and project support

5.Access to data from disparate corporate systems

6.Internal company information

7.Policies and procedures

8.Best practices and lessons learned

9.Human resources and benefits

10.Directories and bulletin boards

11.Identification of experts

12.News and Internet access

Exercise: Planning. Categorise the above using the following categories!

1.Front-ends to networked applications (Groupware, Client-server applications, Databases)

2.Documented (text-based) knowledge (storage, access and retrieval of documents are needed; and classification and / or metadata schemes should be used)

3.Tacit knowledge (Knowledge elicitation techniques to be used, then documentation of the knowledge)

4.Tacit knowledge (aim for cross-levelling through use of communications infrastructure)

5.Procedural knowledge (directories, menus and / or databases to be constructed)

6.Declarative knowledge (knowledge-based systems such as expert systems needed)

eWEEK usability criteria June 4 1999

1.Is the site organised by user goals?

2.Can users find content by the second page-view on the site?

3.Can users find content by the third page-view on the site?

4.Is the text legible, especially on buttons and menus?

5.Are colouring and positioning of controls consistent?

6.Are navigational elements clearly visible?

7.Are words on links and prompts consistent?

8.Is the text in plain English - not jargon?

9.Are basic functions (search, home links) always available?

10.Does the search function find most of the relevant content?

QUICK TIPS TO MAKE ACCESSIBLE WEB SITES (

  • Images & animations. Use the alt attribute to describe the function of each visual.
  • Image maps. Use the client-side map and text for hotspots.
  • Multimedia. Provide captioning and transcripts of audio, and descriptions of video.
  • Hypertext links. Use text that makes sense when read out of context. For example, avoid "click here."
  • Page organization. Use headings, lists, and consistent structure. Use CSS for layout and style where possible.
  • Graphs & charts. Summarize or use the longdesc attribute.
  • Scripts, applets, & plug-ins. Provide alternative content in case active features are inaccessible or unsupported.
  • Frames. Use the noframes element and meaningful titles.
  • Tables. Make line-by-line reading sensible. Summarize.
  • Check your work. Validate. Use tools, checklist, and guidelines at

Exercise: Design and construction.

Write a policy document giving, in point form, design criteria for web pages accessed from an enterprise portal (assuming users in each information centre in the organisation create their own Web pages)