Requirement diagram makerfrom plain language, free.
/ Example
(01)Prompt: Requirements for a medical device that logs patient temperature
requirementDiagram
direction LR
requirement measure {
id: 1
text: "Measure patient temperature"
risk: High
verifymethod: Test
}
performanceRequirement accuracy {
id: 1.1
text: "Accurate to 0.1 degrees C"
risk: High
verifymethod: Test
}
functionalRequirement logging {
id: 2
text: "Log a reading every minute"
risk: Medium
verifymethod: Demonstration
}
interfaceRequirement sync {
id: 2.1
text: "Send logs to the hospital system"
risk: Medium
verifymethod: Inspection
}
designConstraint storage {
id: 3
text: "Keep 7 days of readings offline"
risk: Low
verifymethod: Analysis
}
physicalRequirement battery {
id: 4
text: "Run 48 hours on battery"
risk: Medium
verifymethod: Test
}
element sensor {
type: "Thermistor probe"
}
element firmware {
type: "Embedded software"
}
element gateway {
type: "HL7 gateway"
}
element benchTests {
type: "Bench test suite"
}
accuracy - refines -> measure
logging - derives -> measure
sync - refines -> logging
storage - refines -> logging
sensor - satisfies -> measure
firmware - satisfies -> logging
firmware - satisfies -> storage
gateway - satisfies -> sync
benchTests - verifies -> accuracy
benchTests - verifies -> battery
/ Good for
(02)- Tracing requirements to components
- Safety and compliance documentation
- Planning tests against requirements
(03)
drop something in
1text, notes, whatever
it turns into a diagram
2usually in a few seconds
tweak it if you want
3export it and move on
/ Other diagram types
(04)- FlowchartSign-up, checkout and approval flows
- Sequence DiagramAPI requests across services
- Class DiagramObject-oriented designs and domain models
- State DiagramOrder and ticket lifecycles
- ER DiagramDatabase schema design
- User JourneyOnboarding and first-run experiences
- Gantt ChartProject and release schedules
- Pie ChartBudget and cost breakdowns
- Git GraphExplaining a branching strategy
- Mind MapBrainstorming and planning
- TimelineProduct and company history
- Quadrant ChartEffort and impact prioritisation
- C4 DiagramSystem context for new team members
- Sankey DiagramBudget and money flows
- XY ChartMonthly sales or sign-ups
- Block DiagramHigh-level system overviews
- Packet DiagramProtocol and file format documentation
- Kanban BoardSprint snapshots in a README or doc
- Architecture DiagramCloud infrastructure overviews
- Radar ChartComparing products or frameworks
- TreemapBudgets broken down by department
- Ishikawa DiagramRoot cause analysis after an incident
- Venn DiagramComparing products or roles
- Tree ViewProject folder layouts in a README