AI Quality Analysis
Automatically validate flowcharts for errors, ensure ISO 5807 compliance, and get intelligent suggestions for improvement
AI Quality Analysis
Ensure your flowcharts are error-free, professional, and compliant with industry standards. Our AI Quality Analyzer automatically detects common mistakes, validates ISO 5807 compliance, and provides actionable improvement suggestions.
Overview
The AI Quality Analyzer is your automated quality assurance tool. It scans your flowchart for logical errors, structural issues, and compliance violations, giving you a comprehensive quality report with specific recommendations. Think of it as a code linter, but for flowcharts.
Whether you're creating business process documentation, technical specifications, or educational materials, the Quality Analyzer ensures your diagrams meet professional standards and communicate clearly.
How It Works
The AI Quality Analyzer performs a multi-stage analysis:
- Structural Analysis - Validates node connections and flow paths
- Compliance Check - Ensures ISO 5807 standard adherence
- Logic Verification - Detects unreachable code and infinite loops
- Best Practices - Evaluates against flowchart design principles
- Scoring - Generates an overall quality score (0-100)
Analysis Engine
When you run the analyzer:
- Traverses all nodes and edges in your flowchart
- Identifies entry and exit points
- Maps all possible execution paths
- Checks for terminal conditions
- Validates shape usage according to ISO 5807
- Generates a detailed report with line-by-line feedback
Accessing Quality Analysis
Keyboard Shortcut: Cmd/Ctrl + Shift + A
The Quality Analyzer is available in the flowchart editor toolbar. Click the "Analyze" button or use the keyboard shortcut to run a full analysis on your current flowchart.
Error Detection
Dead Ends
What it finds:
- Nodes without outgoing connections (except End nodes)
- Processes that don't lead anywhere
- Abandoned workflow branches
Example:
❌ Process "Validate Data" has no outgoing edge
→ Add connection to next step or End node
Dead ends are one of the most common flowchart errors. The analyzer identifies every node that doesn't have a path forward, helping you complete your logic flow.
Unreachable Nodes
What it finds:
- Nodes without incoming connections (except Start nodes)
- Isolated workflow sections
- Disconnected processes
Example:
❌ Process "Send Email" is unreachable from Start
→ Add connection from previous step or remove if unused
Infinite Loops
What it finds:
- Circular paths without exit conditions
- Decision nodes that always loop back
- Missing break conditions
Example:
❌ Decision "Retry?" creates infinite loop
→ Add condition to exit loop after max retries
Missing Entry/Exit Points
What it finds:
- Flowcharts without Start nodes
- Flowcharts without End nodes
- Multiple start points
- Ambiguous termination
Example:
❌ No Start node found
→ Add Start/End node to define flow boundaries
Invalid Connections
What it finds:
- Decision nodes with wrong number of outputs
- Incorrect edge types for node kinds
- Logical impossibilities
Example:
❌ Decision node has only one output edge
→ Decisions must have at least 2 branches (Yes/No, True/False)
ISO 5807 Compliance
Shape Validation
The analyzer verifies that each shape is used correctly according to ISO 5807 standards:
Process (Rectangle):
- ✅ Used for operations, calculations, data processing
- ❌ Not for decisions or input/output
Decision (Diamond):
- ✅ Used for Yes/No questions, conditional branches
- ✅ Must have at least 2 outgoing edges
- ❌ Not for processes or simple routing
Terminal (Rounded Rectangle):
- ✅ Used for Start and End points
- ✅ Start nodes should have 0 incoming edges
- ✅ End nodes should have 0 outgoing edges
Data (Parallelogram):
- ✅ Used for input/output operations
- ❌ Not for processing or storage
Database (Cylinder):
- ✅ Used for database operations, persistent storage
- ❌ Not for temporary data or variables
Labeling Standards
The analyzer checks label quality:
- ✅ Clear, descriptive labels
- ✅ Verb-noun format for processes ("Validate Input", "Calculate Total")
- ✅ Question format for decisions ("Is Valid?", "User Logged In?")
- ❌ Empty or placeholder labels
- ❌ Too vague ("Process", "Check", "Thing")
Quality Metrics
Overall Score (0-100)
The analyzer calculates a comprehensive quality score based on:
Structure (40 points):
- No dead ends or unreachable nodes
- Clear entry and exit points
- Proper node connections
Compliance (30 points):
- ISO 5807 shape usage
- Correct labeling conventions
- Standard symbol adherence
Logic (20 points):
- No infinite loops
- Complete decision branches
- Logical flow paths
Best Practices (10 points):
- Readable layout
- Consistent spacing
- Clear visual hierarchy
Quality Levels
90-100: Excellent
- Professional-grade flowchart
- Ready for production use
- Meets all standards
70-89: Good
- Minor improvements needed
- Generally well-structured
- Few minor issues
50-69: Fair
- Several issues to address
- Requires revision
- Some logical problems
0-49: Needs Work
- Major structural problems
- Multiple errors detected
- Significant revision required
Aim for 85+ for professional documentation. Anything above 90 indicates excellent flowchart design that meets industry standards.
Improvement Suggestions
The analyzer provides specific, actionable recommendations:
Structural Improvements
💡 Add End node after "Complete Transaction"
   Your flow ends abruptly. Add a terminal node to clearly mark completion.
💡 Connect "Error Handler" to main flow
   This node is isolated. Integrate error handling into your workflow.
Layout Improvements
💡 Reduce vertical spacing
   Nodes are too far apart. Compact layout improves readability.
💡 Align decision branches
   Inconsistent branch alignment. Use grid snap for cleaner layout.
Labeling Improvements
💡 Rename "Process 1" to descriptive label
   Generic labels reduce clarity. Use specific action verbs.
