Requirement Attributes

Posted on October 13, 2009 by


Requirements (something needed by a stakeholder to meet a solution) have a number of attributes. The BABOK®’s Plan Requirements Management Process task provides a listing of common requirements attributes and their definitions. Documenting the attributes of individual requirements aids in the management of all the project’s requirements. Here is a listing of ten commonly documented attributes along with an example of each. Katy is going to be assisted by her daughter Karen as she performs a cooking demonstration at their state fair. She will be baking cookies that require the pan to be greased. The requirement “pan must be greased” is used as the example requirement below.

Absolute reference is the identifier for the requirement. It could be numerical or textual. (#1254)

Author of the requirement is the person who wrote the requirement. (Katy Cook)

Complexity is how hard it will be to implement the requirement. (Easy to implement)

Ownership is who needs the requirement or will be responsible for it. (Karen Cook is responsible)

Priority is which requirements need to be implemented beforehand. (Two requirements implemented beforehand—Obtain pan and Obtain cooking spray)

Risk is what occurs if the requirement is met versus not met. (The cookies may burn if requirement not met)

Source of the Requirement is from what authority the requirement originated. (Better Baking Cookbook)

Stability is whether the requirement is mature or still changing. (Mature, we know the pan should be greased and how we want to do it)

Status is whether is has been accepted, verified, cancelled, etc. (Accepted as a requirement)

Urgency is how quickly it is needed. (Within two minutes into the cooking demonstration)