Skip to Content

Wiki source code of Requirements Priority Matrix

Version 1.1 by Robert Schaub on 2025/12/23 14:53
Show last authors
1 = Requirements Importance Matrix =
2
3 This page shows all functional, non-functional, and user needs requirements ordered by urgency and importance.
4
5 **Note:** Implementation phases and requirement-to-phase mapping are defined in [[Requirements Roadmap Matrix>>Test.FactHarbor.Roadmap.Requirements-Roadmap-Matrix.WebHome]], not in this importance matrix.
6
7 {{info}}
8 **Scope:** This matrix prioritizes the 16 formal system requirements that have full specifications in the [[Requirements>>Test.FactHarbor.Specification.Requirements.WebHome]] page. POC-specific implementation requirements (FR1-FR3, FR5-FR6, FR8, FR11, FR13, NFR1-NFR3) are detailed in [[POC Requirements>>Test.FactHarbor.Specification.POC.Requirements]] and mapped to phases in the [[Requirements Roadmap Matrix>>Test.FactHarbor.Roadmap.Requirements-Roadmap-Matrix.WebHome]].
9 {{/info}}
10
11 == Importance and Urgency Levels ==
12
13 **How Requirements are Prioritized:**
14
15 * **Importance** = f(risk, impact, strategy)
16 * What happens if we don't do this? (risk)
17 * How much value does it create? (impact)
18 * Does it align with our strategic direction? (strategy)
19
20 * **Urgency** = f(fail fast and learn, legal, promises made)
21 * Do we need this to validate core assumptions? (fail fast and learn)
22 * Are we legally required to have this? (legal)
23 * Have we committed to delivering this? (promises made)
24
25 **Importance Levels:**
26 * **CRITICAL** - System doesn't work without it, or major safety/legal risk
27 * **HIGH** - Core functionality, essential for success
28 * **MEDIUM** - Important but not blocking
29 * **LOW** - Nice to have, can be deferred
30
31 **Urgency Levels:**
32 * **HIGH** - Immediate need (critical for proof of concept)
33 * **MEDIUM** - Important but not immediate
34 * **LOW** - Future enhancement
35
36 == Functional & Non-Functional Requirements ==
37
38 All requirements are sorted by Urgency (HIGH → LOW), then Importance (CRITICAL → LOW).
39
40 |= ID |= Title |= Importance |= Urgency |= Comment
41 | **HIGH URGENCY** ||||
42 | **FR7** | Automated Verdicts (Enhanced with Quality Gates) | CRITICAL | HIGH | Core AKEL capability - system cannot function without automated verdict generation
43 | **NFR11** | AKEL Quality Assurance Framework | CRITICAL | HIGH | Without quality gates, automated analysis cannot be trusted
44 | **FR4** | Analysis Summary (Enhanced with Quality Metadata) | HIGH | HIGH | Essential for users to understand and trust verdicts
45 | **MEDIUM URGENCY** ||||
46 | **NFR12** | Security Controls | CRITICAL | MEDIUM | Essential for production deployment
47 | **FR44** | ClaimReview Schema Implementation | HIGH | MEDIUM | Required for search engine discoverability
48 | **FR45** | User Corrections Notification System | HIGH | MEDIUM | Critical for user trust and transparency
49 | **FR48** | Safety Framework for Contributors | HIGH | MEDIUM | Protects contributors from harassment
50 | **NFR13** | Quality Metrics Transparency | HIGH | MEDIUM | Users need to understand quality levels
51 | **FR46** | Image Verification System | MEDIUM | MEDIUM |
52 | **FR47** | Archive.org Integration | MEDIUM | MEDIUM |
53 | **FR49** | A/B Testing Framework | MEDIUM | MEDIUM |
54 | **LOW URGENCY** ||||
55 | **FR54** | Evidence Deduplication | CRITICAL | LOW | Essential for data integrity and preventing duplicate processing
56 | **FR50** | OSINT Toolkit Integration | HIGH | LOW | Valuable capability for future phases (geolocation, chronolocation, social media analysis)
57 | **FR51** | Video Verification System | HIGH | LOW | Valuable capability for future phases (deepfake detection, frame analysis)
58 | **FR52** | Interactive Detection Training | MEDIUM | LOW |
59 | **FR53** | Cross-Organizational Sharing | MEDIUM | LOW |
60
61 **Total:** 16 requirements (13 Functional, 3 Non-Functional)
62
63 == User Needs Importance ==
64
65 User Needs (UN) are the foundation that drives functional and non-functional requirements. They are not independently prioritized; instead, their importance is inherited from the FR/NFR requirements they drive.
66
67 |= ID |= Title |= Drives Requirements |= Comment
68 | **UN-1** | Trust Assessment at a Glance | FR7, NFR13 |
69 | **UN-2** | Claim Extraction and Verification | FR7 |
70 | **UN-3** | Article Summary with FactHarbor Analysis Summary | FR4 |
71 | **UN-4** | Social Media Fact-Checking | FR7 |
72 | **UN-5** | Source Provenance and Track Records | FR4 |
73 | **UN-6** | Publisher Reliability History | FR4 |
74 | **UN-7** | Evidence Transparency | FR4, NFR13 |
75 | **UN-8** | Understanding Disagreement and Consensus | FR7 |
76 | **UN-9** | Methodology Transparency | NFR13 |
77 | **UN-10** | Manipulation Tactics Detection | FR52 |
78 | **UN-11** | Filtered Research | FR54 |
79 | **UN-12** | Submit Unchecked Claims | FR7 |
80 | **UN-13** | Cite FactHarbor Verdicts | FR44 |
81 | **UN-14** | API Access for Integration | FR44 |
82 | **UN-15** | Verdict Evolution Timeline | NFR13 |
83 | **UN-16** | AI vs. Human Review Status | NFR13 |
84 | **UN-17** | In-Article Claim Highlighting | FR7 |
85 | **UN-26** | Search Engine Visibility | FR44 |
86 | **UN-27** | Visual Claim Verification | FR46, FR51 |
87 | **UN-28** | Safe Contribution Environment | FR48 |