Requirements Graph
How to use the visual Requirements Graph to see relationships between PRD sections, wishes, and conflicts.
Requirements Graph
The Requirements Graph is a visual, interactive map of your project's requirements landscape. It shows how PRD sections, wishes, and conflicts relate to each other — giving you a bird's-eye view of where requirements cluster, where conflicts concentrate, and how different departments' input connects to the spec.
Navigating to the Graph
From any project, click Graph in the project navigation. The graph renders automatically based on your project's current data.
Reading the Graph
The graph uses nodes and edges to represent relationships:
Node Types:
| Node | Color | Represents |
|---|---|---|
| PRD Section | Blue | A section of the project's PRD |
| Wish | Department Color | A requirement submitted by a department |
| Conflict | Red | A detected conflict between wishes |
Edges:
- A line from a Wish node to a PRD Section node means that wish is linked to that section.
- A line from a Conflict node to Wish nodes means those wishes are in conflict.
- A line from a Conflict node to a PRD Section node means the conflict affects that section.
Interacting with the Graph
The graph is fully interactive:
- Pan — click and drag the background to move around.
- Zoom — use the scroll wheel or pinch gesture to zoom in and out.
- Select a node — click any node to highlight it and see its connections. A detail panel appears showing the node's key information and a link to the full record.
- Filter — use the filter controls to show only specific node types (e.g., hide all low-priority wishes to focus on what matters).
- Reset — click the reset button to return the graph to its default layout.
What the Graph Reveals
The Requirements Graph is most useful for:
Spotting hot spots — PRD sections with many wish connections are areas of high interest or concern from departments. If a single section has 15 wishes attached to it, that section deserves careful attention during unification.
Understanding conflict clusters — conflict nodes often cluster around specific PRD sections. If three conflicts all relate to the "Data Storage" section, it's a signal that this is a contested area requiring extra discussion.
Identifying isolated wishes — wishes that aren't connected to any PRD section appear as isolated nodes. These may be orphaned requirements that need to be linked to the relevant section.
Visualizing department overlap — wish nodes are colored by department. Areas of the graph where multiple department colors converge show where teams have overlapping or conflicting requirements.
Graph During Different Phases
The graph evolves as the project moves through phases:
- During Surveying — mainly PRD sections and wishes. Useful for seeing how departments are distributing their requirements.
- During Resolving — conflict nodes appear. Useful for seeing which sections are hotly contested.
- After Unification — the graph settles. Most conflicts are resolved, and the spec is consolidated.
Exporting the Graph
You can export the graph as a PNG image for use in presentations or documentation. Click the Export Image button in the graph controls to download the current view.