Everyone who is going to be effected by the system, ie:
- The user of the system.
- The managers of those users.
- The people who maintain the system.
- Any external partners who need to audit the system.
- Regulatory bodies.
- An official agreement that formalizes the arrangement.
- Also referred as functional specification, requirements definition, or software requirement specification (SRS).
- Needs to be written in terms that are understandable by all stakeholders.
- Will not use technical terms or industry jargon, needs to written in natural language.
- The requirements gathering process consists of three parts:
- Negotiation (often used when presented with inconsistent requirements)
The Top 10 Requirements Guidelines
- Define a standard document structure.
- Make the documents easy to change (online is easier to make revisions).
- Uniquely identify each requirement (use numbering system).
- Define policies for requirement management.
- Define a template for requirements description.
- Use simple language.
- Organize requirements inspections (go over the inspections formally).
- Define a validation checklist (compare requirements against a standard).
- Use checklists of requirements problems.
- Plan for conflicts and their resolution.
|Requirement A||Requirement B||Requirement C|