SlideShare uma empresa Scribd logo
1 de 4
SOLUTIONJUG.COM
CIS/336 iLab 1 of 7 - SQL Course
CLICK HERE TO GET THE SOLUTION !!!!!!!!
L A B O V E R V I E W
Scenario/Summary
This lab will introduce you to the processes involved in defining one of the key components of a data
model; the relationship diagram (RD). In this lab, you will draw a relationship diagram for two of the
steps shown. Keep in mind when you are trying to decide which side of the relationship should be
the "one" side and which should be the "many" that you must first decide which side has the
primary key, or unique identifier. Once you have decided the primary key of the relationship, you
have identified the "one" side of the relationship. Note that for an RD, the foreign key "many" side
of the relationship points to the primary key "one" side. The "one" side should have the arrowhead
point of the connecting line. This is different than an entity/relationship diagram (ERD) that we will
draw next week, where the "many" side has crow's feet.
This will familiarize you with how to set up MS Visio to draw database diagrams. Steps 1 - 3 below
use the Customer, Order, and Employee tables of a simplified Order Entry database. The Customer
table records clients who have placed orders. The Order table contains the basic facts about
customer orders. The Employee table contains facts about employees who take orders. The primary
keys of the tables are CustNo for Customer, EmpNo for Employee, and OrdNo for Order.
The following are the TABLE definitions for the first three tables showing the PRIMARY KEY
constraints.
TABLE Customer has the following attributes
CustNo NUMBER(5)
CustFirstName VARCHAR2(20)
CustLastName VARCHAR2(30)
CustCity VARCHAR2(30)
CustState CHAR(2)
CustZip CHAR(10)
CustBal NUMBER(12,2)
CustNo is the PRIMARY KEY
TABLE Employee has the following attributes
EmpNo NUMBER(5)
EmpFirstName VARCHAR2(20)
EmpLastName VARCHAR2(30)
EmpPhone CHAR(15)
EmpNo is the PRIMARY KEY
TABLE Order has the following attributes
OrdNo NUMBER(5)
OrdDate DATE
CustNo NUMBER(5)
EmpNo NUMBER(5)
OrdNo is the PRIMARY KEY
Your task for this lab is to create the required relationship diagram for steps 1 and 2 using Microsoft
Visio. Step 3 will require you to analyze the scenario given and present your own resolution to the
question. Step 4 is an individual assignment that will introduce you to the group project and the
process of identifying entities and attributes. When finished with the lab, you should have a
complete diagram using all 5 entities, a written explanation for #3, and two lists (entities and
attributes) for Step 4.
Deliverables
The deliverable for this lab is a single MS Word document named "Lab1_solution_yourname" with
the diagram for problems 1 and 2, the written answer for the question in Step 3, and the lists of
entities and attributes for the Initial Project Exercise (Step 4). You should copy and paste the
diagram from MS Visio into a Word document and use this document for Steps 3 and 4.
L A B S T E P S
STEP 1: Drawing your first ER diagram Title
Identify the foreign key columns in the table structures above and draw a relationship diagram
depicting the relationships between the tables. In the Order table , the CustNo column references
the Customer table and the EmpNo column references the Employee table. For each relationship,
identify the table on the "1" side of the relationship and the table on the "Many" side.
STEP 2: Extending the ER diagram
Extend your relationship diagram from problem 1 by adding two tables (OrdLine and Product). Table
definitions for the table structures and primary keys constraints are shown below. You will need to
identify the FOREIGN KEY(s) to complete this problem. When finished you should have a total of 5
tables represented in your diagram for this problem. To copy and paste the diagram into Word,
select Edit from the menu and then Copy Diagram. Open a Word document and use CTRL-V to
paste the diagram.
TABLE Product has the following attributes
ProdNo CHAR(8)
ProdName VARCHAR2(20)
ProdNo is the PRIMARY KEY
TABLE OrdLine has the following attributes
OrdNo CHAR(8)
ProdNo CHAR(8)
Qty NUMBER(5)
The combination of OrdNo and Prodno is the
PRIMARY KEY
STEP 3: Should a NULL be allowed?
From examination of the sample data and your current understanding of businesses in which orders
could be placed either in person, over the phone, or over the Internet, determine if it would be
permissible for null values to be allowed for the foreign key EmpNo in the Order table. This column
would reference back to the EmpNo column in the employee table. Why or why not?
OrdNo OrdDate CustNo EmpNo
O1656777 02/11/2000 C8543321
O7959898 02/19/2000 C8543321 E8544399
STEP 4: Initial Project Exercise
Although the overall project itself will be done as a group, this first exercise is designed as an
individual effort and is intended to; (1) get you to read the project specifications, and; (2) introduce
you to the first step in designing a database from scratch. This little exercise will have you see how
many entities and attributes you can find in the project specifications. In week three, you will work
with your assigned project team and compare notes on what you have found. This is not rocket
science here so remember, you are looking for people, places, things, and events (entities) and the
attributes that describe them.
CLICK HERE TO GET THE SOLUTION !!!!!!!!

