Wiki source code of Requirements Priority Matrix
Last modified by Robert Schaub on 2025/12/23 11:35
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 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 V0\.9\.78.Specification.Requirements-Roadmap-Matrix.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 | |||
| 23 | * **CRITICAL** - System doesn't work without it, or major safety/legal risk | ||
| 24 | * **HIGH** - Core functionality, essential for success | ||
| 25 | * **MEDIUM** - Important but not blocking | ||
| 26 | * **LOW** - Nice to have, can be deferred | ||
| 27 | |||
| 28 | **Urgency Levels:** | ||
| 29 | |||
| 30 | * **HIGH** - Immediate need (critical for proof of concept) | ||
| 31 | * **MEDIUM** - Important but not immediate | ||
| 32 | * **LOW** - Future enhancement | ||
| 33 | |||
| 34 | == Functional & Non-Functional Requirements == | ||
| 35 | |||
| 36 | All requirements are sorted by Urgency (HIGH → LOW), then Importance (CRITICAL → LOW). | ||
| 37 | |||
| 38 | |= ID |= Title |= Importance |= Urgency |= Comment | ||
| 39 | | **HIGH URGENCY** ||||\\ | ||
| 40 | | **FR7** | Automated Verdicts (Enhanced with Quality Gates) | CRITICAL | HIGH | Core AKEL capability - system cannot function without automated verdict generation | ||
| 41 | | **NFR11** | AKEL Quality Assurance Framework | CRITICAL | HIGH | Without quality gates, automated analysis cannot be trusted | ||
| 42 | | **FR4** | Analysis Summary (Enhanced with Quality Metadata) | HIGH | HIGH | Essential for users to understand and trust verdicts | ||
| 43 | | **MEDIUM URGENCY** ||||\\ | ||
| 44 | | **NFR12** | Security Controls | CRITICAL | MEDIUM | Essential for production deployment | ||
| 45 | | **FR44** | ClaimReview Schema Implementation | HIGH | MEDIUM | Required for search engine discoverability | ||
| 46 | | **FR45** | User Corrections Notification System | HIGH | MEDIUM | Critical for user trust and transparency | ||
| 47 | | **FR48** | Safety Framework for Contributors | HIGH | MEDIUM | Protects contributors from harassment | ||
| 48 | | **NFR13** | Quality Metrics Transparency | HIGH | MEDIUM | Users need to understand quality levels | ||
| 49 | | **FR46** | Image Verification System | MEDIUM | MEDIUM |\\ | ||
| 50 | | **FR47** | Archive.org Integration | MEDIUM | MEDIUM |\\ | ||
| 51 | | **FR49** | A/B Testing Framework | MEDIUM | MEDIUM |\\ | ||
| 52 | | **LOW URGENCY** ||||\\ | ||
| 53 | | **FR54** | Evidence Deduplication | CRITICAL | LOW | Essential for data integrity and preventing duplicate processing | ||
| 54 | | **FR50** | OSINT Toolkit Integration | HIGH | LOW | Valuable capability for future phases (geolocation, chronolocation, social media analysis) | ||
| 55 | | **FR51** | Video Verification System | HIGH | LOW | Valuable capability for future phases (deepfake detection, frame analysis) | ||
| 56 | | **FR52** | Interactive Detection Training | MEDIUM | LOW |\\ | ||
| 57 | | **FR53** | Cross-Organizational Sharing | MEDIUM | LOW | | ||
| 58 | |||
| 59 | **Total:** 16 requirements (13 Functional, 3 Non-Functional) | ||
| 60 | |||
| 61 | == User Needs Importance == | ||
| 62 | |||
| 63 | 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. | ||
| 64 | |||
| 65 | |= ID |= Title |= Drives Requirements |= Comment | ||
| 66 | | **UN-1** | Trust Assessment at a Glance | FR7, NFR13 |\\ | ||
| 67 | | **UN-2** | Claim Extraction and Verification | FR7 |\\ | ||
| 68 | | **UN-3** | Article Summary with FactHarbor Analysis Summary | FR4 |\\ | ||
| 69 | | **UN-4** | Social Media Fact-Checking | FR7 |\\ | ||
| 70 | | **UN-5** | Source Provenance and Track Records | FR4 |\\ | ||
| 71 | | **UN-6** | Publisher Reliability History | FR4 |\\ | ||
| 72 | | **UN-7** | Evidence Transparency | FR4, NFR13 |\\ | ||
| 73 | | **UN-8** | Understanding Disagreement and Consensus | FR7 |\\ | ||
| 74 | | **UN-9** | Methodology Transparency | NFR13 |\\ | ||
| 75 | | **UN-10** | Manipulation Tactics Detection | FR52 |\\ | ||
| 76 | | **UN-11** | Filtered Research | FR54 |\\ | ||
| 77 | | **UN-12** | Submit Unchecked Claims | FR7 |\\ | ||
| 78 | | **UN-13** | Cite FactHarbor Verdicts | FR44 |\\ | ||
| 79 | | **UN-14** | API Access for Integration | FR44 |\\ | ||
| 80 | | **UN-15** | Verdict Evolution Timeline | NFR13 |\\ | ||
| 81 | | **UN-16** | AI vs. Human Review Status | NFR13 |\\ | ||
| 82 | | **UN-17** | In-Article Claim Highlighting | FR7 |\\ | ||
| 83 | | **UN-26** | Search Engine Visibility | FR44 |\\ | ||
| 84 | | **UN-27** | Visual Claim Verification | FR46, FR51 |\\ | ||
| 85 | | **UN-28** | Safe Contribution Environment | FR48 |\\ |