Architecture Model 1
This is the architecture model for the Artist viewpoint. The artist can have two roles: it can act as an artist and as a customer as well.
The explanation for the model is just below the image
The frontend is divided into two components: Android and Web. They both have the same functional components as shown in the architecture model. The frontend displays the actions that can be done by the user. The user interacts with the frontend to use the Art Gallery Management system.
Login/sign up: The user can access the art gallery management system by signing up or logging in to the app. If the user is new, the user needs to sign up for a new account and selects his role in the system which is either admin or member. The member can be an artist or a customer. Then the user follows certain steps which includes information like username, password, email address, Full name. If it is an existing user, the user needs to log in to access the system.
Home page: The artist can access the Home page once logged in. The home page displays some important features of our system which includes profile page, all art page, featured art page, Messages.
Profile: The artist can access this page to create a profile and add more information. The profile also displays the list of artworks purchased, published and already sold. The artist can use this page to add a new art Listing to the system. This page displays the list of artworks favorited by the artist as an artist can also be a customer and purchase art. The artist can favorite listings from featured Art or All art pages.
All Art page: The artist can access the list of artworks in the system by clicking the All-art button from the home page. The featured art page only displays the artwork posted on the system by the Manager. The All-art page includes artworks posted by induvial artists as well as artworks from the gallery itself.
Purchase page: This page displays every information required to purchase an artwork from the system.
Messages: The artist gets a notification every time a personal artwork is sold.
The backend highlights the key services implemented for the art gallery management system. The frontend interacts with the backend through REST API method calls every time any user(customer) uses the system. The backend Service component interacts with the persistence component to get information from the database using the CRUD operations in the backend.
