CIS164AG - Project Three - DeZign

T. A. S. K. - Tim's Animal Services and Kennels

In the first and second project assignments you were introduced to T.A.S.K.  At this point, we are going to model this system using DeZign.  We will need to resolve several potential problems with two pairs of many to many relationships.  Below is a very brief layout of the entities that we will include in the scope of this project and how they presently relate to other entities.

PART ONE [44 points]:

For this first part you will use DeZign to draw an ER diagram.  This diagram should include only the entities listed and any intersection entities that are needed.  Use the information below to determine what specific attributes are needed and which ones will be UIDs.  Every mandatory attribute MUST be indicated as not null. All attributes MUST have both a data type and a length.

Before you start: Set your Diagram options to what was used in the DeZign Practice activity.

PEN(pennbr, pensize)

pennbr - pen number that uniquely identifies the pen
pensize - required information of small, medium, large, doublewide
PET(petid, petname, petregname, petsize, petbreed, pettype)
petid - the pets unique id number
petname - the common name of the pet which we must know
petregname - we would like to know the pets registered name
petsize - the size of the pet (small, medium etc.) is helpful information
petbreed - again nice to know
pettype - we must know if it is a dog or cat etc.
CLASS(clid, cldesc, cllevel, clcost, clprerq)
clid - the unique way to know what the class is (i.e. RDO)
cldesc - a brief required description of the class (i.e.. dog obedience)
cllevel - the required level (i.e.. beginning)
clcost - the dollar amount of the class - we must know this when we add a class
clprerq - any prerequisites class is mandatory to know
BILL(billlnbr, billldate, billamount, billpaid)
billlnbr - the unique number that is used to identify the bill
billldate - the required date that the bill occurred
billamount - the amount that the bill is for which may not be know when the bill is first added.
billpaid - when the bill is paid then this field is filled in date that the payment was received
CUSTOMER(cuid, culname, cufname, cuaddress, cusity, cuzip, cuarea, cuphone)
cuid - the required information used to identify each customer
culname - we must know the customers last name
cufname - we also must know their first name
cuaddress - in order to send bills and other information in the mail we must know each customer's address
cusity - and of course we have to know their city
cuzip - and we can not things without a zip code
cuarea - the area code for the customer will be helpful but not required
cuphone - same with the phone number, helpful but not required
Next, the following many to many relationships need to be resolved by adding appropriate intersection entities and their attributes (which should be indicated as optional or mandatory and UID):
PET : PEN - A PET may stay at the Kennel on different dates.  Each day that the pets stays at the Kennel the pet is assigned to a given PEN.

CLASS : PET - Each CLASS section has one or more PETs in it and each PET can take one or more CLASSes.

Add verb phrases to your relationships.

Save your DeZign diagram.

Produce a report that includes only the ER diagram, Entity details and Relationship details as an MS Word document. Print all the pages of this report and staple them to the project three cover sheet.

PART TWO [6 points]:

On the cover sheet for project three, in the space provided, write / define limitations (Domain Integrity Constraints) for the following:

For example, if you were defining a domain Integrity constraint for the UID of EmpId, you might indicate that it is a 3 position field that has to be a number greater than 0 and less than 200.

Cover Sheet for Project 3