Mais conteúdo relacionado

Mais de comp274

Itco 620 unit 5 project
Itco 620 unit 5 projectItco 620 unit 5 project
Itco 620 unit 5 project
comp274
 
Cis 355 ilab 4 of 6
Cis 355 ilab 4 of 6Cis 355 ilab 4 of 6
Cis 355 ilab 4 of 6
comp274
 
Cis 355 ilab 2 of 6
Cis 355 ilab 2 of 6Cis 355 ilab 2 of 6
Cis 355 ilab 2 of 6
comp274
 
Cis 355 ilab 1 of 6
Cis 355 ilab 1 of 6Cis 355 ilab 1 of 6
Cis 355 ilab 1 of 6
comp274
 
Cis 355 ilab 6 of 6
Cis 355 ilab 6 of 6Cis 355 ilab 6 of 6
Cis 355 ilab 6 of 6
comp274
 
Cis 170 ilab 4 of 7
Cis 170 ilab 4 of 7Cis 170 ilab 4 of 7
Cis 170 ilab 4 of 7
comp274
 
Cis 170 ilab 2 of 7
Cis 170 ilab 2 of 7Cis 170 ilab 2 of 7
Cis 170 ilab 2 of 7
comp274
 
Cis 170 ilab 1 of 7
Cis 170 ilab 1 of 7Cis 170 ilab 1 of 7
Cis 170 ilab 1 of 7
comp274
 
Cis 170 ilab 5 of 7
Cis 170 ilab 5 of 7Cis 170 ilab 5 of 7
Cis 170 ilab 5 of 7
comp274
 
Cis 115 week 6 exercise
Cis 115 week 6 exerciseCis 115 week 6 exercise
Cis 115 week 6 exercise
comp274
 
Cis 115 i lab 4 of 7
Cis 115 i lab 4 of 7Cis 115 i lab 4 of 7
Cis 115 i lab 4 of 7
comp274
 

Mais de comp274 (11)

Itco 620 unit 5 project
Itco 620 unit 5 projectItco 620 unit 5 project
Itco 620 unit 5 project
 
Cis 355 ilab 4 of 6
Cis 355 ilab 4 of 6Cis 355 ilab 4 of 6
Cis 355 ilab 4 of 6
 
Cis 355 ilab 2 of 6
Cis 355 ilab 2 of 6Cis 355 ilab 2 of 6
Cis 355 ilab 2 of 6
 
Cis 355 ilab 1 of 6
Cis 355 ilab 1 of 6Cis 355 ilab 1 of 6
Cis 355 ilab 1 of 6
 
Cis 355 ilab 6 of 6
Cis 355 ilab 6 of 6Cis 355 ilab 6 of 6
Cis 355 ilab 6 of 6
 
Cis 170 ilab 4 of 7
Cis 170 ilab 4 of 7Cis 170 ilab 4 of 7
Cis 170 ilab 4 of 7
 
Cis 170 ilab 2 of 7
Cis 170 ilab 2 of 7Cis 170 ilab 2 of 7
Cis 170 ilab 2 of 7
 
Cis 170 ilab 1 of 7
Cis 170 ilab 1 of 7Cis 170 ilab 1 of 7
Cis 170 ilab 1 of 7
 
Cis 170 ilab 5 of 7
Cis 170 ilab 5 of 7Cis 170 ilab 5 of 7
Cis 170 ilab 5 of 7
 
Cis 115 week 6 exercise
Cis 115 week 6 exerciseCis 115 week 6 exercise
Cis 115 week 6 exercise
 
