Complexity Analysis

OPTIONAL Advanced Validation Tool for Problem-Based SRS methodology
Purpose: Analyze specification quality using Axiomatic Design principles
When to use: After completing the standard process, when deeper quality analysis is needed

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 RFC 2119 RFC 8174 when, and only when, they appear in all capitals, as shown here.

⚠️ Optional Skill

This is NOT part of the standard Problem-Based SRS flow. Use it when you want to:

• Verify specification independence (no coupled requirements)
• Evaluate completeness levels mathematically
• Identify redundancies or gaps in your specification
• Apply rigorous engineering quality checks

Standard Flow: customer-problems → software-glance → customer-needs → software-vision → functional-requirements → zigzag-validator