Paisley University Accommodations Office ER Schema Design

Andrew Albert Vinay Kumar Rayai

ER Schema: Entities with primary keys and relationships with all attributes detailed. Each
binary relationship contains cardinality constraints and each relationship has indicated total or
partial participation. Another ER schema on the next page

ER Schema: Detailing all entities and their complete list of attributes.

Relational Database Diagram: Diagram details the different entities and relationships involved
once the ER diagram has been translated to a relational diagram. Foreign keys are indicated by
an arrow pointing from the foreign key to the entity that foreign key refers to.

Assumptions and Design Decisions:

Entities and Attributes:

Assumed that there was a Faculty entity for the possible advisors for a Department
where each faculty member has a unique FiD.

Designed the address compound attribute for Residence Hall, Student, and Staff to be
their own individual compound attributes with all similarly named attributes. This reduced
the need to create an Address entity and the corresponding relationships to these three
entities to include an address.

Assumed that for a suite each Room would have the same door number so Door_num
could be chosen to be an attribute of Room rather than the suite relationship. This helps
deal with the fact that single rooms and suites are the only parts of the database needed
to have door numbers.

Relationships:

Every faculty member can only be an advisor for at most one department and each
department must have exactly one advisor.

Students do not have to have a lease.

Each suite of rooms has a unique suite number associated with that relationship.

Assumed every room must be part of a residence hall and every residence hall must
have at least one room and may contain many rooms.

Assumed every residence hall must have exactly one manager who does not
necessarily have an office in that hall.

Every residence hall may have multiple or no staff with an office but each staff member
has only one location in one residence hall where they can have an office. Offices may
also be shared with staff and are therefore not necessarily unique.

Required that the students Year in a department is stored as part of the lease when
creating a new lease. This is required in order to correctly identify not only the
department the student was in for that lease, but also the year they were when in that
department.

Miscellaneous:
None

Log of hours put into the project for all group members over the course of individual and team
contributions.
Activity Log
Date
Time Start

Time Stop

Total Time

11:30 PM 0.5 hours

Name
Vinay Kumar
Rayai
Vinay Kumar
Rayai

Location
Home

Accomplished
Understanding the basic
application.
Extracted schema from the
application.
Reviewed requirements and
created list of 5 entities and their
keys.
Began work on relationships
between the entities, identified
all remaining attributes for the 5
entities.

10/3/2015

11:00 PM

10/5/2015

4:00 PM

5:00 PM 1 hour

10/6/2015

2:45 PM

3:15 PM 0.5 hours

Andrew Albert

ERC

10/7/2015

12:00 PM

12:30 PM 0.5 hours

Andrew Albert

ERC

10/7/2015

2:00 PM

4:00 PM 2 hours

Vinay Kumar
Rayai

CEAS
Lounge

Created ER diagram.

CEAS
Library

10/7/2015

9:00 PM

10:30 PM 1.5 hours

Andrew Albert

Home

Finalized relationships and

cardinalities as well as any keys
and foreign keys needed for the
relationships. Determined total
or partial participation for all
entities in these relationships.

10/13/2015

12:30 PM

2:00 PM 1.5 hours

Classroom

Creating a common group ERD

10/13/2015

12:30PM

2:00 PM 1.5 hours

Andrew Albert
Vinay Kumar
Rayai

Classroom

Creating a common group ERD

10/17/2015

3:00 PM

5:00 PM 2 hours

Andrew Albert

ERC

Finishing Schema of ERD, created

RDB model.

10/17/2015

3:00 PM

5:00 PM 2 hours

Vinay Kumar
Rayai

ERC

Finishing Schema of ERD, created

RDB model.

10/19/2015

5:30 PM

6:30 PM 1 hour

Andrew Albert

TUC

Finish putting together report,

minor fixes to ERD/RDB

Total

14 hours