💡 Rephrase "Check" as question
   Decision labels should be questions: "Is Valid?" vs "Check"
Logic Improvements
💡 Add timeout condition to loop
   Infinite loop detected. Add max iteration counter or timeout.
💡 Handle false branch in decision
   Missing false path. Add error handling or alternative route.
Analysis Report
The analyzer generates a detailed report with sections:
1. Executive Summary
- Overall quality score
- Total issues found
- Critical vs. minor issues
- Recommendations priority
2. Error Details
- Specific location of each error
- Description of the problem
- Suggested fix
- Severity level (Critical, Warning, Info)
3. Compliance Report
- ISO 5807 adherence percentage
- Shape usage validation
- Labeling convention check
4. Best Practices
- Layout suggestions
- Readability improvements
- Performance optimizations
5. Action Items
- Prioritized list of fixes
- Quick wins (easy fixes)
- Complex improvements
Using the Analyzer
Basic Analysis
- Open your flowchart in the editor
- Press Cmd/Ctrl + Shift + Aor click "Analyze"
- Wait 2-5 seconds for analysis to complete
- Review the report in the side panel
Understanding Results
Critical Issues (Red):
- Must be fixed for flowchart to be valid
- Blocks proper functionality
- Address immediately
Warnings (Yellow):
- Should be fixed for best practices
- May cause confusion
- Address before sharing
Information (Blue):
- Optional improvements
- Nice-to-have enhancements
- Consider for polish
Applying Fixes
Auto-Fix Available: Some issues can be fixed automatically:
- Click "Fix" button next to the issue
- Analyzer applies the recommended change
- Review and undo if needed
Manual Fix Required: Complex issues need manual attention:
- Click issue to highlight affected nodes
- Follow the suggested fix
- Re-run analyzer to verify
Pro Tip: Run the analyzer after each major edit session. It's faster to fix issues incrementally than all at once.
Best Practices
When to Analyze
✅ Always analyze:
- Before sharing flowcharts with team
- Before exporting to PDF/PNG
- After AI-generated content
- Before final documentation
✅ Good practice:
- After completing a workflow section
- When flowchart exceeds 10 nodes
- Before switching to another project
❌ Not necessary:
- After every single node addition
- For simple 3-4 node workflows
- During initial brainstorming
Interpreting Scores
Don't obsess over perfect 100 scores:
- 95+: Excellent, diminishing returns
- 85-94: Professional quality
- 70-84: Good for internal use
- Below 70: Needs revision
Context matters - a quick internal sketch doesn't need the same score as client-facing documentation.
False Positives
The analyzer occasionally flags valid patterns:
Intentional dead ends:
Process → "Show Error Message" (deliberate termination)
You can mark issues as "Won't Fix" or "Acknowledged"
Complex loops:
Sophisticated loop logic may be flagged as potentially infinite
Add a comment explaining the exit condition
Plan Requirements
Free Plan
- ❌ AI Quality Analysis not available
- ✅ Basic manual validation
- ✅ Visual error indicators
Pro Plan ($12/mo)
- ✅ 50 analyses per month
- ✅ Full error detection
- ✅ ISO 5807 compliance checking
- ✅ Quality score and metrics
- ✅ Improvement suggestions
Enterprise Plan ($49/mo)
- ✅ Unlimited analyses
- ✅ Advanced logic verification
- ✅ Custom compliance rules
- ✅ Batch analysis
- ✅ API access for automation
- ✅ Team quality benchmarks
Pro Plan Required: Quality Analysis is a Pro feature. Upgrade to access automated validation, compliance checking, and improvement suggestions.
Current Limitations
Demo Implementation
- Currently uses rule-based detection (not full AI)
- Pattern matching for common errors
- Full machine learning model coming in Q2 2025
Analysis Scope
- Analyzes structure and logic only
- Doesn't evaluate business logic correctness
- Can't validate domain-specific rules
Language Support
- Best results with English labels
- Danish support improving
- Other languages: basic validation only
Performance
- Large flowcharts (100+ nodes) take longer
- Complex loops increase analysis time
- Typical analysis: 2-5 seconds
Troubleshooting
"Analysis taking too long"
- Large flowcharts (100+ nodes) may take 10-15 seconds
- Complex nested loops increase processing time
- Try analyzing smaller sections separately
"False positive errors"
- Mark as "Won't Fix" to suppress
- Add comments explaining intentional patterns
- Report persistent false positives via feedback
"Score seems too low"
- Review each issue carefully
- Minor issues accumulate quickly
- Focus on critical errors first
- Not all warnings need fixing
"Auto-fix broke my flowchart"
- Undo immediately with Cmd/Ctrl + Z
- Auto-fix works best for simple issues
- Complex fixes need manual review
- Report bugs via support
Keyboard Shortcuts
| Shortcut | Action |
|----------|--------|
| Cmd/Ctrl + Shift + A | Run quality analysis |
| Cmd/Ctrl + Shift + R | Re-run last analysis |
| Escape | Close analysis panel |
| Up/Down Arrows | Navigate between issues |
| Enter | Jump to selected issue |
| Cmd/Ctrl + F | Fix selected issue (if auto-fix available) |
Related Features
- AI Prompt Bar - Create flowcharts that analyzer validates
- Shape Reference - Learn ISO 5807 shape standards
- Export & Sharing - Share validated flowcharts with confidence
Next Steps
- Learn ISO 5807 Standards in depth
- Try Best Practices Tutorial
Ready to validate? Open any flowchart, press Cmd/Ctrl + Shift + A, and get instant quality feedback. Fix issues one by one and watch your score improve!
