CS 5744 - Project 1 - Pet Adoption and Medical Record System

CS 5744 - Project 1 - Pet Adoption and Medical Record System

    ›High-Level Design

    Introduction

    • Introduction

    Requirements Summary

    • Use Cases
    • Stakeholder Analysis
    • Requirements

    High-Level Design

    • System Architecture
    • File Storage Design
    • Database Design
    • REST API Design
    • Web Application Design
    • Requirement Traceability Matrix

    Design Rationale

    • System Architecture Rationale
    • Data Tier Rationale
    • REST API Design Rationale
    • Web Application Design Rationale
    • Final Thoughts

    Requirement Traceability Matrix

    Within the previous design sections we have included references to a number of functional and non-functional requirements where appropriate. Some of the requirements are overarching and difficult to pin to a single component of the system. The following requirements traceability matrices should provide a quick reference for the relationship between the requirements and the system components.

    Functional Requriements

    3-Tier Architecture
    Database Component
    File Storage Component
    REST API Component
    Web Application Component
    Additional AWS Services
    FR-1 X X X
    FR-2 X X X
    FR-3 X X X
    FR-4 X X X
    FR-5 X X X
    FR-6 X X X X
    FR-7 X X X X
    FR-8 X X X
    FR-9 X X X
    FR-10 X X X
    FR-11 X X X X

    Non-functional Requriements

    3-Tier Architecture
    Database Component
    File Storage Component
    REST API Component
    Web Application Component
    Additional AWS Services
    NR-1 X
    NR-2 X X X X X X
    NR-3 X X X X X
    NR-4 X X X X
    NR-5 X X X
    NR-6 X X X
    NR-7 X X X
    NR-8 X X X
    NR-9 X X X
    NR-10 X
    NR-11 X X X
    ← Web Application DesignSystem Architecture Rationale →
    • Functional Requriements
    • Non-functional Requriements
    Built with Docusaurus
    Copyright © 2019