Stakeholders

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.

Requirements Document

• 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:
  • Elicitation
  • Analysis
  • Negotiation (often used when presented with inconsistent requirements)

The Top 10 Requirements Guidelines

1. Define a standard document structure.
2. Make the documents easy to change (online is easier to make revisions).
3. Uniquely identify each requirement (use numbering system).
4. Define policies for requirement management.
5. Define a template for requirements description.
6. Use simple language.
7. Organize requirements inspections (go over the inspections formally).
8. Define a validation checklist (compare requirements against a standard).
9. Use checklists of requirements problems.
10. Plan for conflicts and their resolution.

Traceability Matrix

	Requirement A	Requirement B	Requirement C
Component A	X
Component B		X
Component C			X
Component D		X