| Main Description |
The SRD describes in detail all the system software requirements. They are written in a technical language, targeted to
the development team. The analyst review the specified user requirements, assisted by the designer, to
formally establish what need to be. Each software requirement must be specified with 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 normal 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. Stability can be "negotiable" or "non-negotiable".
• Source: Document or person from which the requirement may arises.
• State: The current state of compliance of the requirement, the possibilites are: "Compliant", "Non-Compliant"
or "Ambiguous". The default when creating a requirement is "Not Compliant" .
• Each software requirement should be associated with their corresponding user requirement (can be more than
one).
• Software requirements can be classified into types:
- Functional: Indicate what should be the capabilities of the software. They are derived from the logic
model.
- Interface: Specify the hardware, software or database elements with which the system or its components interact
and communicate.
- Operational: Specify how the system will run and how you will communicate with human operators. They include
all user interfaces, human-computer interaction, and logistical and organizational requirements.
- Resources (Operating Environment): Specify the upper limits of physical resources such as processing power,
memory usage, disk space, etc.
- Usability: They are related to the effort to use and evaluate the use made by users.
- Maintainability: Related to the effort to make modifications, specifying how easy it is to repair faults and
software adaptation to new requirements.
- Portability: Related system's ability to be transferred from one environment to another.
- Reliability: They are related to the ability to maintain, under certain conditions and for a time an adequate
level of service. Specifying acceptable mean times between failures.
- Interoperability: Ability to interact with certain systems.
- Performance: They set numerical values for measurable variables related to system performance.
- Documentation: Specify custom project for documentation.
- Scalability: Specifies the system's ability to maintain or improve their average performance according to the
increased number of users.
|
