This document provides guidance on identifying content and functional requirements for a website. It instructs to create lists of the content elements and functional needs of the site. Content should be categorized as static, dynamic, functional or transactional. Examples of each type of content are given. The document also recommends grouping and labeling content and including content inventories and requirements lists in the design document. The overall purpose is to understand what information and features are needed for the site.
2. Site Content
• Try to get a mental image of what your site will look
like with content on it
• Use this image to your advantage
• Gather the pieces for creating
the structure and organization
of the site.
3. Site Content
• What content does the site need?
• What sort of functionality will be required?
• Pieces of content determine functionality
4. Site Content
• Create a list of content and functional requirements to
get a better picture of how your site will work
• Determine how you want your content grouped and
labeled
5. Content Requirement
• Identify Content and Functional Requirements
• Group and Label Content
• Design Document – Content and Functions
6. Identify Content and
Functional Requirements
START 2 NEW LISTS:
• Content elements
• Functional requirements
CONTENT LIST – CONTENT INVENTORY
• Gather information from everyone
• Determine the importance of each piece of content
7. Identify Content and
Functional Requirements
TYPE OF CONTENTS
• Static
• Dynamic
• Functional
• Transactional
11. Identify Content and
Functional Requirements
FUNCTIONAL REQUIREMENTS
• Member logon pages
• Sign up pages (for email newsletter etc.)
• Pages that involve forms
13. Identify Content and
Functional Requirements
CONTENT INVENTORY
• Revise your list of functional requirements
• Think about the technology and skills needed to meet
each requirements
• Rank the importance of each requirement, eliminate
some if necessary
14. Group and Label Content
• Important because it helps you organize your website.
• Allows you to have a more structured website.
15. Group and Label Content
• Make sure to remember who is doing what.
• Discuss when done.
16. Group and Label Content
• Compare and Contrast
• Pros and Cons
17. Group and Label Content
• Once finished everyone
should agree if the website
is ready or not
• “Ready” = Go
• “Not” = Discuss more.
18. Design Document –
Content and Functions
• Create a new chapter in your design document called
Content and Functional Requirements
• Include and summary of the content inventory
• Add the list of functional requirements with a summary
19. Design Document –
Content and Functions
• Content inventory should be included as an appendix to
the design document
20. Fin.
• HTTP://WWW.WEBMONKEY.COM/2010/02/INFORMATI
ON_ARCHITECTURE_TUTORIAL_-_LESSON_3
• Vi Tran 9-12
• Prince Jackson 5-8
• Nicholas Tegge 1-4
• George Baso 14-17
• Kahi Tai 13, 18-20