📄️ Domain Model
Domain Model
📄️ Requirements
Although we are no longer in the requirements engineering phase, this document may still change in the near future.
📄️ Busines Processes
In the following, the most important business processes are modelled using BPMN.
📄️ experiment-configuration
Note that this page is still viable, but the MiSArch Experiment Tool has way more functionality by now and can be used instead.
📄️ Domain Tradeoff Analysis
This document compares the three domains "Sonarcube Actions" (SA), "Shipping Container Service" (SCS) and ""Ticketing System" (TS) in terms of their suitability with regard to the requirements identified. The complete requirement descriptions can be found in the requirement docs file. Requirements, that are equally fullfillable by both domains are omitted from this comparison.
📄️ Component Diagram
Overview of the main components and their interactions in the Misarch architecture.
📄️ User Journeys
As things stand, "user" refers to a normal visitor of the online shop who may buy something. User journeys for the administrator and the employee of the online shop will follow in the near future.
📄️ Health endpoint
Every service exposes a health check endpoint under GET /health.