Requirements catalogue
A requirements catalogue organises requirements with identifiers and verifiable details. It helps track scope, unresolved questions and changes.
A requirements catalogue is an organised collection of requirements. Unique identifiers and a documented version help people find the same requirement in discussions, quotes and checks.
In a hypothetical portal project, R7 describes which customer prices a signed-in user may see. The entry records the confirmed rule, its priority and the planned evidence. An unresolved ERP prerequisite is explicitly marked as open.
A long list does not prove that requirements are complete, consistent or implemented. Status and evidence need maintaining. Changes should remain visible so providers do not price different versions. Whether the catalogue is a table or held in a tool matters less than clarity and traceability.
Sources
Related terms
- Requirements analysisRequirements analysis clarifies what a solution must achieve and why. Requests are examined for meaning, conflicts and verifiable outcomes.
- Must-have requirementA must-have requirement is essential to the agreed delivery scope. Without it, the intended outcome is not acceptable within that scope.
- Should-have requirementA should-have requirement matters but is not essential to the delivery scope under consideration. An accepted workaround can initially allow use.
- Exit strategyA prepared route to switch, take over or retire an IT service in an orderly way.
- Migration costsEffort and expenditure for the planned move of data or functions to another environment.
- Investment costsCosts of building a new or expanded IT capability, as considered in project planning.
Articles on this topic
IT Consulting & Strategy with ASES
Strategy, architecture and technology choice