Elements
graph TD;
%% REQVIRE-AUTOGENERATED-DIAGRAM
%% Graph styling
classDef userRequirement fill:#D1C4E9,stroke:#7E57C2,stroke-width:2px;
classDef systemRequirement fill:#E1D8EE,stroke:#673AB7,stroke-width:1.5px;
classDef verification fill:#DCEDC8,stroke:#4CAF50,stroke-width:2px;
classDef folder fill:#FAFAFA,stroke:#9E9E9E,stroke-width:3px;
classDef file fill:#FFF8E1,stroke:#FFCA28,stroke-width:2px;
classDef default fill:#F5F5F5,stroke:#424242,stroke-width:1.5px;
subgraph e6e9a42ade18cb0e["📁 requirements/Functional/Output"]
subgraph 7ac75a27d422080f["📄 Behaviors.md"]
67e56f7a86840a["Mermaid Diagram Interaction Behavior"];
class 67e56f7a86840a default;
click 67e56f7a86840a "Behaviors.html#mermaid-diagram-interaction-behavior";
5c87b81c1c498514["Reverse Relation Traversal Behavior"];
class 5c87b81c1c498514 default;
click 5c87b81c1c498514 "Behaviors.html#reverse-relation-traversal-behavior";
e3571c4e0809ece6["Short Mode Behavior"];
class e3571c4e0809ece6 default;
click e3571c4e0809ece6 "Behaviors.html#short-mode-behavior";
c722f86eb2eb252f["Start Element Type Filter Behavior"];
class c722f86eb2eb252f default;
click c722f86eb2eb252f "Behaviors.html#start-element-type-filter-behavior";
8244c27e5a9f5023["Verification Coverage Philosophy Behavior"];
class 8244c27e5a9f5023 default;
click 8244c27e5a9f5023 "Behaviors.html#verification-coverage-philosophy-behavior";
end
end
Mermaid Diagram Interaction Behavior
Interactive behavior for Mermaid diagrams in HTML export.
Details
Click Behavior:
- Nodes are clickable links to element definition
- Links use relative paths from output location
- External links open in new tab
Zoom/Pan:
- Mouse wheel for zoom
- Click and drag for pan
- Reset button to restore initial view
Metadata
Reverse Relation Traversal Behavior
When reverse mode is enabled for model traversal:
- Follow backward relations (derivedFrom, satisfy, verify) instead of forward relations
- Start from leaf elements (elements with no outgoing forward relations) when no specific element is specified
- Build tree structure from leaves upward toward root requirements
- When a specific starting element is provided, start from that element and traverse upward
- Report “Reverse” direction indicator in output metadata
Metadata
Relations
Short Mode Behavior
Behavior when --short flag is provided to CLI commands.
Details
Short mode reduces output verbosity for quick scanning:
Text Output (–short without –json):
- One line per element:
[type] identifier - name
- Omit detailed content, relations, and metadata
- Suitable for piping to other tools
JSON Output (–short with –json):
- Omit verbose fields:
content, page_content, attachments
- Omit computed fields:
element_count, total_elements, global_counters
- Retain:
identifier, name, type, file_path
- Retain:
relations (for traceability)
Rationale:
- Reduces output size for large models
- Faster parsing by downstream tools
- Maintains essential traceability information
Metadata
Start Element Type Filter Behavior
When start element type filtering is enabled:
- Accept a list of element types to filter starting points
- Use only elements matching specified types as traversal starting points
- When combined with reverse traversal, filter leaf elements by type
- When used with forward traversal, filter root elements by type
- Support all element types as filter values
Metadata
Relations
Verification Coverage Philosophy Behavior
Coverage evaluation philosophy for verification reporting.
Details
Leaf Requirements (MUST be verified):
- Requirements that don’t derive other requirements
- Must have verifiedBy relations to verification artifacts
- Verification gaps are flagged in coverage reports
Parent/Intermediate Requirements (MAY be verified):
- Requirements that derive other requirements
- Optional verification since leaf verifications may cover them
- System engineers responsible for ensuring verification scopes are sufficient
Verification Relationships:
- One verification may verify multiple leaf requirements (N:1)
- Change impact propagates from parent to leaf requirements and verifications
- AI systems can help create comprehensive verification scopes and prevent overlap
Roll-up Strategy:
- Leaf requirement verification provides coverage for parent requirements
- Parent verification is redundant if all derived leaves are verified
- Coverage percentages focus on leaf requirement verification status
Metadata
Relations