Database Foundation Project

Project Report
Database Foundations - MIS 6320.501
Group Members:
Anup Desai
Anvitha Ananth
Medha Tiwary
Vaidik Natani

A) Company Background:
Established in 2016, EasyLivingUTD offers a unique service of apartment leasing that
caters specifically to the needs of UT Dallas graduate international students. The
University of Texas at Dallas is becoming an increasingly popular choice among
international students to pursue a graduate degree. UTD is about 15 miles from
downtown Dallas, and this means that students coming here for the first time will need
to plan their accommodation well in advance since options are limited. The goal of
EasylivingUTD is to ensure that the transition for international students from their
home country into Dallas is smooth and hassle free as this portal allows students to
compare the different apartment options available around the university area where
majority of the students typically stay.
Based on an agreement, EasyLivingUTD partners with local residential communities
such that a certain number of apartment openings will be made available on the portal.
Considering the demand for accommodation near UTD we believe that the apartment
communities have an incentive to sign up for this service, they are virtually assured of
all openings being taken. Finally, our company prices all packages at a price point that is
affordable by students.
B) Business Process:
EasylivingUTD will approach the apartments that students typically stay in, these are
normally the apartments along the UTD shuttle bus route. An agreement will be signed
with each community whereby a minimum number of apartments will be assured by
the community to EasyLivingUTD. Based on the profitability margins, interests and
availability of apartments this agreement will be up for negotiation periodically. Each
apartment assured by the community will be leased to EasyLivingUTD on a BaseRent
fee. Communities stand to gain from this deal since the risk of apartments remaining
unoccupied reduces which ensures steady cash flow for them.
The listed apartments will then be leased to students at a slightly marked up price
(known as LeasingAmount). Students will be given the option to choose their
roommates/housemates. Once a lease has commenced more students can join the
apartment by signing in the lease.
C) Problem at hand:
Since the inception of the company the details pertaining to community contracts, user
details etc were being stored in spreadsheets. Since the volume of data being handled by
EasyLivingUTD was not large enough the company did not invest in creating a database.
Now, due to the growth of the company a sound database was needed. Given the current
needs, the following tables have been created.

D) Tables for EasyLivingUTD along with their purpose:
1. User_Details - This table will have the details of the students who have signed
up with EasyLivingUTD for their services. This table will comprise of all the
students who have registered with the portal irrespective of whether they have
an existing leasing contract. UTD ID is the most unique form of identifying each
user thus it is used as a UserID.
Attribute Data Type Description
Primary Key UserID VarChar UTD ID of students is used as UserID.
UTDEmail VarChar UTD email address
LastName VarChar Last name of the user.
FirstName VarChar Given name of the user.
Contact Numeric Phone number of the user.
Gender VarChar M/F
DateOfBirth Date Date of birth of
2. Community_Details - This table will have the details of the communities with
which EasyLivingUTD has an agreement with. Depending on the contract, each
community is likely to have multiple apartment listings with EasyLivingUTD.
Primary
Key
CommunityID Numeric Unique numeric ID allocated to each
community.
CommunityName VarChar Name of the community.
Address VarChar Community’s address.
Zipcode Number Community’s zipcode.
Contact Number Community’s phone number.
City VarChar Community’s city.
State VarChar Community’s state.
PointOfContact VarChar Point of contact at each community.
3. Apartment_Details - This table will list the details of the apartments that are
assured to EasyLivingUTD by the various communities. Including a Status
attribute in this table has enabled us to differentiate between the rented,
available and unavailable apartments. Due to reasons such as renovation, pest
control etc some apartments may not be available at a given point of time. This
table will be updated on a fairly regular basis given the nature of the attributes in
this table.

