A requirements source is the origin from which a team obtains information about a stakeholder need, system capability, or constraint.
Common sources include stakeholders, documents, existing systems, business processes, policies, observations, and operational data. Therefore, teams should identify relevant origins early during elicitation.
Analysts record each source with suitable details. For example, they may capture a stakeholder’s name, role, and contact information. For a document, they may record its title, owner, version, and location.
One source often reveals additional contacts, documents, or systems. Consequently, teams can use the snowball principle to expand their search. They should also review the register regularly because new information may appear throughout the project.
Traceability links each requirement to its origin. Moreover, this connection helps teams verify information, understand rationale, and assess changes.
Missing or outdated sources can cause incomplete or incorrect requirements. Therefore, teams should confirm relevance and remove obsolete entries.
Systematic source management improves coverage, traceability, validation, and the overall reliability of the requirements set.
« Back to Glossary Index