This document provides a comprehensive architectural overview of the system, using a number of different architectural views to depict different aspects of the system. It is intended to capture and convey the significant architectural decisions which have been made on the system.
This document is closely related to the Software Requirement Specifications and the defined Use Cases. You can find both in the GitHub repository of this Project.
- MVC = Model View Controller
- JSON = JavaScript Object Notation
- N.a = Not applicable
- Github Repository: https://github.com/turniere
- Blog: https://blog.turnie.re
This Document contains information about our software architecture. In more details, you can find information about Architectural Representation, Architectural Goals and Constraints, Use-Case View, Logical View, Process View, Deployment View, Implementation View, Data View, Size and Performance and Quality.
This section describes what software architecture is for the current system. Our Project consists of two Applications. We have an Ruby on Rails backend and an React frontend. These have different architectures. React is in our project anyways only used as a view, while Rails provides the Information as JSON. Ruby on Rails is 'classic' MVC architecture.
The MVC architecture has a very simple functionality. You have a View which gets User actions and passes them to the Controller. The Controller sends data to the Model or updates the View with the data received from the Model. The Model is the logic of the application.
N.a
N.a
N.a
N.a
N.a
N.a
We are using a Postgres database. Here you can see our database scheme.
N.a
N.a