CommunityID is a foreign key in this table since it links each apartment with its
respective community address and point of contact.
Primary
Key
ApartmentID Numeric Unique numeric ID allocated to each
apartment registered with
EasyLivingUTD.
ApartmentType VarChar Floor plan of the apartments.
Example: 1x1, 2x2
ApartmentNumber VarChar Apartment number
BaseRent Numeric Base rent is the amount
EasyLivingUTD will pay to the
community.
Status VarChar Available(A), Rented(R), Not
available(N)
CarpetArea VarChar Floor area of the apartment
Foreign
Key
CommunityID Numeric Unique numeric ID allocated to each
community
4. Community_Agreement - This table is maintained to keep track of all
agreements signed with each community till date. This table keeps track of
historic as well as current data related to the community agreement.
Each employee from Sales division is responsible for the agreements he/she
seals with the communities thus EmployeeID is a foreign key in this table.
Primary
Key
CommunityID Numeric Unique numeric ID
allocated to each
community
MinApartmentAllocated Numeric Minimum number
of apartments
agreed upon by the
community to be
published on the
portal
AgreementFee Numeric Total amount
Easyliving pays to
the community for
renting the
apartment
StartDate Date Start of lease date
EndDate Date End of lease date
Foreign
Key
EmployeeID Numeric Unique ID allocated
to each employee

5. Leasing_Contract – This table contains details of the leasing contract signed
between students and EasyLivingUTD. Every lease is given a unique LeaseID
along with the UserID which is a primary foreign key in this table.
Primary
Key
LeaseID Numeric Unique ID allocated for each
lease signed for every apartment
with EasyLiving
Foreign
Key
UserID VarChar UTD ID of students is used as
UserID. This is the primary POC
for the apartment
UserID1 Varchar The second tenant of the apartment
LeaseStartDate Date Lease start date
LeaseEndDate Date Lease end date
LeaseSignDate Date Date on which lease is signed by
the first tenant.
ApplicationFee Numeric Amount charged by EasyLiving
for the application.
LeasingAmount Numeric Monthly amount charged by
EasyLiving for renting the
apartment
Foreign
Key
ApartmentID Numeric Unique numeric ID allocated to
each apartment registered with
EasyLivingUTD
6. Employee_Details - This table contains details of employees working in
EasyLivingUTD. EmployeeID is the primary key of this table. The table contains
details of both existing as well as terminated employees.
Primary
Key
EmployeeID Numeric Unique ID allocated to each
employee
LastName VarChar Last Name of Employee
FirstName VarChar First Name of employee
EmailAddress VarChar Email address of the employee
Department VarChar Department the employee
belongs to
StartDate Date Start date of the employment
with EasyLivingUTD
EndDate Date Termination date of the
employment
Contact Numeric Contact address of the employee
Address VarChar Residential address of the
employee
City VarChar Employee’s city
State VarChar Employee’s state
Zipcode Numeric Zipcode

7. Employee_Salary – This table contains the annual base salary and commissions
earned by the respective employees. Both Year and EmployeeID are primary keys of
this table since the salaries and commissions are maintained on a yearly basis for each
employee.
Primary
Foreign Key
EmployeeID Numeric Unique ID allocated to each
employee
Primary
Key
Year Numeric Financial year in which salary
was given.
BaseSalary Numeric Annual base salary
Commission Numeric Commission earned for the
number of agreements made
with the community
8. Renters_Insurance – Under agreement with EasyLivingUTD, students will be
required to procure a renter’s insurance. This table contains details such as name of
insurance provider, claim amount.
Primary
Foreign
Key
LeaseID Numeric Unique ID allocated for each
lease signed for every
apartment with EasyLiving
Primary
Foreign
Key
UserID VarChar UTD ID of students is used as
UserID
InsuranceProvider VarChar Name of insurance providing
organization
ClaimAmount Numeric The amount insured for

E) Entity Relationship Diagram

