Skip to main content

Analytics Dashboard

The Analytics workspace provides four powerful analysis tools for requirements traceability, coverage, compliance reporting, and custom dashboards.

Accessing Analytics​

Click the Analytics icon (brain icon) in the left navigation.

Five Analytics Tools​

  1. Dashboard Builder: Custom dashboards with widgets
  2. AI Guardrails: Project health scoring, FMEA gap analysis, and release readiness checks
  3. Traceability Matrix: Requirement relationship mapping
  4. Coverage Analysis: Test coverage and traceability metrics
  5. Compliance Reports: Industry standard compliance (ISO 26262, DO-178C, etc.)

1. Dashboard Builder​

Purpose​

Create custom analytics dashboards tailored to different stakeholders (engineering, management, QA).

Available Widgets​

Requirements Summary​

  • Count of requirements by type
  • Count by status (Draft, Approved, Implemented)
  • Breakdown by hierarchy level
  • Recently modified requirements

Traceability Coverage​

  • Percentage of requirements with traces
  • Orphaned requirements count
  • Traceability gaps by type
  • Upstream/downstream coverage

FMEA Summary​

  • High-risk items (RPN > 100)
  • Average RPN across project
  • FMEA completion rate
  • Top 10 failure modes by RPN

Activity Timeline​

  • Recent requirement changes
  • Recent FMEA updates
  • Comment activity
  • User activity breakdown

Compliance Status​

  • Progress toward compliance goals
  • Open compliance issues
  • Requirements coverage by standard
  • Audit readiness score

How to Use​

  1. Click "Analytics" in left navigation
  2. Click "Dashboard" tab
  3. Click "+ Add Widget" button
  4. Select widget type from dropdown
  5. Configure widget settings:
    • Title
    • Refresh interval
    • Filters (type, status, date range)
  6. Click "Add to Dashboard"
  7. Drag widgets to rearrange
  8. Resize widgets by dragging corners
  9. Click "Save Layout" to persist

Widget Actions​

  • Refresh: Update widget data (click refresh icon)
  • Edit: Modify widget settings (click edit icon)
  • Remove: Delete widget from dashboard (click X icon)
  • Fullscreen: Expand widget (click expand icon)

Dashboard Management​

  • Save: Persist layout and widgets
  • Reset: Restore default dashboard
  • Export: Download dashboard as PDF
  • Share: Generate shareable link (coming soon)

2. AI Guardrails​

Purpose​

Assess project quality through automated scoring, identify FMEA coverage gaps, and evaluate release readiness -- all from a single dashboard.

Project Health Score​

A composite 0-100 score that grades your project across five weighted categories.

How the Score is Calculated​

CategoryWeightWhat It Measures
FMEA Coverage25 points% of requirements linked to FMEA analyses
Test Coverage25 points% of requirements with test cases
Action Completion20 points% of high-priority actions completed
Traceability15 points% of requirements with links, parents, or test cases
On-Time Delivery15 pointsPenalty for overdue action items

Grade Scale​

GradeScoreMeaning
A85-100Excellent -- project is well-managed
B70-84Good -- minor improvements possible
C50-69Needs Improvement -- significant gaps exist
D30-49At Risk -- many areas need attention
F0-29Critical -- immediate action required
tip

Click the info icon next to "Project Health" to see this formula directly in the app.

How to Use​

  1. Navigate to Analytics > AI Guardrails tab
  2. The health score loads automatically
  3. Review each category's progress bar to identify weak areas
  4. Click the refresh button to recalculate after making changes

FMEA Gap Analysis​

Identifies all requirements without FMEA coverage and uses AI to suggest failure modes.

Running the Analysis​

  1. Click "Run Gap Analysis" in the FMEA Gap Analysis card
  2. The system finds all uncovered requirements
  3. AI generates 3-5 failure mode suggestions for up to 10 uncovered requirements
  4. Results are cached for 30 minutes -- they persist when switching tabs

