-
Notifications
You must be signed in to change notification settings - Fork 0
04 Architecture
We plan to build the application using [Architecture] style.
Tip
We recommend building architecture using Draw.io. Draw.io also has a desktop application.
Tip
You can also document your architecture using C4Model. We recommend C1(System Context) and C2(Container) diagrams.
C4 model is a lean graphical notation technique for modelling the architecture of software systems. It is based on a structural decomposition of a system into containers and components and relies on existing modelling techniques such as the Unified Modelling Language (UML) or Entity Relation Diagrams (ERD) for the more detailed decomposition of the architectural building blocks.
Tip
Use this tool to create ADR logs (Generate an architectural decision log out of architectural decision records (ADRs)).
The list of technologies we will use to build the application are as follows:
| Technology | Purpose | Version |
|---|---|---|
| [Language] | [Programming Language] | [version] |
| [Database] | [Database] | [version] |
| [Frontend Framework] | [Framework?yes:no] | [version] |
| [Backend Framework] | [Framework] | [version] |
Non-functional requirement for the project are:
| Quality Attribute | Description | Target (examples) |
|---|---|---|
| [Performance] | [Transaction Response Time] | [2 seconds] |
| [Availability] | [System Uptime] | [99.9] |
| [Throughput] | [Number of requests/transactions per second at peak time] | [1000 RPS] |
| [Auditability] | [Ability of the application to show what has happened to it, who did it and when] | [A log file that captures the event with the timestamp] |
| [Reliability] | [Mean time to recovery] | [System should be able to recover from failure under 5 mins] |
| [Usability] | [Usability can be described as the capacity of a system to provide a condition for its users to perform the tasks safely, effectively, and efficiently while enjoying the experience] | [Browsers: Chrome, IE, Firefox] [Screen Size] |