Course Project: Shared Workspace

Coworking is a work style where different individuals or teams share a

working environment. If you are a self$-$employed or a working$-$from$-$home

professional, you would love to have the option to rent a meeting room, or a

desk in an office equipped with high$-$speed internet, printers, copiers,

stationaries, and office kitchen. As there is an increase in the number of

coworkers and the number of sharable workspaces, we are looking to

develop an application to connect both parties. The objective is very similar

to how Uber connects riders with drivers and Airbnb connects tenants with

landlords.

You will work on this project in individually to develop a database system.

For this project, you must use the software we use in class. You will receive

half mark during phase one and half mark for your final submission. Grades

for your project throughout the term using the following milestones.

$1.$ Phase $1$: $-$ Submit well designed and detailed ERD diagram for this

project

$-$ Read the case study and the given sample user stories and drive all

the appropriate Entities and the corresponding attributes.

$-$ Do your analysis and explicitly indicate all the relationship and the

cardinality or cordiality that exist between the entities on your ERD

diagram

$-$ Check each of the entities for normalization to avoid anomalies. If you

found out any anomalies make sure you normalize it to eliminate the

anomalies.

$-$ Prepare a sample table for each entity and association entity and enter

a record of $25$ row of data.

$2.$ Phase $2$: Implement the ERD diagram and populate it with sample

data and prepare a query statement to fetch information with variety

of makeup user stories. If you need sample user stories you can speak

with your teacher

$-$ Clear DDL to create the a database FirstName$\_$sharedworkspace

$-$ Clear DML to populate sample data

$-$ Clear Query to manipulate data from the database based on the user

stories.

$-$ Clear descriptive comment for each of your SQL code

Final Minimum Viable Product $($MVP$)$

DATA$1201$ Database Design project

The MVP is the smallest conceivable list of features that fulfill the primary

business goal of the database product. One way to summarize a feature is a

user story$--$ a short sentence describing the feature from the perspective of

the user. User stories frequently take the form: $$As a $,$ I can

so I can $.$ You can start with the

following user stories as a backlog for your MVP$.$

$1.$ As a user, I can sign up for an account and provide my information

$($name$,$ phone, and email$).$ I can give my role as an owner or a

coworker as option.

$2.$ As an owner, I can list a property with its address, neighborhood,

square feet, whether it has a parking garage, and whether it is

reachable by public transportation.

$3.$ As an owner, I can select one of my properties and list workspaces for

rent. Workspaces could be meeting rooms, private office rooms, or

desks in an open work area. For each workspace, I can specify how

many individuals it can seat, whether smoking is allowed or not,

availability date, lease term $($day$,$ week, or month$),$ and price.

$4.$ As an owner, I can modify the data for any of my properties or any of

my workspaces.

$5.$ As an owner, I can delist or remove any of my properties or any of my

workspaces from the database.

$6.$ As a coworker, I can search for workspaces by address, neighborhood,

square feet, with$/$without parking, with$/$without public transportation,

number of individuals it can seat, with$/$without smoking, availability

date, lease term, or price.

$7.$ As a coworker, I can select a workspace and view its details.

$8.$ As a coworker, I can get the contact information of a workspace$$s

owner. $($can you please do the phase $1$ for now$)$