Cis 115 i lab 4 of 7
Cis 115 i lab 4 of 7Cis 115 i lab 4 of 7
Cis 115 i lab 4 of 7
 

Último

Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptxHarnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
FIDO Alliance
 
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
Tales from a Passkey Provider  Progress from Awareness to Implementation.pptxTales from a Passkey Provider  Progress from Awareness to Implementation.pptx
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
FIDO Alliance
 

Último (20)

Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
 
TopCryptoSupers 12thReport OrionX May2024
TopCryptoSupers 12thReport OrionX May2024TopCryptoSupers 12thReport OrionX May2024
TopCryptoSupers 12thReport OrionX May2024
 
The Metaverse: Are We There Yet?
The  Metaverse:    Are   We  There  Yet?The  Metaverse:    Are   We  There  Yet?
The Metaverse: Are We There Yet?
 
Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptxHarnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
 
(Explainable) Data-Centric AI: what are you explaininhg, and to whom?
(Explainable) Data-Centric AI: what are you explaininhg, and to whom?(Explainable) Data-Centric AI: what are you explaininhg, and to whom?
(Explainable) Data-Centric AI: what are you explaininhg, and to whom?
 
Using IESVE for Room Loads Analysis - UK & Ireland
Using IESVE for Room Loads Analysis - UK & IrelandUsing IESVE for Room Loads Analysis - UK & Ireland
Using IESVE for Room Loads Analysis - UK & Ireland
 
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdfHow Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
 
Linux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdf
Linux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdfLinux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdf
Linux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdf
 
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
Tales from a Passkey Provider  Progress from Awareness to Implementation.pptxTales from a Passkey Provider  Progress from Awareness to Implementation.pptx
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
 
Google I/O Extended 2024 Warsaw
Google I/O Extended 2024 WarsawGoogle I/O Extended 2024 Warsaw
Google I/O Extended 2024 Warsaw
 
WebAssembly is Key to Better LLM Performance
WebAssembly is Key to Better LLM PerformanceWebAssembly is Key to Better LLM Performance
WebAssembly is Key to Better LLM Performance
 
Microsoft CSP Briefing Pre-Engagement - Questionnaire
Microsoft CSP Briefing Pre-Engagement - QuestionnaireMicrosoft CSP Briefing Pre-Engagement - Questionnaire
Microsoft CSP Briefing Pre-Engagement - Questionnaire
 
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
Where to Learn More About FDO _ Richard at FIDO Alliance.pdfWhere to Learn More About FDO _ Richard at FIDO Alliance.pdf
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
 
ERP Contender Series: Acumatica vs. Sage Intacct
ERP Contender Series: Acumatica vs. Sage IntacctERP Contender Series: Acumatica vs. Sage Intacct
ERP Contender Series: Acumatica vs. Sage Intacct
 
Simplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdf
Simplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdfSimplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdf
Simplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdf
 
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...
 
Portal Kombat : extension du réseau de propagande russe
Portal Kombat : extension du réseau de propagande russePortal Kombat : extension du réseau de propagande russe
Portal Kombat : extension du réseau de propagande russe
 
Oauth 2.0 Introduction and Flows with MuleSoft
Oauth 2.0 Introduction and Flows with MuleSoftOauth 2.0 Introduction and Flows with MuleSoft
Oauth 2.0 Introduction and Flows with MuleSoft
 
Intro in Product Management - Коротко про професію продакт менеджера
Intro in Product Management - Коротко про професію продакт менеджераIntro in Product Management - Коротко про професію продакт менеджера
Intro in Product Management - Коротко про професію продакт менеджера
 
How we scaled to 80K users by doing nothing!.pdf
How we scaled to 80K users by doing nothing!.pdfHow we scaled to 80K users by doing nothing!.pdf
How we scaled to 80K users by doing nothing!.pdf
 

