Skip to Content

Requirements Priority Matrix

Version 2.1 by Robert Schaub on 2025/12/22 20:48

Requirements Importance Matrix

This page shows all functional, non-functional, and user needs requirements ordered by urgency and importance.

Note: Implementation phases (POC1, POC2, Beta 0, V1.0) are defined in POC Requirements and Implementation Roadmap, not in this importance matrix.

Importance and Urgency Levels

How Requirements are Prioritized:

  • Importance = f(risk, impact, strategy)
  • What happens if we don't do this? (risk)
  • How much value does it create? (impact)
  • Does it align with our strategic direction? (strategy)
  • Urgency = f(fail fast and learn, legal, promises made)
  • Do we need this to validate core assumptions? (fail fast and learn)
  • Are we legally required to have this? (legal)
  • Have we committed to delivering this? (promises made)

Importance Levels:

  • CRITICAL - System doesn't work without it, or major safety/legal risk
  • HIGH - Core functionality, essential for success
  • MEDIUM - Important but not blocking
  • LOW - Nice to have, can be deferred

Urgency Levels:

  • HIGH - Immediate need (critical for proof of concept)
  • MEDIUM - Important but not immediate
  • LOW - Future enhancement

Functional & Non-Functional Requirements

All requirements are sorted by Urgency (HIGH → LOW), then Importance (CRITICAL → LOW).

 ID  Title  Importance  Urgency  Comment
 HIGH URGENCY 
 FR7  Automated Verdicts (Enhanced with Quality Gates)  CRITICAL  HIGH  Core AKEL capability - system cannot function without automated verdict generation
 NFR11  AKEL Quality Assurance Framework  CRITICAL  HIGH  Without quality gates, automated analysis cannot be trusted
 FR4  Analysis Summary (Enhanced with Quality Metadata)  HIGH  HIGH  Essential for users to understand and trust verdicts
 MEDIUM URGENCY 
 NFR12  Security Controls  CRITICAL  MEDIUM  Essential for production deployment
 FR44  ClaimReview Schema Implementation  HIGH  MEDIUM  Required for search engine discoverability
 FR45  User Corrections Notification System  HIGH  MEDIUM  Critical for user trust and transparency
 FR48  Safety Framework for Contributors  HIGH  MEDIUM  Protects contributors from harassment
 NFR13  Quality Metrics Transparency  HIGH  MEDIUM  Users need to understand quality levels
 FR46  Image Verification System  MEDIUM  MEDIUM  
 FR47  Archive.org Integration  MEDIUM  MEDIUM  
 FR49  A/B Testing Framework  MEDIUM  MEDIUM  
 LOW URGENCY 
 FR50  OSINT Toolkit Integration  HIGH  LOW  Valuable capability for future phases
 FR51  Video Verification System  HIGH  LOW  Valuable capability for future phases
 FR52  Interactive Detection Training  MEDIUM  LOW 
 FR53  Cross-Organizational Sharing  MEDIUM  LOW 
 FR54  Evidence Deduplication  CRITICAL  LOW  Essential for data integrity and user trust

Total: 16 requirements (13 Functional, 3 Non-Functional)

Total: 20 User Needs

See Also