Reviewing AI Suggestions​

Each AI-suggested failure mode shows:

  • Failure mode name and RPN (Risk Priority Number)
  • Function, Effect, Cause, S/O/D ratings
  • Recommendations for mitigation

For each suggestion, you can:

  • Accept (green check) -- include as-is in your FMEA
  • Modify & Accept (pencil icon) -- edit fields (function, cause, S/O/D, etc.) then accept
  • Reject (red X) -- skip this suggestion
Batch Save Pattern

Changes are not saved immediately. Make all your accept/modify/reject decisions first, then click "Save All Decisions" to create the FMEA items in one batch. This avoids disruptive page refreshes.

Bulk Actions​

  • Accept All Pending -- accept all remaining suggestions at once
  • Reject All Pending -- reject all remaining suggestions

Addressing Uncovered Requirements​

Requirements that didn't receive AI suggestions are listed in the "Other Uncovered Requirements" section. For each one, you can:

  • AI Generate -- generate AI failure mode suggestions for that specific requirement
  • Add Manual -- open an inline form to enter a failure mode manually (function, failure mode, cause, effect, S/O/D, recommendations)

Both AI-generated and manually added entries participate in the same "Save All Decisions" workflow.

Release Readiness Check​

Evaluates your project against five quality gates to determine if it's ready for release.

Quality Gates​

GatePassWarningFail
FMEA Coverage>= 90%70-89%< 70%
Test Coverage>= 80%50-79%< 50%
Action Items0 open high/critical--Any open
High-Risk Items0 unmitigated (RPN>200)1-3 items> 3 items
Overdue Items0 overdue--Any overdue

Overall Verdict​

  • Ready for Release -- all gates pass
  • Conditional -- warnings present but no failures
  • Not Ready -- one or more gates failed

How to Use​

  1. Click "Run Readiness Check"
  2. Review each gate's pass/warning/fail status
  3. Results are cached for 15 minutes
  4. Click "Re-run check" after addressing issues
note

Both FMEA Gap Analysis and Release Readiness results are cached and persist when you navigate away from the AI Guardrails tab. You won't need to re-run them every time you switch tabs.

3. Traceability Matrix​

Purpose​

Map requirement relationships and dependencies to ensure complete coverage and identify gaps.

Features​

Matrix View​

  • Rows: Source requirements (e.g., Customer Requests)
  • Columns: Target requirements (e.g., System Requirements)
  • Cells: Traceability links (click to view)
  • Color coding:
    • Green: Fully traced
    • Yellow: Partially traced
    • Red: Not traced

Relationship Types​

  • Parent-Child: Hierarchical decomposition
  • Derived-From: Requirement derivation
  • Satisfies: Implementation relationship
  • Verified-By: Test verification
  • Depends-On: Dependency relationship

How to Use​

  1. Click "Analytics" in left navigation
  2. Click "Traceability Matrix" tab
  3. Select row type (source requirements):
    • Customer Request
    • System Requirement
    • Subsystem Requirement
  4. Select column type (target requirements):
    • System Requirement
    • Function Requirement
    • Detailed Requirement
  5. Matrix populates automatically
  6. Click cell to view relationship details:
    • Source requirement text
    • Target requirement text
    • Relationship type
    • Creation date
  7. Filter matrix by:
    • Requirement status
    • Date range
    • User who created link
  8. Export matrix:
    • Excel (.xlsx)
    • PDF (formatted report)
    • CSV (raw data)

Interpreting the Matrix​

Full Coverage (Green cell):

  • Every source requirement traces to at least one target
  • Indicates complete decomposition

Partial Coverage (Yellow cell):

  • Some source requirements lack traces
  • Review needed

No Coverage (Red cell):

  • No traceability links exist
  • Immediate action required

Finding Gaps​

  1. In Traceability Matrix, look for red/yellow cells
  2. Click cell to see which requirements lack traces
  3. Click requirement to navigate and add trace links
  4. Return to matrix to verify coverage

