Skip to content
SE311 · Prince Sultan University

Heart disease runs in families. So should prevention.

Sillah (صلة) is a family health management system that turns scattered family history into early warnings for hereditary cardiac risk. This site documents its full requirements lifecycle, from inception and elicitation to analysis and a prioritised specification.

SA GA GS SK Four-person team · SE311 Software Requirements Engineering
Risk alert Hereditary CAD · 2 generations
~/sillah/family-tree risk engine
GEN 1 GEN 2 GEN 3 GF GM AU M F S YOU heart disease · 50 high cholesterol screening due
Next step Lipid panel booked
scroll
30
Functional requirements across the analysed scope
6
Core features, four of them high-priority
3
Stakeholder groups: families, providers, admins
17+
Non-functional and operational constraints
00 · Abstract

Most cardiac risk is visible years before the emergency.

Inherited heart conditions are often identified late. The signals are usually there already, in a parent's diagnosis or a grandparent's age at first event, but they are spread across people, memories and paper records.

Sillah gives families one place to record that history, applies rule-based risk checks across generations, and moves people from an alert to a screening appointment with a provider.

This project delivers the requirements baseline for that system: 30 testable functional requirements, a domain model, use cases, and a prioritised release scope, all traced to stakeholder needs.

01 · Prevention design

Four ideas shape every requirement.

Each requirement traces back to at least one of these prevention goals.

focus / 01

Early risk identification

Capture and structure family history so inherited risk patterns surface as early as possible, before the first cardiac event.

focus / 02

Preventive guidance

Clear recommendations and reminders that encourage regular screening and healthier habits.

focus / 03

Clinical readiness

Appointment workflows that move a family from alert to provider action quickly.

focus / 04

Governance & trust

Traceability, validation and change control keep health-related requirements reliable as the system evolves.

02 · Requirements lifecycle

From a problem statement to a prioritised specification.

Three phases are documented page by page on this site. Specification, validation and management are covered in the final report.

  1. 01 Inception Business goals, scope boundaries and strategic context. 4 pages →
  2. 02 Elicitation Interviews, a survey and document analysis across three stakeholder groups. 9 pages →
  3. 03 Analysis Domain model, use cases, functional and non-functional requirements, and priorities. 6 pages →
  4. 04–06 Specification · Validation · Management SRS consolidation, quality checks, traceability and change control. In the report →
03 · Prototype

The requirements, as screens.

Patient and doctor portals from the Sillah prototype. Click any screen to enlarge it.

04 · Stakeholders

Three groups, three sets of needs.

05 · Deliverables

Read the full report.

Three written phase reports and the final presentation, available to download or read in the browser.