Embedded Files
Architecture
Architecture
The architecture for this project is split into a domain layer, a data layer and a presentation layer. The presentation layer will be using an MVP structure as well.
As detailed in the technologies page the tasks of the domain, presentation and data layers is as follows:
- Data layer
- Manage any data from API's, databases and shared preferences.
- Domain
- Serve as interface between data and presentation layer
- Hold relevant models for domain and presentation layer
- Presentation
- Takes care of all the view logic
- Takes care of all communication with other modules
The software will connect to the Brickx API using hibernate and RetroFit.
Class diagram
Class diagram
Because this project uses the MVP architecture, working out the whole class diagram with every call would mean a lot of similar classes and a ton of repeating the same thing over and over again. It would also be a giant mess and unreadable.
Instead I decided to only detail the pipeline for logging in as a user. It does cover every module and the API so it should give a good idea about how the app is structured.
Page updated
Google Sites
Report abuse