Allocation View - SENG-350-2024-fall/Team-11 GitHub Wiki

Allocation View Documentation

Graphical Representation

The allocation view describes the mapping of the system’s software components to physical resources, infrastructure, and user devices. It highlights how the components interact with one another in the operational environment.

Key Elements in the Allocation View

Hardware/Infrastructure Layer

  • AWS Cloud:
    • Hosts the AWS Database component, which stores all system data securely.
    • Provides cloud-based infrastructure to ensure scalability and reliability.

Application Layer

  • Symptom Evaluation System:
    • Deployed on the application server.
    • Handles patient symptom evaluations and communicates with the database adapter.
  • Prescription Command System:
    • Processes prescription commands and sends prescription data to the database adapter.
  • Notification System:
    • Manages notifications and stores related data in the database.
  • Database Adapter System:
    • Acts as a bridge between application-layer components and the AWS database.
  • User Role System:
    • Centralized management of user roles and permissions for all users (Patients, ED, Clinic, Nurse, Chemist, Admin).

User Devices

  • Patient Device:
    • Used by patients to interact with the system for virtual triage and care selection.
  • Healthcare Staff Device:
    • Used by staff (e.g., nurses, chemists) for triage, patient updates, and prescription handling.
  • Admin Console:
    • Used by admins for managing users, system configuration, and monitoring.

Element Catalog

Element Name Description
AWS Cloud Cloud infrastructure hosting the database and application servers.
AWS Database Central database hosted on AWS for secure and scalable data storage.
Symptom Evaluation System Component for evaluating symptoms and storing results in the database.
Prescription Command System Handles prescription submissions and stores data securely.
Notification System Manages patient notifications and observer updates.
Database Adapter System Connects application components to the database, ensuring secure data flow.
User Role System Centralized system for managing user roles and interactions.
Patient Device Devices used by patients for interacting with the virtual triage platform.
Healthcare Staff Device Devices used by staff for managing triage, patient flow, and prescriptions.
Admin Console Device used by admins for system configuration and monitoring.

Variability Guide

  • Cloud Infrastructure:
    • The AWS cloud can be replaced with other platforms (e.g., Azure, Google Cloud) with minimal changes due to the Database Adapter System.
  • User Device Types:
    • The system supports various device types (e.g., mobile, desktop, tablet) for flexibility.
  • Database Variability:
    • The Database Adapter System supports integration with multiple databases if needed.

Other Information

  1. Design Decisions:
    • AWS Cloud was chosen for its scalability and reliability.
    • Centralized User Role System ensures streamlined access control across user types.
  2. Analysis Results:
    • Cloud-based architecture ensures high availability and resilience.
    • Modular design supports easy adaptation to new devices and infrastructure.