F) Relational Database Schema
User Details:
1. USER_DETAILS TABLE
CREATE TABLE USER_DETAILS(
User ID varchar(50),
UTDEmail varchar(180),
LastName varchar(100),
FirstName varchar(100),
Contact numeric(20),
Gender varchar(5),
DOB datetime,
CONTRAINT UserPK PRIMARY KEY (UserID);
2. COMMUNITY_DETAILS
CREATE TABLE COMMUNITY_DETAILS (
CommunityID numeric(20),
CommunityName varchar(80),
Address varchar(200),
Zipcode numeric(10),
City varchar(30),
State varchar(30),
PointOfContact varchar(100)
CONSTRAINT CommunityIDPK PRIMARY KEY (CommunityID);
3. COMMUNITY_AGREEMENT TABLE
CREATE TABLE COMMUNITY AGREEMENT(
MinApartmentAllocated numeric(10),
AgreementFee numeric(10),
StartDate date,
EndDate date,
EmployeeID numeric(20),
CONSTRAINT PKCommunityID PRIMARY KEY (CommunityID),
CONSTRAINT EmployeeIDFK FOREIGN KEY (EmployeeID) REFERENCES
EMPLOYEE_DETAILS(EmployeeID),
CONSTRAINT CommunityId FK FOREIGN KEY (CommunityID) REFERENCES
COMMUNITY_DETAILS(CommunityID);
4. EMPLOYEE_DETAILS
CREATE TABLE EMPLOYEE_DETAILS (
LastName varchar(100),
FirstName varchar(100),
EmailAddress varchar(180),
Department varchar(100),
StartDate date,
EndDate date,
Address varchar(200),

City varchar (200),
State varchar(100),
Zipcode numeric(10)
CONSTRAINT EmployeeIDPK PRIMARY KEY (EmployeeID);
5. EMPLOYEE_SALARY
CREATE TABLE EMPLOYEE_SALARY(
Year numeric(4),
BaseSalary numeric(20),
Commission numeric(20),
CONSTRAINT EmployeeIDFK FOREIGN KEY (EmployeeID) references
EMPLOYEE_DETAILS(EmployeeID),
CONSTRAINT EmpSalPK PRIMARY KEY (Year, EmplpyeeID);
6. APARTMENT_DETAILS TABLE
CREATE TABLE APARTMENT_DETAILS(
ApartmentID numeric(20),
ApartmentType varchar(10),
ApartmentNumber varchar(10),
BaseRent numeric(10,2),
Status varchar(10),
CarpetArea numeric(10),
CONSTRAINT ApartmentIDPK PRIMARY KEY (ApartmentID),
CONSTRAINT CommunityIDFK FOREIGN KEY (CommunityID) references
COMMUNITY_ID(CommunityID);
7. LEASING_CONTRACT
CREAT TABLE LEASING_CONTRACT (
LeaseID numeric(10),
UserID varchar(50),
LeaseStartDate date,
LeaseEndDate date,
ApplicationFee numeric(10),
LeasingAmount numeric(10),
ApartmentID numeric(20),
CONSTRAINT LeaseIDPK PRIMARY KEY (LeaseID),
CONSTRAINT UserIDfFK FOREIGN KEY (UserID) references USER_DETAILS(UserID),
CONSTRAINT ApartmentIDFK FOREIGN KEY (ApartmentID) references
APARTMENT_DETAILS(ApartmentID);
8. RENTERS_INSURANCE TABLE
CREATE TABLE RENTERS_INSURANCE (
LeaseID numeric(10),
UserID varchar(50),
InsuranceProvider char(20),
ClaimAmount numeric(10),
CONSTRAINT RenterInsPK PRIMARY KEY (LeaseID,UserID),
CONSTRAINT LeaseIDFK FOREIGN KEY (LeaseID) references LEASING_CONTRACT(LeaseID),
CONSTRAINT UserIDFK FOREIGN KEY (UserID) references USER_DETAILS(UserID);

G) MENU and DATA INPUT SCREENS
Over the course of the business new data will need to be added to the database.
To add new data several forms have been created whereby the Business
Development or Customer Support team can view, input, edit or delete data.
Start Up Screen:
For the ease of the user, the Menu screen lists the forms which can be accessed
to perform any of the above-mentioned activity as well as to view relevant
reports.

User Details Form:
This form can be used to view and update details of existing student users as
well as to add new users in the database.

Community Details form:
Community Details form will allow users to view the details of the communities
that are currently in business with EasyLivingUTD. Details of expired contracts
can also be found from this form.
Using the ‘Add New Community’ tab, the employees can add new communities
to the database.

Apartment Details form:
Apartment Details form allows user to view the layout and status of the
apartments listed with EasyLivingUTD portal. Using the ‘Add New
Apartment’, this form also allows to add new apartments from the existing or
newly added communities.

H) REPORT:
a. Number of unleased apartments:
From time to time, the company needs to keep a check on the number of
available unoccupied apartments which can be viewed using this report.
Related query:
SELECT COMMUNITY_DETAILS.CommunityName,
COMMUNITY_DETAILS.PointOfContact,
Count(APARTMENT_DETAILS.ApartmentID) AS
NumberOfUnleasedApartments
FROM COMMUNITY_DETAILS INNER JOIN APARTMENT_DETAILS
ON COMMUNITY_DETAILS.CommunityID =
APARTMENT_DETAILS.CommunityID
WHERE (((APARTMENT_DETAILS.Status)='A'))
GROUP BY COMMUNITY_DETAILS.CommunityName,
COMMUNITY_DETAILS.PointOfContact;

b. Employee commission:
Employees in the sales division receive commission for each deal they strike
with the communities. These commissions are paid on a yearly basis after the
deal has been followed through entirely.
Related query:
SELECT EMPLOYEE_DETAILS.FirstName,
EMPLOYEE_SALARY.EmployeeID, EMPLOYEE_DETAILS.LastName,
EMPLOYEE_SALARY.Year, EMPLOYEE_SALARY.Commission AS
TotalCommission, Count(COMMUNITY_AGREEMENT.EmployeeID) AS
NumberOfContractsLanded,
(EMPLOYEE_SALARY.Commission/EMPLOYEE_SALARY.BaseSalary)*10
0 AS PercentCommisionOverSalary
FROM (EMPLOYEE_DETAILS INNER JOIN
COMMUNITY_AGREEMENT ON EMPLOYEE_DETAILS.EmployeeID =
COMMUNITY_AGREEMENT.EmployeeID) INNER JOIN
EMPLOYEE_SALARY ON EMPLOYEE_DETAILS.EmployeeID =
EMPLOYEE_SALARY.EmployeeID
WHERE ((EMPLOYEE_DETAILS.Department)='Sales')
AND EMPLOYEE_SALARY.Commission > 0
AND
((EMPLOYEE_SALARY.Commission/EMPLOYEE_SALARY.BaseSalary)*1
00) >0
GROUP BY EMPLOYEE_SALARY.Year,
EMPLOYEE_SALARY.EmployeeID, EMPLOYEE_SALARY.Commission,
EMPLOYEE_DETAILS.FirstName, EMPLOYEE_DETAILS.LastName,
(EMPLOYEE_SALARY.Commission/EMPLOYEE_SALARY.BaseSalary)*10
0;

c. Profit on apartments leased out:
This report shows the profit earned on each apartment leased. The profit is
calculated as a difference between the leasing amount and base rent.
Related query:
SELECT CommunityName,
COUNT(APARTMENT_DETAILS.CommunityID) AS ApartmentsLeasedOut,
SUM(BaseRent) AS LeaseOnAptAsPerContract, SUM(LeasingAmount) AS
LeaseEarnedOnAptLeased, SUM(LeasingAmount)-SUM(BaseRent) AS
ProfitMadeOnAptLeasedOut
FROM APARTMENT_DETAILS, LEASING_CONTRACT,
COMMUNITY_DETAILS
WHERE
APARTMENT_DETAILS.ApartmentID=LEASING_CONTRACT.ApartmentI
D AND
APARTMENT_DETAILS.CommunityID=COMMUNITY_DETAILS.Commu
nityID
GROUP BY CommunityName
ORDER BY SUM(LeasingAmount)-SUM(BaseRent) DESC;

I) Individual Contributions:
A great deal of team effort has gone into making this project but in all fairness
some members worked in depth on certain aspects of it. The specifics were
taken care of by the following members:
ER diagram using ERWIN: Anup, Vaidik
Access Forms: Anvitha, Vaidik
Access Report: Medha, Vaidik
Queries: Anup, Anvitha
Data generation: Medha, Anvitha
Final Report: Medha, Anup

Database Foundation Project

Recommended

Recommended

More Related Content

Similar to Database Foundation Project

Similar to Database Foundation Project (20)

Recently uploaded

Recently uploaded (20)

Database Foundation Project