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

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

    ›Design Rationale

    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

    Final Thoughts

    There is one requirement that we have failed to address thus far, FR-11. Notifications must be sent to users without an external event initiating the process. There are many mechanisms to perform such actions. There is no reason to restrict the system developers from using the mechanism that best suits the project. We can, however, suggest that for any process that needs to be scheduled to run at a defined frequency AWS Lambdas provide the needed functionality. Each process can be coded and configured for AWS Lambdas independently. If we were to include theses processes in the three-tier architecture diagram, they would fall under the application tier.

    We have provided enough design within this document to begin development on a pet adoption and medical record system. Most of our decisions have been based on proven approaches to web application development. It is impossible to anticipate all possible problems or flaws in a design. If any unforeseen issues should arise, the separation of concerns will allow for easier changes in the design. If any changes are required, please keep in mind, all design decisions include tradeoffs.

    ← Web Application Design Rationale
    Built with Docusaurus
    Copyright © 2019