Scribd
Upload
26 views

CH6 Problems 10

Uploaded by

007503711
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
26 views

CH6 Problems 10

Uploaded by

007503711
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Initial Relational Schema:

Functional Dependencies:

We can infer the following dependencies from the table:

1. CLIENT_NUM → CLIENT_NAME, CLIENT_REGION


Each client’s number determines their name and region.

2. CONTRACT_NUMBER → CONTRACT_DATE, CONTRACT_AMOUNT, CLIENT_NUM


The contract number determines the contract details and the client associated with it.

3. CONSULTANT_NUM → CONSULTANT_NAME, CONSULTANT_REGION


Each consultant’s number determines their name and region.

4. CONTRACT_NUMBER → CONSULT_CLASS_1, CONSULT_CLASS_2, CONSULT_CLASS_3,


CONSULT_CLASS_4, CONSULTANT_NUM_1, CONSULTANT_NUM_2,
CONSULTANT_NUM_3, CONSULTANT_NUM_4
The contract number also determines which classes of service and which consultants are
assigned to the contract.

Transitive and Partial Dependencies:

 CLIENT_NUM → CLIENT_NAME, CLIENT_REGION is a partial dependency in the current


schema because CLIENT_NUM should belong in a separate CLIENT table.

 CONTRACT_NUMBER → CONSULTANT_NUM_X, CONSULT_CLASS_X creates multivalued


dependencies, which can be eliminated by separating out consultants and consulting
services into their own tables.

3NF:

Table 1 (CLIENT):

 CLIENT_NUM is the primary key, and all client-related information is stored here.
Table 2 (CONTRACT):

 CONTRACT_NUMBER is the primary key, and it stores the contract-specific details with a
foreign key relationship to CLIENT_NUM.

Table 3 (CONSULTANT):

 CONSULTANT_NUM is the primary key, storing all consultant-related details.

Table 4 (CONTRACT_CONSULTANT):

 This table resolves the many-to-many relationship between contracts and consultants, with
a composite key of CONTRACT_NUMBER and CONSULTANT_NUM.

Table 5 (CONTRACT_CLASS):

 This table stores the consulting services (classes) provided under each contract.

ERD:

 CLIENT has a 1:M, relationship with CONTRACT because each client can sign multiple
contracts.
 CONTRACT_CONSULTANT table resolves the many-to-many relationship between
CONTRACT and CONSULTANT.
 CONTRACT_CLASS stores the consulting services related to each contract.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy