requirement-traceability

What problem does it solve?

Consistent and valid requirement keys are fundamental for effective traceability throughout the SDLC, but their definition and validation can be complex and prone to inconsistencies.

Core Features & Use Cases

• Key Pattern Definition: Provides clear patterns for different requirement types (Functional, Non-Functional, Data Quality) and their naming rules.
• Key Validation Rules: Defines rules for domain naming and ID sequencing to ensure uniqueness and consistency across all requirements.
• SDLC Traceability Support: Acts as a foundational knowledge base for other skills needing to trace requirements through design, code, tests, and runtime.
• Use Case: When a new requirement is extracted, this skill provides the definitive guide for assigning a unique and correctly formatted REQ-* key, ensuring it can be traced through design, code, and tests.

Quick Start

Explain the pattern for Functional Requirements (REQ-F-*) and provide examples for the 'Authentication' domain.