4. Interviews (Elicitation Notes + Evidence)¶
Interviews were conducted as a primary elicitation technique to gather qualitative insights from key stakeholders. The objective was to identify user needs, constraints, expectations, and potential risks related to hereditary health tracking and preventive alerts.
4.1 Interview Guide¶
Objectives¶
The interview guide was designed to:
- Understand current methods of tracking family health history
- Identify expectations regarding preventive alerts
- Explore privacy and trust concerns
- Assess usability requirements
- Identify workflow expectations from healthcare providers
Stakeholder Groups Interviewed¶
- Family Users (Primary End Users)
- Healthcare Providers
Questions were aligned with project goals and structured to extract both functional and non-functional requirements.
4.2 Interview Session 1 — Family Users¶
Participant Profile¶
- Relationship status: (e.g., parent, adult child)
- Familiarity with digital health tools:
- Health tracking experience:
Key Questions Asked¶
- How do you currently track family health history?
- Would you use a digital system to record hereditary conditions?
- What concerns would you have about storing health data?
- What type of alerts would you find helpful?
- What would make the system easy to use?
Observations & Responses¶
(To be completed)
Preliminary Insights¶
(To be completed)
4.3 Interview Session 2 — Healthcare Provider¶
Participant Profile¶
- Role (e.g., general practitioner, cardiologist)
- Years of experience:
- Experience with digital systems:
Key Questions Asked¶
- Do patients provide structured family health history?
- Would a summarized hereditary risk profile be useful?
- What information format would be most helpful?
- What concerns would you have about integrating such a system?
- What would increase your willingness to use it?
Observations & Responses¶
(To be completed)
Preliminary Insights¶
(To be completed)
4.4 Key Findings¶
After analyzing both interview sessions, the following themes emerged:
- (Finding 1 — e.g., Strong privacy concerns among family users)
- (Finding 2 — e.g., Providers require concise risk summaries)
- (Finding 3 — e.g., High usability expectations for mobile interface)
- (Finding 4 — e.g., Need for clear consent transparency)
4.5 Extracted Requirements¶
The following requirements were derived from interview findings:
| ID | Type | Requirement | Source |
|---|---|---|---|
| FR-? | Functional | System shall allow structured family profile creation | Interview – Family |
| NFR-? | Security | System shall provide explicit consent confirmation | Interview – Family |
| FR-? | Functional | System shall generate concise risk summaries | Interview – Provider |
| NFR-? | Usability | System shall support mobile-first interaction | Interview – Family |
(Complete with actual IDs once finalized.)
4.6 Attached Evidence¶
The following artifacts are attached as supporting evidence:
- Interview transcripts (anonymized)
- Audio recordings (if applicable)
- Signed consent forms (if required)
- Interview notes
These materials support traceability between elicitation activities and derived system requirements.