Professional Documents
Culture Documents
AN20201204-1676 Final
AN20201204-1676 Final
Student’s Name
Professor’s Name
Course Number
Date
Given the nature of this automation, we decided to break our information into 5 entities:
Member, Transaction, Cars, Accounts, and Buildings. The member entity has the related
information to the user, such as the identification of the user, its first and last names, and the
contact information (phone number and email). It is also possible to find useful data like the
member address. The Member entity is connected to the Cars and Account tables, which identify
the user as a student and verifies the car connected to his/her account. It is important to highlight
that one user may have more than one car associated with his/her account. However, a student
The entity Cars stores information regarding the registered vehicles, identified by their
identification (VIN). Other information to identify the vehicles are also registered: the color,
year, make, model, and license plate are stored as a form to be sure that the car inside the
The Account table, related to each user, is a mandatory relationship that provides the
database with essential information to identify the billing information related to each user. It
contains the email as the primary key, identifying the user, the membership status, the monthly
fee associated with each type of account, and the order history. This table is associated with the
Transaction is an entity that stores and controls the orders related to each account. It
contains the historical information of the transactions performed in every account, providing
information such as the order identification, the identification of the user, the start and stop time
of each order, the order status, as well as the space number occupied by the car associated to the
member.
The last entity, Buildings, stores information about the buildings that belong to this
company. Each building is identified by an ID number, its location, the total capacity, and