InfoFoundry

• Published:October 17th, 2008
• Comments:No Comment
• Category:Information Architecture

The Requirements document is important to create a specific list of functionality so that the client and company can specfically agree on exactly what is needed for the project. Recently I re-authored our requirements document based on several different past documents. I remember a while back when, I would search the web looking for headings so that I wouldn’t miss any possible requirements for a site. Heres the list of starting point headings that are in the current document, that I thought other Information Architects, and Interaction Designers may find useful.

1.0 BACKGROUND AND OVERVIEW
2.0 PURPOSE OF THIS DOCUMENT
3.0 ROLES AND OBJECTIVES OF THE SITE
4.0 PHASE ONE REQUIREMENTS
4.1 GENERAL
4.2 USER ACCOUNTS
4.3 BACKEND MANAGEMENT
4.4 PAYMENT SYSTEM
4.5 BILLING SYSTEM
5.0 PHASE TWO KNOWN REQUIREMENTS
6.0 REQUIREMENTS EXCLUDED FROM SCOPE
7.0 TARGET AUDIENCES
7.1 PRIMARY AUDIENCE
7.2 SECONDARY AUDIENCE
7.3 AUDIENCE USER REQUIREMENTS
8.0 SITE SUCCESS MEASURES
9.0 OTHER FUNCTIONALITY
9.1 UTILITY PAGES
9.2 COMPLIANCE STANDARDS
10.0 CONSIDERATIONS AND RECOMMENDATIONS