FRD Functional Requirements Specification Format
I have found a very convenient format of writing requirements documents. The format is mostly suitable for writing functional requirements documents. Yet, the format give a very good framework to specify requirements for UI elements and controls.
- Reqt – is a unique (within a document) requirement id.
- Label – normally the controls are labled so you can reference it by label, otherwise you can make a call out on the wireframe.
- Type – control or UI element type: field, button, list etc.
- Length – length of the data in characters.
- Required – specify if the element is required or not.
- Values – this column contains the value for drop-downs and other list views.
- Rule – any rule associated with the rule, including business rules.
- Pre-populated – any default value that should prepopulate the field, or be set in drop-down etc.
- Error Message – one or multiple error messages that should be shown if a rule is violated.
