The
MateMate
Architecture
Introduction and goals
Design a chess system. A user can interact and the system responds according to the moves.
Nonfunctional requirements:
- Good Performance (Production of a move shall take less than 20 seconds for 95% of the cases.)
- Reliability (The probability that the component fails shall not exceed .001% per year.)
Constraints
Cross-Plattform Webapp
Browser: Chrome, Firefox, Edge
Backend: Java
Frontend: ReactJs
Documentation in English
User Interface is a GUI
No persistent datastorage
Context
Solutions Ideas and Strategy
- Solution works over a Core Logic that has GUI Drawer Logic and a Move Logic as main modules.
- It can only communicate over those 2 modules. The 2 modules can communicate with the more specific modules.
Building Block View
Runtime View
Deployment View
System will run on 2 redudant AWS instances.
Concepts
Design Decisions
Quality Scenarios
- A Tester has the possibilty to load a game over an XML.
- The XML for loading a game is understandable for a normal programmer in about 15 minutes.
- It is possible to extract the complete log from the event handler.
Risks
AWS instance not reachable
Arc42 Proposal:
-
Metamodel
- Traceability
Glossary
- AWS - Amazon Web Services
Thank you!
Management Bewertung
- Erfüllt es die Funktionalität
- Zuverlässigkeit
- Usability
- Effizienz
- Wartbarkeit
- Portabilität
- Kosten
- Zeitaufwand
- Punkte von 0 - 10
- Gesamtpunkte max. 80
The best MateMate Architecture
By masterwendu
The best MateMate Architecture
- 21