CIS/336 ilab 1 of 7
Upcoming SlideShare
Loading in...5
×
 

CIS/336 ilab 1 of 7

on

  • 265 views

 

Statistics

Views

Total Views
265
Views on SlideShare
265
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

CIS/336 ilab 1 of 7 CIS/336 ilab 1 of 7 Document Transcript

  • CIS/336 iLab 1 of 7 - SQL CourseLABOVERVIEWScenario/SummaryThis lab will introduce you to the processes involved in defining one of the key components of a datamodel; the relationship diagram (RD). In this lab, you will draw a relationship diagram for two of thesteps shown. Keep in mind when you are trying to decide which side of the relationship should bethe "one" side and which should be the "many" that you must first decide which side has theprimary key, or unique identifier. Once you have decided the primary key of the relationship, youhave identified the "one" side of the relationship. Note that for an RD, the foreign key "many" sideof the relationship points to the primary key "one" side. The "one" side should have the arrowheadpoint of the connecting line. This is different than an entity/relationship diagram (ERD) that we willdraw next week, where the "many" side has crows feet.This will familiarize you with how to set up MS Visio to draw database diagrams. Steps 1 - 3 belowuse the Customer, Order, and Employee tables of a simplified Order Entry database. The Customertable records clients who have placed orders. The Order table contains the basic facts aboutcustomer orders. The Employee table contains facts about employees who take orders. The primarykeys 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 KEYconstraints.TABLE Customer has the following attributesCustNo 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 KEYTABLE Employee has the following attributesEmpNo NUMBER(5)EmpFirstName VARCHAR2(20)EmpLastName VARCHAR2(30)EmpPhone CHAR(15)EmpNo is the PRIMARY KEYTABLE Order has the following attributesOrdNo NUMBER(5)OrdDate DATE
  • CustNo NUMBER(5)EmpNo NUMBER(5)OrdNo is the PRIMARY KEYYour task for this lab is to create the required relationship diagram for steps 1 and 2 using MicrosoftVisio. Step 3 will require you to analyze the scenario given and present your own resolution to thequestion. Step 4 is an individual assignment that will introduce you to the group project and theprocess of identifying entities and attributes. When finished with the lab, you should have acomplete diagram using all 5 entities, a written explanation for #3, and two lists (entities andattributes) for Step 4.DeliverablesThe deliverable for this lab is a single MS Word document named "Lab1_solution_yourname" withthe diagram for problems 1 and 2, the written answer for the question in Step 3, and the lists ofentities and attributes for the Initial Project Exercise (Step 4). You should copy and paste thediagram from MS Visio into a Word document and use this document for Steps 3 and 4.LABSTEPSSTEP 1: Drawing your first ER diagram TitleIdentify the foreign key columns in the table structures above and draw a relationship diagramdepicting the relationships between the tables. In the Order table , the CustNo column referencesthe 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 diagramExtend your relationship diagram from problem 1 by adding two tables (OrdLine and Product). Tabledefinitions for the table structures and primary keys constraints are shown below. You will need toidentify the FOREIGN KEY(s) to complete this problem. When finished you should have a total of 5tables 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 topaste the diagram. View slide
  • TABLE Product has the following attributesProdNo CHAR(8)ProdName VARCHAR2(20)ProdNo is the PRIMARY KEYTABLE OrdLine has the following attributesOrdNo CHAR(8)ProdNo CHAR(8)Qty NUMBER(5)The combination of OrdNo and Prodno is thePRIMARY KEYSTEP 3: Should a NULL be allowed?From examination of the sample data and your current understanding of businesses in which orderscould be placed either in person, over the phone, or over the Internet, determine if it would bepermissible for null values to be allowed for the foreign key EmpNo in the Order table. This columnwould reference back to the EmpNo column in the employee table. Why or why not?OrdNo OrdDate CustNo EmpNoO1656777 02/11/2000 C8543321O7959898 02/19/2000 C8543321 E8544399STEP 4: Initial Project ExerciseAlthough the overall project itself will be done as a group, this first exercise is designed as anindividual effort and is intended to; (1) get you to read the project specifications, and; (2) introduce View slide
  • you to the first step in designing a database from scratch. This little exercise will have you see howmany entities and attributes you can find in the project specifications. In week three, you will workwith your assigned project team and compare notes on what you have found. This is not rocketscience here so remember, you are looking for people, places, things, and events (entities) and theattributes that describe themCLICK HERE TO GET THE SOLUTION !!!!!!!!