| Lesson 11 ||Navigational brief and requirements definition |
|| Describe Documents that define Navigational Structure of Site |
Documents that define Navigational Structure of Website
What do Navigational Briefs do?
Why use a Requirements Definition?
The Requirements Definition is a key document for helping relate the business objectives of the site to specific functionality, including navigational and architectural components. For example, if one of the requirements is to provide a site that is easy for children to use, the site navigation and architecture are likely to be quite different than for a site directed to astrophysicists.
The primary objective of a Requirements Definition is to describe the Web product in sufficient detail to gain approval from key stakeholders. To do so, the Requirements Definition must describe the business objectives that call for a Web solution,
and how the Web product will meet those objectives. As such, the Requirements Definition includes a description of the navigational elements and architectural structure of the site and how they relate to specific business objectives.
The sample Requirements Definition
for the website includes the following sections:
- Executive Summary,
- Business Objectives,
- Solution Requirements, and
This document goes into more detail on topics of the business itself and your client's objectives; audience information and expectations; success metrics; and various technical and solution requirements.
Question: What is the difference between the Navigational Brief and the Requirements Definition document?
Answer: The Navigational Brief comes first and is in less detail. After it is approved, you will flesh out the ideas more fully in the Requirements Definition document.
You will learn about the process of modeling information architecture in the next lesson.