Family Cardiac Prevention
Sillah (صلة) Family Health Management System¶
Sillah is a preventive health platform focused on reducing hereditary heart disease risk in Saudi families through early detection, structured family history tracking, and timely clinical action.
- University: Prince Sultan University (CCIS)
- Course: SE311 - Software Requirements Engineering
- Approach: Full requirements lifecycle from inception to management
Mission¶
Build a prevention-first system that helps families move from reactive treatment to proactive risk awareness and early intervention.
Problem Area¶
Inherited cardiac conditions are often identified late. Families need simple tools to capture health history and trigger preventive follow-up before critical events.
Outcome¶
A documented software requirements baseline for a health prevention system, including validated scope, traceability, and testable requirements.
Prevention Impact Snapshot¶
Lifecycle phases completed in this documentation set.
Core stakeholder groups analyzed: families, providers, administrators.
Requirements mapped toward prevention-oriented decisions and workflows.
Why prevention matters: cardiac risk signals in family history are often visible before severe outcomes occur. Sillah prioritizes earlier alerts, guidance, and scheduling support.
Prevention Design Focus¶
1) Early Risk Identification¶
Capture and structure family history to detect inherited risk patterns as soon as possible.
2) Preventive Guidance¶
Provide understandable recommendations and reminders that encourage regular screening and healthy behavior.
3) Clinical Readiness¶
Support appointment simulation workflows so users can move quickly from alert to provider action.
4) Governance and Trust¶
Use traceability, validation, and change control to keep health-related requirements reliable over time.
SE311 Requirements Lifecycle¶
Phase 1 - Inception¶
Defines business goals, project boundaries, and strategic context for a family cardiac prevention platform.
Phase 2 - Elicitation¶
Collects stakeholder needs through interviews, surveys, and document analysis to uncover prevention-driven requirements.
Phase 3 - Analysis¶
Converts collected inputs into structured models, prioritized requirements, and measurable quality constraints.
Phase 4 - Specification¶
Consolidates requirements into an SRS aligned with formal standards and implementation readiness.
Phase 5 - Validation¶
Verifies requirement quality and consistency to ensure the specification supports safe preventive workflows.
Phase 6 - Requirements Management¶
Maintains traceability and controlled change so the system can evolve without losing prevention objectives.
Navigate the Documentation¶
Use the navigation tabs and side menu to explore each phase, supporting artifacts, and the final report.