High level Architecture Design
High level Architecture Design
Architecture Flow
For the architecture flow of this website, we will have a simplified design so the consumers can be easily navigate and selling or buying the tickets. As we are using AngularJS as the framework to create ‘single page’ website, we will have these main views: Main view, Search & Browse view, Cart View and Transaction View.
Components
Main View: The main view will have the list of couple upcoming events ( two each stadium ) displaying which is fetched using google API. The users can either choose from the list directly or can browse for more in depth events. Also, a search bar will be provided to look for specific events. Images and videos are also appear along the side to promote possible popular events.
Search View: Search view displays a list of string search as well as filters including but not limited to: dates, event’s name, stadium, time, price range, popular, etc. If the query is found by the consumers, then there will be options either add to cart or bookmark it. If the query is not found then the view will display a link going back to the Main view.
Account View: Account view allows the user to either create an account or log in into existing account. All purchasing requires users to login first. All accounts require a valid credit card in order to verify.
Browse View: Browse View is similar to Search View but will displays a list of upcoming events time based first and is divided into 10 events per pages. Also, there will be option to filter out specific date, time, price, place query. Options to either add event to cart or bookmark it or sell your own tickets.
Purchase View: Cart View displays the events added either the user is selling or buying the tickets. Information such as the price and quantity, total price and taxes is calculated and appear at the bottom of the view. From here, it will takes the user either back to main view if cancel decision or transaction pop ups to complete the request. Finally, the receipt will be produced here as well email confirmation.
HW/SW/Frameworks
HW / Software Requirements: OS – MS Windows or Linux for the Server pieces Web Server – Apache Database – Any relational DBMS for storing and retrieving data (e.g. MySQL) Client – Should work on any web browser, mainly Firefox, Chrome, and Safari (at least 2) Data – Create sample (but make it realistic) data for demo and testing purpose Map – Use Google Maps for any map related components Android or iOS – for any mobile components or clients
Software, frameworks, and tools Firebase Database: Use to store the user’s information such as transaction history, personal information, billing address, billing methods ( right now only accept credits card ) and ticket information
Angular 2: Use as a framework in creating single page website, as Angular 2 allows to work on both frontend and backend of the website.
Github: Use as a version control of each version as well as the development process.
Google/Stadiums API: Use to get the information of the current events to display on the main page as well as allow searching without having to redirect to different site.