CGS2541 Project 1 Assignment

Name Cherry Doty

Section #

73335

Questions 1 7 are based on the Module 1 Assignment dB Access database attached in the
assignment instructions. Open the database and respond to the questions below:
1.

How many records does the ProjectEmployees table contain? How many fields are
there per record?
There are 9 records and each record contains 8 fields

2.

What problem would you encounter if you wanted to produce a listing by city form
the ProjectManager table? How would you solve this problem by altering the file
structure?
I noticed there is no a field for city, it is only managers address. So in order to get listing by city,
you should break up the managers address into address, city, state, zip code file format.
3. What data redundancies do you detect in the ProjectManager table? How could those
redundancies lead to anomalies?
The data redundancies Ive noticed in the ProjectManager table are: Holly B Parker appears three
times and George F Dorts appears twice. If either you move or change their phone number, these
changes must be made more than once and must be done correctly. And if there is any occurrence
is missed or there is any mistake when entering in the information on one, the data can be
different for the same person creating anomalies.
4. What data redundancies do you detect in the Project_Employees table? How could
those redundancies lead to anomalies?
The data redundancies Ive noticed in the Project_Employees table there are multiple entries for
John D Newson, Anne R Ramoras, and David F Schwann. So if any person moves or changes
their phone number, these changes must be made more than once and they must be done
correctly. And if any occurrence is missed or there is a mistake when entering the information on
one, the data are different for the same person creating anomalies like with John D Newsons
phone number. This shows that his personal information was not updated correctly on all files in
the database

CGS2541 Project 1 Assignment

5. Looking at the EMP_NAME and EMP_PHONE contents in the Projects_Employees
table, what change(s) would you recommend?
The changes that I would recommend the field set up should be EMP_FNAME, EMP_INITIAL,
EMP_LNAME, EMP_AREACODE, and EMP_PHONE.
6. Identify and discuss the serious data redundancy problems exhibited by the table
structure for the Teachers_Buildings
The serious data redundancy problems by the table structure for the Teachers_Buildings is likely
intance of data inconsistencies-two different initials have been entered for the teacher Maria
Cordoza.
And if you see the Teachers_Buildings table there are multiple entries for every teacher. So any
person moves or changes their phone number, these changes must be made more than once and
they must be done correctly. And any occurrence is missed or there is mistake when entering in
the information on one, the data are different for the same person creating anomalies like with
Maria Cordozas initial. This shows that her personal information was not updated correctly on
all files in the database.
7. Given the table structure for the Teachers_Buildings table, what problem(s) might you
encounter if building KOM were deleted?
You might lose all data related to KOM like teachers Horace Williston, Maria Cordoza, and Ann
Hawkins; also the data related in rooms 204E, 123, and 34; it causing a deletion anomaly.

Questions 8 10 are based on the diagram below:

CGS2541 Project 1 Assignment

8. Identify each relationship type and write all of the business rules.
A business rule is a brief description of policies, procedures, or principles within a specific
organization. And it also a description of operations to create/enforce actions within an
organizations environment. It must be in written correctly and kept up to date. In a sense,
business rules are misnamed: they apply to any organization large or small - a business, a
government unit, or a schools that stores and uses data to generate information. Using diagram
above, I identify each relation type and write it down all business rules.
COURSE generates CLASS. One course can generate many classes. Each class is generated by
one course. CLASS is referenced in ENROLL entity is also related STUDENT. Each entry in the
ENROLL entity references one student and the class for which that student has enrolled. A
student cannot enroll in the same class more than once. If a student enrolls in five classes, that
student will appear in the ENROLL entity five times, each time for a different class. STUDENT
is shown in ENROLL. One student can be shown in enrollment many times. Each individual
enrollment entry shows one student
9. Create the basic Crows Foot ERD for Tiny College, paste the ERD in the space below..

generates
COURSE

CLASS

ref
ere

shown in

STUDENT
10.

ENROLL
Create

the

UML

class diagram that reflects

the entities and relationships you identified in the relational diagram, paste your
diagram in the field below:
An entity is defined anything about which data are to collected and stored. Entity is a mapped
to a relational table. Entity is represented in the UML diagram by a rectangle. Relationship
described associates among data.
In the following UML diagrams COURSE generates CLASS. One course can generate many
classes 1:M. Each class is generated by one course. CLASS is referenced in ENROLL. One
class can be referenced in enrollment many times. So this relationships is1:M. Each
individual enrollment references one class. STUDENT is shown in ENROLL. One student
can be shown in enrollment many times. So this relationship is 1:M. Each individual
enrollment entry shows one student.

CGS2541 Project 1 Assignment

COURSE
CRS_CODE
DEPT_CODE
CRS_DESCRIP
TION
CRS_CREDIT

+generates

+shown in

1..1

STUDENT
STU_NUM
STU_LNAME
STU_FNAME
STU_UNIT
STU_DOB
STU_HRS
STU_CLASS
STU_GPA
STU_TRANSFER
DEPT_CODE
STU_PHONE
PROF_NUM

0..*

+generates
1..1

CLASS
CLASS_CODE
CRS_CODE
CLASS_SECTION
CLASS_TIME
CLASS_ROOM
PROF_NUM

1..1

+generates

0..*
0..*

+reference
ENROLL

+reference
d in

CLASS_CODE
STU_NUM
ENROLL_GRADE