Cis 336 ilab 1 of 7

  • 1. SOLUTIONJUG.COM CIS/336 iLab 1 of 7 - SQL Course CLICK HERE TO GET THE SOLUTION !!!!!!!! L A B O V E R V I E W Scenario/Summary This lab will introduce you to the processes involved in defining one of the key components of a data model; the relationship diagram (RD). In this lab, you will draw a relationship diagram for two of the steps shown. Keep in mind when you are trying to decide which side of the relationship should be the "one" side and which should be the "many" that you must first decide which side has the primary key, or unique identifier. Once you have decided the primary key of the relationship, you have identified the "one" side of the relationship. Note that for an RD, the foreign key "many" side of the relationship points to the primary key "one" side. The "one" side should have the arrowhead point of the connecting line. This is different than an entity/relationship diagram (ERD) that we will draw next week, where the "many" side has crow's feet. This will familiarize you with how to set up MS Visio to draw database diagrams. Steps 1 - 3 below use the Customer, Order, and Employee tables of a simplified Order Entry database. The Customer table records clients who have placed orders. The Order table contains the basic facts about customer orders. The Employee table contains facts about employees who take orders. The primary keys of the tables are CustNo for Customer, EmpNo for Employee, and OrdNo for Order. The following are the TABLE definitions for the first three tables showing the PRIMARY KEY constraints. TABLE Customer has the following attributes CustNo NUMBER(5) CustFirstName VARCHAR2(20) CustLastName VARCHAR2(30) CustCity VARCHAR2(30) CustState CHAR(2) CustZip CHAR(10) CustBal NUMBER(12,2)
  • 2. CustNo is the PRIMARY KEY TABLE Employee has the following attributes EmpNo NUMBER(5) EmpFirstName VARCHAR2(20) EmpLastName VARCHAR2(30) EmpPhone CHAR(15) EmpNo is the PRIMARY KEY TABLE Order has the following attributes OrdNo NUMBER(5) OrdDate DATE CustNo NUMBER(5) EmpNo NUMBER(5) OrdNo is the PRIMARY KEY Your task for this lab is to create the required relationship diagram for steps 1 and 2 using Microsoft Visio. Step 3 will require you to analyze the scenario given and present your own resolution to the question. Step 4 is an individual assignment that will introduce you to the group project and the process of identifying entities and attributes. When finished with the lab, you should have a complete diagram using all 5 entities, a written explanation for #3, and two lists (entities and attributes) for Step 4. Deliverables The deliverable for this lab is a single MS Word document named "Lab1_solution_yourname" with the diagram for problems 1 and 2, the written answer for the question in Step 3, and the lists of
  • 3. entities and attributes for the Initial Project Exercise (Step 4). You should copy and paste the diagram from MS Visio into a Word document and use this document for Steps 3 and 4. L A B S T E P S STEP 1: Drawing your first ER diagram Title Identify the foreign key columns in the table structures above and draw a relationship diagram depicting the relationships between the tables. In the Order table , the CustNo column references the Customer table and the EmpNo column references the Employee table. For each relationship, identify the table on the "1" side of the relationship and the table on the "Many" side. STEP 2: Extending the ER diagram Extend your relationship diagram from problem 1 by adding two tables (OrdLine and Product). Table definitions for the table structures and primary keys constraints are shown below. You will need to identify the FOREIGN KEY(s) to complete this problem. When finished you should have a total of 5 tables represented in your diagram for this problem. To copy and paste the diagram into Word, select Edit from the menu and then Copy Diagram. Open a Word document and use CTRL-V to paste the diagram. TABLE Product has the following attributes ProdNo CHAR(8) ProdName VARCHAR2(20) ProdNo is the PRIMARY KEY TABLE OrdLine has the following attributes OrdNo CHAR(8) ProdNo CHAR(8) Qty NUMBER(5) The combination of OrdNo and Prodno is the PRIMARY KEY STEP 3: Should a NULL be allowed? From examination of the sample data and your current understanding of businesses in which orders could be placed either in person, over the phone, or over the Internet, determine if it would be permissible for null values to be allowed for the foreign key EmpNo in the Order table. This column would reference back to the EmpNo column in the employee table. Why or why not? OrdNo OrdDate CustNo EmpNo O1656777 02/11/2000 C8543321
  • 4. O7959898 02/19/2000 C8543321 E8544399 STEP 4: Initial Project Exercise Although the overall project itself will be done as a group, this first exercise is designed as an individual effort and is intended to; (1) get you to read the project specifications, and; (2) introduce you to the first step in designing a database from scratch. This little exercise will have you see how many entities and attributes you can find in the project specifications. In week three, you will work with your assigned project team and compare notes on what you have found. This is not rocket science here so remember, you are looking for people, places, things, and events (entities) and the attributes that describe them. CLICK HERE TO GET THE SOLUTION !!!!!!!!