23 Feb The main function of the server is to serve user requests from the front-end client. Data is exchanged between the client and server through HTTP requests. To accept requests at the back end
computer science question and need an explanation and answer to help me learn.
since you have database design, you need to design the user interface for each data item in the database ,you also need to define the relationship between the viewers
please continue work on the database design I created
Requirements: details
Database Design
Bucket List
Haein Yu, Karen J Kraft, Dennis Liang, Benjamin Charles Scuron, Curtis LAM, Jianlin Deng, Lauren Kan, John A Karas, Ashley Kolb Malaviya
REVISION HISTORY
Database Design
Abstract: This document describes and presents the database tables. There are three tables that store user data, profile page data, and event data. The user table stores login and unique identifier information to manage the userbase. The profile table will have an associated user_id foreign key, in order to have a 1 to 1 relationship between a user and a users profile. The profile table will store more public data while the user table will store sensitive data. The third table is the event table. Events require location information for the react native map. The event table will also store user filled information such as descriptions, names, event categories, and more.
Design Document – Par I Architecture
Haein Yu, Karen J Kraft, Dennis Liang, Benjamin Charles Scuron, Curtis LAM, Jianlin Deng, Lauren Kan, John A Karas, Ashley Kolb Malaviya?
REVISION HISTORY
?
Description of Components
Client
The client side will be the starter of most of the features. This user input is taken either on the users phone or through the website. The user will need to click on the login page and click on the text boxes for their account information. This input applies to the Bucket List events as well since the user will click on ?new event and the event details will also use text boxes. Some of the details, such as the date, time, or location, may be put onto a calendar. The users actions on the web application will have the HTTP GET or POST request using Axios, which transforms the requests to have the server send back that transformed response. The full process is the HTTP request will get transformed, which then is sent to the browser and Node.js as an XML HTTP request and Node.js HTTP request respectively. Both requests are combined to be the transformed response sent to the client from the server. This should work similarly for the mobile version as well.
Server
The main function of the server is to serve user requests from the front-end client. Data is exchanged between the client and server through HTTP requests. To accept requests at the back end, Express.js is being used for routing. Routing refers to how an applications endpoints (URIs) respond to client requests. When a client makes a request to a back-end route, data is returned to the user in JavaScript Object Notation (JSON). The server also interacts with the MySQL database using the Node MySQL client driver. SQL queries can be made to the MySQL database that alter the contents and structure of the database using information received from the client side. In addition to routing and database interaction, the server is responsible for managing user sessions. Sessions will be used to authorize users. Unauthorized users will be prevented from accessing data not pertaining to them, this will ensure application security.
Database
The database will be used to store all persistent data. Data stored in the database includes user credentials (usernames, passwords, emails, etc.), event details (location, time, place, etc.), event images (stored in binary format), and more. The database is essential in creating an experience for the user that will be consistent between sessions. The database will be organized in a relational format, linking tables together using primary keys. As of right now, the three main tables will be: the ‘User’ table, the ‘Profile’ table, and the ‘Event’ table. Each table will store information pertaining to their focus. For example, the ‘User’ table will store user credentials. The focus of the database is to provide a structured way to store our application data. The database itself should be easily understood and easy to work with. The back end is responsible for interacting with the database. The Node MySQL client driver will be used in the back end to make SQL queries. The database will return the requested data from the back-end queries.
System Components
Direction:
Describes the components (i.e. client, server, and database) and their interface.
For each component, provide class diagrams to show the classes to be developed and their relationship.
Client
Server
Database
Purpose
The following document, Design Document Part I Architecture,? describes the software architecture of the Bucket List + Whats the Move and how its requirements have been mapped into the design. The document will consist of diagrams and descriptive text that explains the content of the diagrams.
The document covers the following topics:
Components and Interfaces
Class Diagrams
Sequence Diagrams
State/UML Diagrams
Database Diagrams
System Block diagram
Database
Entity-Relation Diagram
Figure 1. Entity-Relation Diagram
Table Design
Considering the application features, three tables are necessary to hold users account information, detail user profiles and event data.
Each user requires to create an account to gain access of all application features. User table holds registration information, which requires to login into application system. Those information are username, registered email address, account password, a unique user id and account creation data and time.
Users: to store user login information such as user id, login id and password etc.
UserID primary key, autoinc
Username – String
Password encrypted hex?
User_Profile Foreign Key?
Users_Profile: to store user personal information such as first name, last name, and data of birth etc.
First_name String
Last_name String
DoB Formatted String
UserID Link
User_Bucket_List Foreign Key
User_Bucket_List: to store all user data related to bucket list such as data, location, and detail etc.
Events?
User_Events: to store the events created by the user with additional information such as who is joining and number of people participate event etc.
Events: to store events information in different city by week?
Name String
Desc String
Lat/Long – Formatted Decimal or String
Img blob
*How do we handle friends? Would we have a Users_Friend table?
*for events in react native map, we need to create s where they need a name, desc, lat/long and icon I believe. So we probably need to pull that info from the event Table
Class Diagram
Sequence Diagrams
Sequence Diagram for use cases
Use Case #1:
Kelly, a new user, is seeking an application that enables her to establish her bucket list.
Kelly downloads the application.
Kelly opens the app and creates an account
Kelly creates a profile from the Home Page. She uploads a profile image, her name, zip code, birthday, email.
Kelly selects several key words from a drop-down list of Bucket List? items in the Home Page.
Sequence Diagram:
Use Case #2:
Megan shared her experience
Megan went to the museum with her friends and she wants to share her photos and experience. Megan opens the app and navigates to her profile. She clicks on add memory?.
The app then prompts her to choose photos from her camera roll to upload. She then clicks next? which directs her to add a caption to her set of photos. Here, she also chooses tags that go along with her activity; such as: Museum. She can also add the location of her activity.
She then clicks post? which uploads the post for others to see.
Sequence Diagram
Use Case #3:
Holly is a student looking for events around her through app.
1. Holly downloads the application.
2. Holly uses app to click the Map? to connect instance server which she can search for events near her by entering her location into the search bar.
3. The map? returns the locations where surrounding her, and once she finds an event she is interested in, she can view more details about it, including the time, location, and cost.
4. She can also read reviews from other users who have attended the event.
5.She can add the event to the bucket list” once she decides what events she will attend.
Sequence Diagram
Use Case #4:
Cixin is creating a profile.
Cixin logs in the application.
He then, from the main page, clicks the create a profile button from the drop-down menu.
He fills out the necessary information to create a profile (name, email, password, DOB)
He then picks items from the ?Bucket List drop down menu, to indicate his interests.
He then adds a profile picture from his phones library.
He lastly clicks the Create Profile? button at the bottom of the form and waits for an email to be sent confirming his profiles email address.
Sequence Diagram
Use Case #5:
Cixin is creating an Event.
Cixin is signed in and on the home page.
He is interested in creating a new event for him and his friends to attend.
He clicks the + button at the bottom left corner which when hovered over, says Create an Event??
When he clicks on it a new screen appears.
Cixin is then prompted to give the event a name, which he labels Rock climbing at Tufas Bolder Lounge?.
The event requires the user to input the address, date and time of Event.
It is also required to tag this event with a specific item from the same list of Bucket List? items. He chooses the tag #RockClimbing.
He then clicks the Create Event? button at the bottom of the form.
A new page thanking Cixin for creating an event appears.
When he goes back to his profile page, the event appears in his Upcoming Events? section.
Next to it is a + button which others can use to indicate they will be attending the Event.
Sequence Diagram
Use Case #6:
Lea intends to attend an event organized by her friend.
Lea accesses her account.
She clicks the Friend List? and goes through her friends accounts.
She notices Cixins event Rock climbing at Tufas Bolder Lounge? listed under his Upcoming Events? section.
She clicks the +? button, and her name added to the list of attendees for the event.
The event is also reflected under Leas Upcoming Events? section in her account.
Sequence Diagram
