Create UML Diagram for REST API Structure

License and Copyright Notice

By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).

Pre-checklist

• I have searched for, and did not find, an existing issue at the top-level.

Stories

Story 1: As a developer, given data that will be passed, I want a template for our class structure so that these are correctly and most efficiently implemented.

Ready checklist

• Independent (of other issues in flow)
• Negotiable (and negotiated)
• Valuable (the value to an identified role has been identified)
• Estimable (the size of this story has been estimated using /weight value or the menu on the right)
• Small (can be completed in 50% or less of a single iteration)
• Testable (has testable acceptance criteria)

Also

• Appropriate role labels have been applied (e.g., role:*).
• Relevant activity labels have been applied (e.g., activity:*).
• Linked to related issues, epics, and milestones.

Diagrams

Diagram will be attached

https://drive.google.com/file/d/1-HACEbNWQ3_QI3XzU6ia-f8_jAN7jE1w/view?usp=sharing

Acceptance Criteria

Scenario: [I want to add a new class]
  Given a new class
  When I want to understand its interactions
  Then the existing class relationships are laid out completely

Version 2.0.0

<!--
This is the version of the template being used.
-->