Please enable JavaScript.
Coggle requires JavaScript to display documents.
REQUIREMENTS MANAGEMENT - Coggle Diagram
REQUIREMENTS MANAGEMENT
Requirements Attributes
Typical Attributes Requirements
Source
Stability
Description
Criticality
Name
Priority
Identifier
Defining Requirements Attributes
Ensuring consistency (dependencies)
Identification
Structuring
Progress and state control
Additional Attributes of Requirements
Legal Obligation (Shall, should, Will)
Kano model type
Requirement kind (high-level, detailed requirement)
Author
Requirement type (functional, quality, constraint)
Status (regarding content, validation, agreement)
Version
Requirements Attribute Schemes
Specific properties of the project
Constraints of the organization
Domain rules
Constraints of the development process
Prioritizing Requirements
Method
Determining the requirements to be prioritized
Establish prioritization techniques
Choosing the stakeholder for prioritizing
Prioritizing
Determining prioritization criteria
Techniques
Kano Classification
Ranking
Single-Criterion Classification, IEEE Std. 830-1998
Top-ten Technique
Traceability of Requirements
Classification
Post-RS Traceability
Traceability between requirements
Pre-RS Traceability
Representation
Hyperlinks
Trace matrices
Text-based references
Trace graphs
Matrix Record relationships between two item types
Test cases and requirements
Design parts and requirements
Use cases and features
Requirements and requirements
Requirements and sources
Change Management
Composition of Change control board
User representative
Quality manager
Architect
Contractor
Requirements engineer
Change manager
Clasification of incoming change request
Corrective requirement change
Adaptive requirement change
Exceptional requirement change
Tools Support
Categories
Issue management tools
Configuration management tools
Modeling tools
Knowledge management tools (e.g. wiki)
Requirements management tools
Office tools
Integrated tool suites