Skip to content

Phase 2 — Requirements Elicitation

Phase 2 transforms the high-level Vision & Scope defined in Phase 1 into structured, evidence-based, and traceable user requirements.

This phase corresponds to the Elicitation stage of the Requirements Engineering lifecycle and focuses on discovering stakeholder needs, constraints, expectations, and priorities.

Multiple elicitation techniques were applied to ensure comprehensive requirement coverage and reduce ambiguity.

Elicitation Approach

  • Stakeholder Interviews

    Semi-structured interviews were used to uncover workflows, expectations, and concerns from key stakeholders.

  • Bilingual Survey

    A broader survey validated usability preferences, language needs, and security expectations.

  • Document Analysis

    PDPL and public-health references were reviewed to ground the requirements in regulatory evidence.

  • Observation

    Current family health-tracking habits were examined to identify pain points and informal workarounds.

  • Competitive Review

    Similar platforms were reviewed to identify market gaps and differentiation opportunities.

  • Traceable Output

    All extracted requirements are documented consistently, classified, prioritized with MoSCoW, and linked to supporting evidence.

Phase Deliverables

  • Elicitation Plan

    Defines objectives, techniques, risks, and expected outputs.

  • Stakeholder Analysis

    Profiles stakeholder interests, attitudes, and constraints.

  • Interview Notes

    Structured session records and extracted findings.

  • Survey Findings

    Quantitative usability insights and preference trends.

  • Prioritized User Requirements

    Functional and non-functional requirements classified and ranked using MoSCoW.

  • Document & Competitive Analysis

    Regulatory review and market gap analysis supporting requirements.