Tài liệu Activity 6.1: Translating the Logical Data Design pdf

Activity 6.1: Translating the Logical Data Design In this activity, you will evaluate the logical design for part of the solution developed for the Ferguson and Bardell, Inc.. From this

Activity 6.1: Translating the Logical

Data Design

In this activity, you will evaluate the logical design for part of the solution developed for the Ferguson and Bardell, Inc case study From this design, you will determine the tables, columns, data types, and keys that are appropriate for the solution

Objectives

After completing this activity, you will be able to:

! Evaluate a logical data design

! Determine the appropriate data types for columns in a table

! Produce a physical data design

Before You Begin

This activity is completed individually, with a class discussion to follow

Time to complete this activity: 30 minutes

Exercise 1:

Deriving a Physical Data Design from a Logical Data Design

In this exercise, you will use the logical data design presented below and derive

a physical data design

This picture is file v05_1609a_act52-answer.vsd or bmp

TypeID (FK)

FirstName

MiddleInitial

LastName

Address1

Address2

City

State

Zip

SSN

E-Mail

Salary

BillableRate

EmployeeID (PK)

Employee

ClientID (FK) EmployeeID (FK) JobID (FK) TaskID(FK) Date Expenses TotalHours BillableHours Description

TimesheetID (PK) Timesheet

ClientID (FK) TimesheetID (FK) Date

Amount Work Description

InvoiceID (PK) Invoice

Name Address1 Address2 City State Zip

ClientID (PK) Client

EmployeeID (FK) Make

Model VIN Year BeginMileage EndMileage

VehicleID (PK) Vehicle

Is Issued

Completes

Is Made From

1

1 ∞

Is Sent To

1

0 ∞

Contracts With

1

1 ∞

JobDesc JobID (PK) Job

Bills Time To Bills Time To

VehicleID (FK) MaintenanceCost MaintenanceDesc MaintenanceDate MaintenanceMiles

MaintID (PK) VehicleMaint Can Have

0 ∞ 1

1

1 ∞

TypeDesc TypeID (PK) EmployeeType

Is Classified As

1

1

1 ∞

1

1 ∞

ClientID(FK) EmployeeID(FK) StartDate EndDate Description

ContractID(PK) Contract

Purchases

1

1

0 ∞

TaskDesc TaskID (PK) Task

0 ∞

0 ∞

1 ∞

! Derive the physical data design

1 Using the following table templates, translate each entity into a table

You can have more tables than entities, and you might not need all the templates

2 For each table, translate each attribute into a field

You can have more fields than attributes, and you might not need all the rows in the templates

3 Select a data type for each field

4 Label all primary and foreign keys as follows:

Primary Key (PK) Foreign Key (FK)

Solution found in file v06_1609a_act61-answer.vsd or bmp Answer Key: Int Integer

Currency Currency DInt Double Integer Date Date

VChar Variable Character Float Floating Point Number (N) Not Null field

Next, you will present your findings to the class

Table Field Data type

Table Field Data type

THIS PAGE INTENTIONALLY LEFT BLANK

Table Field Data type