Skip to content

Phase 3 — Requirements Analysis

Phase 3 translates the elicited needs from Phase 2 into a structured analysis model and a draft Software Requirements Specification (SRS) for the Sillah Family Health Management System.

This phase focuses on clarifying system behavior, defining functional and non-functional requirements, and organizing the solution into use cases, domain entities, interfaces, and priorities.

Phase Purpose

The goal of this phase is to convert stakeholder expectations into a clear, implementable, and testable specification that can guide design and development.

This analysis package is based on the approved Phase 3 report and captures:

  • the system scope and intended release boundaries
  • the major use cases and interaction flows
  • functional requirements grouped by core feature area
  • non-functional, legal, security, and operational constraints
  • a domain model and data dictionary for core entities
  • implementation priority across the analyzed feature set

Core Analysis Outputs

  • Domain Model

    Defines the main entities in the Sillah system, including users, family members, health events, alerts, appointments, and dashboard summaries.

  • Use Cases

    Documents the primary end-to-end user interactions, with detailed emphasis on managing family members and navigating key system flows.

  • Functional Requirements

    Groups analyzed requirements into six features: account management, family member management, health event tracking, risk alerts, dashboard visualization, and database interaction.

  • Non-Functional Requirements

    Covers performance, safety, security, usability, reliability, legal/privacy, bilingual support, and database integrity.

  • Prioritization

    Classifies the features by delivery importance, highlighting the high-priority release scope versus medium-priority support features.

Phase 3 Page Set

The current Phase 3 documentation is intentionally organized into the five analysis pages shown in the section navigation:

  1. Domain Model
  2. Use Cases
  3. Functional Requirements
  4. Non-Functional Requirements
  5. Prioritization

No extra Phase 3 pages are required right now because the approved report’s appendix content is already folded into the existing analysis pages, especially the domain model and non-functional requirements.

Analysis Snapshot

  • 30 Functional Requirements
    Identified across the six analyzed system features.

  • 6 Core Features
    Four high-priority operational features and two medium-priority supporting features.

  • 5 User / Stakeholder Classes
    Including end users, managed family members, healthcare providers, feedback contributors, and evaluators.

  • 17+ Supporting Constraints
    Spanning operating environment, implementation constraints, communication, security, and regulatory expectations.

Supporting Report Artifact