When writing a requirements document it is essential that each requirement is structured in a manner that allows the reader to understand the content and status of the requirement. The following are a list of components that assist in this process:

• Unique ID
• Requirement status (new, draft, approved, cancelled, changed, delivered)
• Requirement title
• Requirement description
• Priority (MoSCoW)
• Functional area

Unique ID: This is a serial number that is used from cradle to grave against the requirement. It is non-transferable
Requirement status: Each requirement follows a standard method from creation to delivery
Requirement title: This is a short meaningful strap line e.g. Registration - Twitter/Facebook accounts
Requirement description: This is a single sentence describing the requirement that is to be delivered. E.g. a user can register using either a valid Twitter or Facebook account as an alternative to an email address
Priority: Using MoSCoW you are able to specify the importance of developing software where too many requirement, exceeding budgets or delivering late are a threat.
In the example above MUST would be allocated to supplying an email address; Should to a valid Twitter account and Could to a valid Facebook account
Functional area: This is an initial indication on thee area of code that the business requirement relates. In the example used above Registration

Tags: Requirements, MOSCOW