4. Coverage Analysis​

Purpose​

Analyze requirement test coverage and traceability completeness.

Metrics Tracked​

Traceability Coverage​

  • Formula: (Requirements with traces / Total requirements) × 100
  • Target: 100% for safety-critical projects
  • Breakdown: By requirement type

Test Coverage​

  • Formula: (Requirements with tests / Total requirements) × 100
  • Target: 100% for verified requirements
  • Breakdown: By test type (unit, integration, system)

Orphaned Requirements​

  • Requirements with no parent (except root level)
  • Requirements with no children (leaf nodes expected to have children)
  • Requirements with no traces (upstream or downstream)

Coverage by Type​

  • Customer Request coverage
  • System Requirement coverage
  • Subsystem Requirement coverage
  • Function Requirement coverage
  • Detailed Requirement coverage

How to Use​

  1. Click "Analytics" in left navigation
  2. Click "Coverage Analysis" tab
  3. View main dashboard showing:
    • Overall coverage percentage (large metric)
    • Coverage by type (bar chart)
    • Traceability heatmap
    • Trend over time (line chart)
  4. Click "View Untraced Requirements" to see gaps:
    • Requirement ID
    • Type
    • Text preview
    • Action: "Add Trace" button
  5. Click "View Orphaned Requirements" to see isolated items
  6. Use filters:
    • Date range (show coverage at specific point in time)
    • Requirement type
    • Status (include/exclude draft requirements)
  7. Export coverage report:
    • PDF (formatted report with charts)
    • Excel (raw data for analysis)

Coverage Best Practices​

Traceability Targets:

  • Safety-critical: 100%
  • Business-critical: 95%
  • Non-critical: 80%

Review Frequency:

  • Before milestones
  • After major requirement changes
  • Monthly for active projects

Gap Resolution:

  1. Identify untraced requirements
  2. Determine if trace is needed (some leaf requirements may not need downstream traces)
  3. Add appropriate traceability links
  4. Re-run coverage analysis
  5. Export report for records

5. Compliance Reports​

Purpose​

Generate compliance reports for industry standards to support audits and certifications.

Supported Standards​

Automotive​

  • ISO 26262: Functional safety for automotive (ASIL A/B/C/D)
  • ASPICE: Automotive software process improvement

Aerospace​

  • DO-178C: Software for airborne systems (DAL A/B/C/D)
  • DO-254: Hardware for airborne systems

Medical​

  • IEC 62304: Medical device software lifecycle (Class A/B/C)
  • ISO 13485: Medical devices quality management

Industrial​

  • IEC 61508: Functional safety for industrial (SIL 1/2/3/4)

Report Contents​

Each compliance report includes:

  1. Executive Summary:

    • Compliance score (%)
    • Pass/fail status
    • Critical findings count
    • Recommendation summary

  2. Requirements Completeness:

    • All standard requirements addressed?
    • Requirement text quality check
    • Unique ID verification

  3. Traceability Verification:

    • Upstream traceability complete?
    • Downstream traceability complete?
    • Bi-directional traceability confirmed?

  4. Test Coverage Analysis:

    • Requirements verified by tests?
    • Test coverage percentage
    • Unverified requirements list

  5. Documentation Gaps:

    • Missing requirement descriptions
    • Missing test cases
    • Missing verification results

  6. Compliance Issues:

    • Critical issues (must fix)
    • Major issues (should fix)
    • Minor issues (nice to fix)
    • Each issue with:
      • Description
      • Affected requirements
      • Remediation steps
      • Priority

  7. Action Items:

    • Tasks to achieve compliance
    • Assigned owners
    • Due dates
    • Status tracking

