Wiki source code of Requirements Priority Matrix

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

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 (POC1, POC2, Beta 0, V1.0) are defined in [[POC Requirements>>Test.FactHarbor.Specification.POC.Requirements]] and [[Implementation Roadmap>>Test.FactHarbor.Roadmap.WebHome]], not in this importance matrix.
6
7 == Importance and Urgency Levels ==
8
9 **How Requirements are Prioritized:**
10
11 * **Importance** = f(risk, impact, strategy)
12 * What happens if we don't do this? (risk)
13 * How much value does it create? (impact)
14 * Does it align with our strategic direction? (strategy)
15
16 * **Urgency** = f(fail fast and learn, legal, promises made)
17 * Do we need this to validate core assumptions? (fail fast and learn)
18 * Are we legally required to have this? (legal)
19 * Have we committed to delivering this? (promises made)
20
21 **Importance Levels:**
22 * **CRITICAL** - System doesn't work without it, or major safety/legal risk
23 * **HIGH** - Core functionality, essential for success
24 * **MEDIUM** - Important but not blocking
25 * **LOW** - Nice to have, can be deferred
26
27 **Urgency Levels:**
28 * **HIGH** - Immediate need (critical for proof of concept)
29 * **MEDIUM** - Important but not immediate
30 * **LOW** - Future enhancement
31
32 == Functional & Non-Functional Requirements ==
33
34 All requirements are sorted by Urgency (HIGH → LOW), then Importance (CRITICAL → LOW).
35
36 |= ID |= Title |= Importance |= Urgency |= Comment
37 | **HIGH URGENCY** ||||
38 | **FR7** | Automated Verdicts (Enhanced with Quality Gates) | CRITICAL | HIGH | Core AKEL capability - system cannot function without automated verdict generation
39 | **NFR11** | AKEL Quality Assurance Framework | CRITICAL | HIGH | Without quality gates, automated analysis cannot be trusted
40 | **FR4** | Analysis Summary (Enhanced with Quality Metadata) | HIGH | HIGH | Essential for users to understand and trust verdicts
41 | **MEDIUM URGENCY** ||||
42 | **NFR12** | Security Controls | CRITICAL | MEDIUM | Essential for production deployment
43 | **FR44** | ClaimReview Schema Implementation | HIGH | MEDIUM | Required for search engine discoverability
44 | **FR45** | User Corrections Notification System | HIGH | MEDIUM | Critical for user trust and transparency
45 | **FR48** | Safety Framework for Contributors | HIGH | MEDIUM | Protects contributors from harassment
46 | **NFR13** | Quality Metrics Transparency | HIGH | MEDIUM | Users need to understand quality levels
47 | **FR46** | Image Verification System | MEDIUM | MEDIUM |
48 | **FR47** | Archive.org Integration | MEDIUM | MEDIUM |
49 | **FR49** | A/B Testing Framework | MEDIUM | MEDIUM |
50 | **LOW URGENCY** ||||
51 | **FR50** | OSINT Toolkit Integration | HIGH | LOW | Valuable capability for future phases
52 | **FR51** | Video Verification System | HIGH | LOW | Valuable capability for future phases
53 | **FR52** | Interactive Detection Training | MEDIUM | LOW |
54 | **FR53** | Cross-Organizational Sharing | MEDIUM | LOW |
55 | **FR54** | Evidence Deduplication | CRITICAL | LOW | Essential for data integrity and user trust
56
57 **Total:** 16 requirements (13 Functional, 3 Non-Functional)
58
59 **Total:** 20 User Needs
60
61 == See Also ==
62
63 * [[Requirements>>Test.FactHarbor.Specification.Requirements.WebHome]] - Detailed requirement specifications
64 * [[POC Requirements>>Test.FactHarbor.Specification.POC.Requirements]] - POC1 scope and simplifications
65 * [[Implementation Roadmap>>Test.FactHarbor.Roadmap.WebHome]] - Phase-by-phase implementation plan
66 * [[User Needs>>Test.FactHarbor.Specification.Requirements.User Needs.WebHome]] - Foundation that drives these requirements