... | ... | @@ -3,7 +3,7 @@ |
|
|
|
|
|
# Architecture
|
|
|
## Architectural Style
|
|
|
Two main architectural styles influences development of this app, in particular both Event-Based and Object-Oriented architectures were used. Our front end followed an Event-Based architecture, with the use of various event listeners (for clicks, changes to the database etc) to allow the user to interact with the front end components of the app to produce changes to back-end data and the app state itself. The back-end of the app followed an Object-Oriented architecture through the use of various Java classes to represent entities of our problem domain: leagues, teams, games and team members for example.
|
|
|
Two main architectural styles influences development of this app, in particular both Event-Based and Object-Oriented architectures were used. Our front end followed an Event-Based architecture, with the use of various event listeners (for clicks, changes to the database, etc) that allow the user to interact with the front end components of the app to produce changes to back-end data and the app state itself. The back-end of the app followed an Object-Oriented architecture through the use of various Java classes to represent entities of our problem domain: leagues, teams, games and team members for example.
|
|
|
|
|
|
## Deployment View
|
|
|
![ArchitectureDeploymentViewImage](uploads/88419a2db6125c678f4d19148967064f/ArchitectureDeploymentViewImage.png)
|
... | ... | |