Requirement Attributes

Attributes of a Software Project Requirement

Let’s learn in brief about various attributes of a Requirement

1.  Id.: Id or Identification Number. Please provide every Requirement of your project a unique id. It is not unusual for the team track any update on the requirement by mentioning the Id
2. Title: Provide a short, crisp and meaningful title to this requirement. The Title should not be more than a line with 4-8 words
3. Author: Name of the person who has written this requirement
4. Source: Name of the person / client stake holder who has mentioned this requirement
5. Description: 2-6 line meaningful description of this requirement.
6.  Priority: Priority for this requirement. For example, priority can be "High", "Medium" or "Low"
7. Type: Type of the requirement. Whether it is a "New Functionality", "Bug", "Enhancement", "Design Change" etc.
8. Department: The client department which is associated with this requirement
9. Module: The software module of which this requirement will be a part
10. Release / Sprint No: Mention the release number or sprint number in which the requirement will be delivered
11. Status: Mention the status of the requirement. Status can be 'Delivered' , 'Under Development' , "Scheduled', 'Revision', "To Be Scheduled' , 'Rejected' . Just in case you reject the requirement do not forget to mention the reason for rejection
12. Approved By: Mention the name of the approver of this requirement. This can be a senior user from the client.
13. Verified by: Mention the name of the verifier of this requirement. This can be the BA himself or his reporting manager.
14. Dev Team: Name of the development team who has been assigned this requirement
15. Developer: Name of the developer who has been assigned this requirement
16. Tester: Name of the tester who has been assigned to test this requirement
17. Delivery Date: Expected date of delivery of this requirement. This can be derived from the delivery date of the concerned release or sprint
18. Vendor Owner: The owner of this requirement from within the IT vendor who is responsible for the delivery it can be the Project Manager or the Product Manager
19. Client Owner: Name of the client stakeholder who finally owns this requirement. He can be the departmental head or the project champion.

Dear fellow IT Business Analyst if you are facing a challenge to manage requirements of your software project you can convert the above attributes to fields of a Requirements Catalogue or a Requirements Database in MS Excel or any other Spreadsheet program. You may take note that you can remove some or add new requirement attributes as per needs of your project. Just in case you find it difficult don' t hesitate to drop in an email to [email protected]