Example: Core Requirements Attributes
This is a basic list of requirement attributes that could apply to most requirement types. They should be used whether the requirements are being tracked manually or with a tool.
Relationships
Description
Main Description

Some attributes are best described as a number, date, Boolean (true or false), or a text field for entering free-format comments. Other attributes can be expressed as lists. For instance, priority type is a list of high, medium, and low; weekday is a list that includes Monday, Tuesday, and so on.

Creator Person who is writing the original requirement
Date of Last Update Date the requirement was modified
Creation Date Date the requirement was first created
Last Person to Update Name of the person who last modified the requirement
Source Person, document, or other origin of a given requirement. This is useful for determining who to call for questions, or for grouping requirements according to the person making the demands.
Priority Statement of relative importance of the requirement, either to the system or to the business (for instance, critical, high, medium, or optional)
Status Current status of the requirement (for example, submitted, reviewed, or approved)