A requirement is an unambiguous and verifiable rendering of a need, want, or expectation that is expressed by a stakeholder. It is derived directly from user needs or stated in a contract, standard, specification, or other formally imposed document. All requirements are stored in the project database. You can create requirements in a document, in the RequisitePro Explorer, or directly in the database through a view.
A requirement type is a set of descriptive and operational information associated with a requirement. RequisitePro provides some requirement types (for example, feature, supplementary, use case, and glossary terms), but you can specify as many types as you like. Each of these types has a different tag prefix (for example, the tag for feature requirements is FEAT, the tag for specification requirements is SR, and the tag for use-case requirements is UC), and each is numbered separately. Requirement types are useful for classifying or grouping similar requirements in a project. Each type has a unique set of user-defined attributes.