Featured image of post Requirements Analysis Document

Requirements Analysis Document

1. Overview

This requirements analysis document aims to provide a detailed description of the functionalities and interaction flows of a medical rehabilitation system. The system consists of four main modules: User Interface Module (UI Group), System Core Module (System Group), Data Processing Module (Data Group), and Data Analysis Module (Analysis Group). These modules work together through clear interaction relationships to provide efficient and secure services for patients, doctors, and administrator doctors.


2. User Roles

2.1 Patient

  • Responsibilities: Use the system to register, log in, view real-time measurement data and feedback results, and adjust rehabilitation training plans based on doctor recommendations.
  • Permissions:
    • Access personal health data.
    • Submit personal information and measurement data.

2.2 Doctor

  • Responsibilities: Manage patient health information, view measurement data, and provide professional advice.
  • Permissions:
    • Access patient-related data.
    • Edit patient basic information.

2.3 AdminDoctor (Administrator Doctor)

  • Responsibilities: Manage doctor account information, maintain doctor data support within the system, and monitor system logs and operational status.
  • Permissions:
    • Full access to doctor and patient data.
    • Modify system configurations and manage the database.

3. Functional Module Division

3.1 UI Group (User Interface Module)

Functional Overview

The UI Group is responsible for providing the interface for user interaction with the system, including login, registration, patient management, measurement preparation, data display, and result feedback functions, ensuring a user-friendly and intuitive experience.

Detailed Use Case Expansion

  • UC_Login:

    • Description: Enables patients or doctors to log into the system using a username and password.
    • Preconditions: The user already has an account.
    • Main Flow:
      1. The user enters the username and password.
      2. The system verifies the credentials.
      3. Upon success, the user is redirected to their homepage.
    • Error Handling:
      • Incorrect username or password: Prompt “Username or password is incorrect, please re-enter.”
      • System unavailable: Prompt “The system is temporarily unavailable, please try again later.”
  • UC_Register:

    • Description: New users complete registration by filling in basic information.
    • Preconditions: None.
    • Main Flow:
      1. The user accesses the registration page.
      2. Fills in basic information such as name, contact details, and email.
      3. The system verifies the completeness and uniqueness of the information.
      4. After successful registration, the user is notified of completion.
    • Error Handling:
      • Incomplete information: Prompt “Please fill in all required fields.”
      • Email already registered: Prompt “This email is already registered, please use another email.”
  • UC_PatientManage:

    • Description: Doctors create or search for patient basic information.
    • Preconditions: The doctor is logged into the system.
    • Main Flow:
      1. The doctor selects “Create Patient” or “Search Patient.”
      2. If creating a patient, fills in the patient’s basic information and saves it.
      3. If searching for a patient, enters keywords (e.g., name or ID) and views the search results.
    • Error Handling:
      • No search results: Prompt “No related patient information found.”
  • UC_PrepareMeasure:

    • Description: Provides animated guidance to help patients correctly wear sensors and initialize the device.
    • Preconditions: The patient is logged into the system.
    • Main Flow:
      1. The patient accesses the measurement preparation page.
      2. The page plays an animation to guide the patient in correctly wearing the sensor.
      3. The system calls the “Initialize Sensor” interface to initialize the device.
      4. After initialization is complete, the patient is prompted to start the measurement.
    • Error Handling:
      • Device initialization failure: Prompt “Device initialization failed, please check the connection.”
  • UC_RealTimeDisplay:

    • Description: Displays the real-time joint angle status of the patient.
    • Preconditions: The measurement device has been initialized and started collecting data.
    • Main Flow:
      1. The system calls the “Get Streaming Data” interface to obtain real-time data.
      2. The data is processed and displayed in chart form.
      3. The patient can view their joint angle changes in real-time.
    • Error Handling:
      • Data stream interruption: Prompt “Data stream interrupted, please check the device connection.”
  • UC_ResultFeedback:

    • Description: Displays measurement results and professional advice from the doctor to the patient.
    • Preconditions: Measurement is complete, and analysis results have been generated.
    • Main Flow:
      1. The system calls the “Request Analysis” interface to request analysis results.
      2. After loading the analysis results, they are displayed on the page.
      3. The doctor provides rehabilitation suggestions based on the results.
    • Error Handling:
      • Analysis result loading failure: Prompt “Result loading failed, please try again later.”
  • UC_DoctorInfoManage:

    • Description: Administrator doctors edit and manage doctor information.
    • Preconditions: The administrator doctor is logged into the system.
    • Main Flow:
      1. The administrator doctor accesses the information management page.
      2. Selects the doctor information that needs editing.
      3. Modifies the information and saves it.
    • Error Handling:
      • Insufficient permissions: Prompt “You do not have permission to perform this operation.”

3.2 System Group (System Core Module)

Functional Overview

The System Group serves as the core part of the system, coordinating interactions between different modules, including but not limited to data storage, logging, data collection, and uploading operations, ensuring the stable operation and efficient data processing capability of the system.

Detailed Use Case Expansion

  • UC_CICD: Data support services for doctors.
  • UC_API: Secure storage of user information.
  • UC_Log: Monitoring and recording system logs.
  • UC_UItoDataCollect: Transition to data collection after measurement preparation.
  • UC_UItoDataUpload: Uploading real-time data to the server.
  • UC_UItoDBManage: Synchronizing analysis results to the database.
  • UC_UItoAnalysis: Connecting feedback pages with analysis modules.

3.3 Data Group (Data Processing Module)

Functional Overview

The Data Group focuses on data collection, cleaning, storage, and management, ensuring that the data entering the system is clean and useful.

Detailed Use Case Expansion

  • UC_DataCollect: Collecting data from sensors.
  • UC_DataUpload: Uploading collected data to the server.
  • UC_DataClean: Cleaning and interpolating raw data.
  • UC_CRUD: Basic database operations (Create, Read, Update, Delete).
  • UC_DBManage: Managing database information to ensure consistency and security.

3.4 Analysis Group (Data Analysis Module)

Functional Overview

The Analysis Group is dedicated to conducting in-depth analysis of sensor data, identifying deviations and anomalies, and generating structured feedback results.

Detailed Use Case Expansion

  • UC_ReceiveData: Receiving cleaned sensor data.
  • UC_Analysis: Performing deviation analysis and anomaly tagging.
  • UC_ResultReturn: Returning analyzed results to the feedback page.

4. System Integration and Workflow

Data Flow Description

The system revolves around the flow of data, from sensor-wearing by patients to data collection, uploading, cleaning, analysis, and finally feeding back the results to patients and doctors.

User Interaction Workflow

  • Patient Perspective: Register/login → Prepare measurements → View real-time data → Receive professional advice.
  • Doctor Perspective: Manage patients → Use data support services → Provide rehabilitation guidance.

Error Handling Mechanism

The system incorporates multiple error handling mechanisms, providing clear prompts and minimizing impact when issues arise, covering scenarios like user input errors, device malfunctions, and data transmission interruptions.

Licensed under CC BY-NC-SA 4.0
comments powered by Disqus
2777619715@qq.com
使用 Hugo 构建
主题 StackJimmy 设计