7. Typical structure

There are no hard and fast rules for creating a Requirements Document. Companies sometimes have a standard template than can be used. This saves time and tends to ensure that important aspects are covered.

A template might include

• Establish a vision for the system. Include information that has been gathered in the investigation stage. It should focus on the 'what' of the project not the 'how' it is to be done.
• Create a glossary of terms and their definition for this project. For example, the word 'system' can mean many things to many people. So pin it down in the glossary so everyone has the same understanding with its use in the project.
• Define the contraints of the project, in terms of time and budget as well as any physical constraints.
• Identify standards and legal aspects the system must adhere to.
• Use system diagrams, data flow diagrams and tables to clarify the details
• Explain how the system integrates with existing business processes. Include Use Cases to clarify how people are going to use it.
• Define performance in a quantifiable way.
• Establish who is allowed to manage and update the document along with who has sign-off authority.