| Main Description |
The User Requirement describes in detail all the user requirements. They are written with a language oriented to the
client or user. The usage of technical terms should be avoided. Each user requirement should be specified according to
the following structure:
• ID: Unique code used to identify and formally refer to this requirement in the project. It is automatically assigned
incrementally using the "RUXXXX" format.
• Name: Name in current language.
• Description: Description of requirement (the aspects involved, what it is, etc.).
• Priority: level of urgency associated with the requirement. The priority of a requirement may be "urgent", "soon",
"normal" or "if possible".
• Stability: This attribute determines whether or not the requirement may be subject to change during the product
life-cycle management software. Stability can be "negotiable" or "non-negotiable".
• Type: User requirements can be classified into 3 types:
- Functional: Describes a capacity that must be supported by the software product.
- Quality: They represent an attribute of product quality, and can be expressed in a measurement scale.
- Restriction: They indicate what restrictions will develop and / or operate the software, depending on cost,
time, personnel, operational environment, hardware, networks, etc.
• Source: Document or person from which the requirement arises.
• State: The current state of compliance with the requirement in the development, may be "Compliant", "Non-Compliant"
or "Ambiguous". The default when creating status is "Not Compliant".
|
