1. INFORMATION ARCHITECTURE SECTION 3 By : Crystal Ledesma Zhi Cen Vidal Orozco

2. Site Content What pieces of content does the site need? What sorts of functionality will be required?

3. Site Content: Identify Content & Functional Requirements

4. Site Content: Content Elements Types of Content: static, dynamic, functional, transactional Static content examples: Copyright notices, privacy statements, and membership rules Functional content examples: Member logon pages, signup pages for email newsletters, and other pages involving forms or transactions

5. Site Content: Content Inventory 1.Everyone creates their own lists of desired content. 1.Combine main list with others lists. 1.Review the combined list to determine the importance of each piece of content 1.Revise if necessary.

6. Site Content: Revise, Review, Rank Revise Utilize the content inventory to revise the list of functional requirements. Review Review by determining the feasibility of each requirement (i.e. do you have the technology & skills to meet each requirement?)

7. Site Content: Revise, Review, Rank Rank Utilizing what you learned through revising and reviewing, rank the importance of each requirement.

8. Group and Label Content Begin with write down each element of the content inventory on an index card.

9. Group and Label Content Take the cards and organize them into groups.

10. Group and Label Content Name each groups. For instant, Group 1 can be called "images", we can name group 2 "company history," etc. Groupd

11. Group and Label Content Have everyone in your team involved and repeat the process several times. Watch out for your deadlines, because this process might be time consuming.

12. Group and Label Content Decide the final grouping and names.

13. Group and Label Content After you decided on the final groupings and names, use them as the basis for defining the major sections of the site and the names of each section. This is the basis for your site structure.

14. Group and Label Content Revise the content inventory to reflect the new organization of information.

15. Design Document: Content and Functions

16. Design Document: Purpose Have a comprehensive and highly defined guide that you follow. It’s an essential tool to help write the program efficiently.

17. Design Document: Example

18. Content Requirement: web as hypertext system. Functions Requirement: web as software interface. Content and Functions Requirements

19. Content and Functions Specification Content Specification: Should provide word count for text features, pixels for images, file size for downloads, etc. Functions Specification: What the system will do and how to prevent bad things.

20. The End Information Architecture- Section 3