Requirement Management Guide
What is requirements management?
Why is requirements management important?
How are requirements managed in an organization?
- Stakeholder roles and responsibilities
- Requirements gathering & management process
- Types of requirements
- Requirements artifacts
- Requirements naming and versioning convention
- Requirements prioritization
- Requirements traceability
- Requirements versioning
- Requirements baseline
Requirements Change Management
4. Requirements artifacts
An artifact is an object, structure, observation of key importance, or a result derived from preparatory or investigatory procedures. For example, the artifacts in your project can be use-cases, design documents, business process diagrams, or use case diagrams. Requirements artifacts are the documents that are produced during requirements management that contain requirements and other supplementary information for the project team and the stakeholders. The following are some of the artifacts are derived from the requirements management process:
- System Requirements Document (SRD)
- System Requirements Justification Document (for traceability purposes)
- System External Interface Requirements Document
The information provided in the artifacts, the format, layout & structuring, and ownership of these artifacts will vary depending on who is creating them as well as in which domain they will be utilized. Similarly, the number and structure of requirement artifacts may slightly differ from organization to organization as well.