Requirements attributes provide information about the requirements and help in the ongoing management of the requirements throughout the change.

The most commonly used requirements attributes are as follows:

• An absolute reference: This is the unique identifier. This identifier is completely unique to this requirement and never changed or reused, even if the original requirement is deleted.
• The author of the requirement is the person who formulated the requirement and also the person who should be contacted regarding ambiguity, something being unclear, or if there is a conflict relating to the requirement.
• The complexity indicates how difficult it will be to implement the requirement.
• The ownership refers to the stakeholder or stakeholder group that will be the business owner of the requirement once the solution is implemented.
• The priority refers to the relative importance of the requirement. This can indicate the value or sequence of implementation.
• Risks identify uncertain events that may impact the requirement.
• The source indicates where the requirement comes from. This could be from a specific stakeholder or group of stakeholders or it can be from an existing system.
• The stability shows how mature the requirement is. In other words, how likely the requirement is to change.
• The status shows whether the requirement is proposed, accepted, verified, postponed, canceled, or implemented.
• The urgency is the attribute that shows how soon the requirement is needed.