zigzag-validator
Zig Zag Decomposition
Validation & Consistency Tool for Problem-Based SRS methodology
Purpose: Map and decompose between CP, CN, and FR domains
Single Responsibility: Ensure traceability and consistency across domain hierarchies
Position in Process
This skill is used during and after Steps 1, 3, and 5 to validate and refine mappings between domains. It does not replace the generation skills—it complements them.
Diagram preference: When visualizing traceability mappings, prefer Mermaid UML diagrams (e.g.,
flowchartfor hierarchy trees,graphfor dependency maps) over ASCII art where rendering supports it.
More from rafaelgorski/problem-based-srs
problem-based-srs
Complete Problem-Based Software Requirements Specification methodology following Gorski & Stadzisz research. Use when you need to perform requirements engineering from business problems to functional requirements with full traceability.
20software-vision
Transform Software Glance and Customer Needs into a detailed Software Vision with positioning, stakeholders, features, and architecture. Use after Customer Needs. Step 4 of Problem-Based SRS methodology.
4business-context
Establish structured business context and project principles before problem discovery. Use as Step 0 of Problem-Based SRS to capture project identity, business principles, stakeholders, domain boundaries, and success criteria that feed into Customer Problems identification.
4functional-requirements
Generate Functional Requirements (FR) and Non-Functional Requirements (NFR) from Customer Needs and Software Vision. Creates individual requirement files with traceability. Step 5 of Problem-Based SRS methodology.
4customer-problems
Identify and document Customer Problems (CP) from business context. Use when starting requirements engineering or when stakeholders describe solutions instead of problems. Step 1 of Problem-Based SRS methodology.
4customer-needs
Specify Customer Needs (CN) that define WHAT outcomes software must provide to solve Customer Problems. Use after Software Glance to translate problems into needs. Step 3 of Problem-Based SRS methodology.
3