How to Generate Report​

  1. Click "Analytics" in left navigation
  2. Click "Compliance Reports" tab
  3. Click "+ Generate New Report" button
  4. Select standard from dropdown:
    • ISO 26262 (Automotive)
    • DO-178C (Aerospace)
    • IEC 62304 (Medical)
    • IEC 61508 (Industrial)
    • etc.
  5. Select compliance level:
    • ISO 26262: ASIL A/B/C/D
    • DO-178C: DAL A/B/C/D/E
    • IEC 62304: Class A/B/C
    • IEC 61508: SIL 1/2/3/4
  6. Configure report options:
    • Include draft requirements? (Yes/No)
    • Include internal requirements? (Yes/No)
    • Date range (all time or specific period)
  7. Click "Generate Report"
  8. Wait for generation (may take 30-60 seconds)
  9. Review report in browser
  10. Export to PDF for distribution

Report Actions​

View Compliance Issues:

  1. In generated report, click "View Issues" tab
  2. Filter by severity (Critical, Major, Minor)
  3. Click issue to see details:
    • Issue description
    • Standard requirement reference
    • Affected project requirements
    • Remediation steps
  4. Click "Resolve" to mark as fixed
  5. Add resolution notes

Export Report:

  1. Click "Export" button
  2. Select format:
    • PDF (formatted, suitable for audits)
    • Excel (raw data for analysis)
    • HTML (web page)
  3. File downloads automatically

Share Report:

  1. Click "Share" button
  2. Generate shareable link (read-only)
  3. Copy link and send to stakeholders

Interpreting Compliance Score​

90-100%: Excellent - Ready for audit 80-89%: Good - Minor gaps to address 70-79%: Fair - Significant work needed <70%: Poor - Major compliance issues

Compliance Workflow​

  1. Early Analysis (Design Phase):

    • Generate initial compliance report
    • Identify major gaps
    • Plan remediation work

  2. Iterative Improvement (Development):

    • Re-run report monthly
    • Track compliance score trend
    • Address high-priority issues first

  3. Pre-Audit Preparation (Before Audit):

    • Generate final compliance report
    • Ensure 95%+ compliance
    • Export PDF for auditor

  4. Post-Audit (After Audit):

    • Address auditor findings
    • Re-generate report
    • Achieve 100% compliance

Analytics Best Practices​

Dashboard Usage​

  • Create role-specific dashboards:
    • Engineering: Requirements and FMEA widgets
    • Management: Compliance and progress widgets
    • QA: Coverage and traceability widgets
  • Refresh dashboards before standup meetings
  • Export dashboards for weekly reports

Traceability Matrix​

  • Run traceability analysis before major milestones
  • Review matrix after bulk requirement imports
  • Use matrix to validate decomposition logic
  • Export matrix for traceability documentation

Coverage Analysis​

  • Set target coverage percentages
  • Review weekly during active development
  • Investigate coverage drops immediately
  • Use untraced requirements report as action list

Compliance Reports​

  • Generate early to identify gaps
  • Track compliance score over time
  • Address critical issues first
  • Export for compliance documentation

Troubleshooting​

"Widgets show no data"​

Status: Frontend components need backend API integration (in progress) Workaround: Backend APIs are ready, frontend wiring in development

"Traceability matrix is empty"​

Cause: No traceability links created yet Solution: Use requirement linking features to establish traces

"Coverage shows 0%"​

Cause: No test cases or traces created Solution: Add traceability links and test cases

"Can't generate compliance report"​

Status: Frontend components need backend API integration (in progress) Workaround: Backend APIs are ready, frontend wiring in development

Status​

FeatureBackendFrontendAvailable
Dashboard Builder✅⚠️Partial
AI Guardrails - Health Score✅✅Yes
AI Guardrails - FMEA Gap Analysis✅✅Yes
AI Guardrails - Release Readiness✅✅Yes
Traceability Matrix✅⚠️Partial
Coverage Analysis✅⚠️Partial
Compliance Reports✅⚠️Partial

⚠️ = Backend ready, frontend integration in progress