Architecture

The business logic of the system will revolve around the account type used in the login phase. Each system component will behave differently depending on the type of account logged in. The components include the following: login, map, tile, notification, settings, and chat. The user interface views will be coded differently using mono and mono for android. However, each component will reference a view model which will contain the properties that will bind to different control elements of the view. The properties of the view models will perform business logic that will be common to both views coded in mono and mono for android.

The different account types will be the VendorAccount, the BuyerAccount and the PublicAccess. Vendor accounts contain a the PromotionPin and the Tile objects.

The map, follow notification and tile components will use a VendorDataRetriever to access the vendor's account information from the database.

Moreover, the camera, settings, and chat components will not use the database to retrieve data. The camera will be able to access the photo library of the user's phone. The settings will store the user's settings locally on their phone and finally the chat will simply manipulate data loaded on the app.

The layer diagram of our application is represented below and separates Glimpse into 3 tiers: user interface, domain logic, and data tier. The user will interact with the application through the presentation layer. Information related to the Account will be stored and retrieved through the database. The logic tier coordinates the application and is composed of 7 main concepts: the map, the chat feature, the tile display, the camera, notifications, and the login process. Moreover it processes information between the data layer and the presentation layer.