|
| |
Requirements traceability is the practice of connecting requirements to related information to support requirements validation, analysis, decision making, project management, implementation and testing. Requirements traceability can be implemented as a matrix that links each requirement to related information. The following are common examples.
Business CaseStating the related business case or goal for each requirement to ensure that the business has actually asked for it. For example, a requirement for a change to a sales workflow might be connected to the business case "reduce order processing time."ObjectiveLinking a requirement to an objective. It is a common best practice to list requirements at the lowest level possible. Requirements can then be grouped together by the objective that they achieve. For example, ten different requirements for data, process and user interface changes might relate to "capture customer contacts" as an objective.
SourceListing the person and business unit who submitted the requirement.ProcessThe impacted business processes.TechnologyThe impacted components or systems.DataImpacted data entities.TestsLinking requirements to test cases.SpecificationsLinking business requirements to detailed specifications such as a technical design.|
Type | | Definition | The practice of connecting each requirement to related business information such as goals, objectives, components, systems, processes, specifications, business units, data entities and test cases. | Related Concepts | |
Business Analysis
This is the complete list of articles we have written about business analysis.
If you enjoyed this page, please consider bookmarking Simplicable.
A list of common project risks.
A list of basic project management techniques.
A definition of workaround with examples.
A list of project branding techniques.
An overview of project stakeholder management with examples.
A definition of action plan with examples.
The primary types of cost overrun.
The definition of document control with examples.
A guide to project oversight.
A definition of design driven development with examples.
The common types and formats of requirements.
The difference between functional and non-functional requirements explained.
The difference between requirements and specifications.
The difference between functional and behavioral requirements explained.
A few examples of non-functional requirements.
The common types of customer requirements.
The difference between functions and features.
The common types of requirements elicitation.
A definition of requirements management with examples.
The common types of needs analysis.
TrendingThe most popular articles on Simplicable in the past day.
Recent posts or updates on Simplicable.
Site Map
© 2010-2024 Simplicable. All Rights Reserved. Reproduction of materials found on this site, in any form, without explicit permission is prohibited.
View credits & copyrights or citation information for this page.
|
