Page 1 of 11 A. Lab # BSBA BIS245A-5B B.docx

of 11
A. Lab # : BSBA BIS245A-5B
B. Lab 5B of 7: Completing Forms
C. Lab Overview--Scenario/Summary
TCO(s):
5. Given a physical database containing tables and
relationships, create
forms which demonstrate effective user-interface design and
allow for
efficient entry and retrieval of data.
Scenario/Summary
The lab begins with creating a form in Access using the Form
Wizard. After the
form is created, the user can use Themes to change the
appearance of the form.
The second part of the lab uses Form Design to create a form.
Finally, the form
will be customized.
Upon completing this lab, you should be able to

• create a form using the Form Tool;
• create a form using Form Design; and
• create a form using the Form Wizard.
D. Deliverables
Submit the MS Access Database file that contains the forms
created in this lab.
Step Deliverable Points
1 Form 1 – Form Tool - step-by-step 5
2 Form 2 – Form Design – step-by-step 5
3 Form 3 – Form Wizard—Employee/Customers Multi-Table
Form
– step-by-step
5
4 Form 4 – Suppliers and Products Multi-Table Form 10
E. Lab Steps
Preparation
1. Get the Database from Doc Sharing
Page 2 of 11
a. Download the Lab5_Start.accdb Northwind database file from
your

course Doc Sharing panel (Labs view), and Save the file to your
local
drive.
2. Using Citrix for MS Visio and/or MS Access
a. If you are using the Citrix remote lab, follow the login
instructions
located in the iLab tab in Course Home.
b. You will have to upload the Lab5_Start.accdb file to your
Citrix folder.
Follow the instructions located on the iLab tab in Course Home.
3. Start MS Access
a. If you are using Citrix, click on Microsoft Office
Applications folder.
b. If you are using Visio on a local computer, select Microsoft
Office from your
Program Menu.
Lab
Step 1: Using the Form Tool
Select Employees table as in the following figure. You will see
the Employees
table highlighted.
Click the Create tab, and then click the Form tool.

of 11
After clicking the Form button, a new form is created by
Access.
The appearance of the form can be easily modified using the
Themes option on
the Design ribbon. As you move your cursor over the various
themes, the form
will adjust to preview how the modified form would look. You
may select any
theme for your form.
Click the Save button to save the form. Name it Lab5_Form1,
and then close the
form.
Step 2: Using the Form Design
Page 4 of 11
Click the Create tab; then, click on Form Design. (Make sure
that you do not
have any of the tables selected in the Tables list on the left side

of the screen.)
After clicking the Form Design, a new form will be shown as
the following
Page 5 of 11
Click the Add Existing Fields
option, and then click Show All
Tables to show all the tables in
the database. Drag and drop
fields from the Customer table
to the form. You can also
double click the fields that you
want to add. Select a number
of fields from the Customers
table. Adjust the location of the
fields. Then, click the Form
option in the View list to see
the form. The View button is
highlighted at the right.

After viewing the form, click the View button again, and select
Design View to go
back to form design. Save the form as Lab5_Form2.
Step 3: Creating Multi-Table Forms
You can incorporate data from several tables in a single form.
In this step, you
will create a form that displays data concerning one employee.
The form will also
Page 6 of 11
display data concerning the many customers that your
employees serve. This
type of relationship between employees and customers is called
one-to-many
relationships (one employee serving many customers). In this
relationship, the
Employees table is the “one” table and the Customers table is
the “many” table.
To create a multi-table form using the Form Wizard
• click the Create tab, then select the Form Wizard; and
• make sure that Customers table is selected in the
Table/Queries box.
• Select CustomerID, CompanyName, ContactName,
ContactTitle, Address,

City, Region, PostalCode, Country, and Phone Fields from
Customers table.
• Back in the Tables/Queries, click on the down arrow and
select Employees
table. See illustration on next page.
Page 7 of 11
• Select EmployeeID, LastName, FirstName, Photo, and
ReportsTo from that
table, then click Next button.
• Make sure that by Employees is selected in “How do you want
to view your
data?”
• You also have the option to select Form with subform(s) or
Linked forms.
Select Form with subform(s), then click Next.
Page 8 of 11

• In the next screen, you have the option of selecting the layout
of your
subform. Select Tabular, and then click Next.
• Assign a title to your form (Lab5_Form3) and subform
(Lab5_Subform3),
and click finish.
• Click on View, and then view the form in Form View.
Page 9 of 11
Before closing the form, go to Design View, and change the
Caption
property for the form to Employees. (See below.) Return to
Form View
before saving your form.

of 11
In Form View your form should display nine records, showing
employees and the
customers that they serve. These records can be cycled through
on using the
navigation options available on the lower left of the application
screen.
You will be prompted to save changes when closing the form.
Say Yes to save
changes at the prompt, and close the form.
Step 4: Create a Multi-Table Form
Following instructions provided in Step 3, create a multi-table
form, showing what
products are supplied by which supplier.
Requirements: There is ONE Supplier for MANY Products. You
must display the
following fields: SupplierID, CompanyName, ContactName,

ContactTitle, Address,
City, Region, PostalCode, Country, and Phone fields along with
ProductID,
ProductName, and CategoryID.
Page 11 of 11
Your form should look like the following
There should be 29 records in your suppliers, each providing
numerous products.
Save your form as Lab5_form4, and the Subform as
Lab5_Subform4.
Step 5: Submit Deliverables
Save your MS Access Lab5_Start.accdb file as
YourName_Lab5_ Final.accdb
Submit the Access file created during this assignment to the
Dropbox located on
the silver tab at the top of this page. (See Syllabus/"Due Dates
for Assignments &
Exams" for due dates.)

End of Lab 5B
Page 1 of 5
A. Lab # : BSBA BIS245A-5A
B. Lab 5A of 7 : Database design using Visio, and based on data
requirements
and business rules focusing on normalizing data to third normal
form.
C. Lab Overview--Scenario/Summary:
TCO(s):
2. Given a situation containing entities, business rules, and data
requirements,
create the conceptual model of the database using a database
modeling tool.
Scenario:
You have been asked to create a database model using the MS
Visio Database
Model Diagram Template. The purpose of this lab is to provide
experience
normalizing the database to third normal form based on limited
instructions, data

requirements, and associated business rules.
Upon completing this lab, you will be able to
1. create a new Visio file for database design; and
2. using the data requirements and the business rules provided,
develop a
conceptual model (ERD), including attribute data types and
required field
lengths.
D. Deliverables
Section Deliverable Points
Step 1 YourName_Lab5A_ERMatrix.docx
Step 3 YourNameLab5A.vsd (Visio Diagram)
E. Lab Steps
Preparation
1. Get the Lab5A_ERMatrix.docx document from Doc Sharing:
a. Download the Lab5A_ERMatrix document file from your
course Doc
Sharing panel (Labs view), and Save the file to your local drive.
instructions
located in the iLab tab in Course Home.
3. Start MS Visio

a. Open Microsoft Office, Visio application, or
b. if you are using Citrix, click on Microsoft Office
Applications folder
to start Visio.
Page 2 of 5
Lab
Step 1: Identify the entities and relationships.
a. Over the past four weeks, you have created ERDs based on
information
provided. This week, you will complete the ERD being sure to
normalize it to
3NF (third normal form). Normalization is the systematic
application of rules
designed to eliminate redundancy from the database. Data in
previous weeks
was, to some extent, normalized for you. This week, it is not.
An abbreviated
list of the data requirements follows.
College Scheduling Data Requirements
Student ID
Student First Name
Student Last Name

Course Code
Course Name
Course Description
Course Credit Hours
Course Time
Course Days
Instructor ID
Instructor First Name
Instructor Last Name
Room Number
Room Capacity
b. Open the Word file in the Week 5 Lab Materials,
Lab5A_ERMatrix.docx
c. Save the Word file as YourName_Lab5A_ERMatrix.
d. An ER Matrix helps define both the entities and the
relationships between the
entities. Using the partially completed ER Matrix below as a
guide, complete
the matrix.
Hint: You should end up with four entities.
1. List each entity both across and down.
2. Determine whether a relationship exists between entities and
define that
relationship with a verb phrase. (NOTE: The entity with the
greatest
number of related entities is usually the center of the ER
diagram.)
3. Identify minimum (Optional or Mandatory) and maximum

(only one, or one
or more).
Page 3 of 5
Student Course
Student none Enrolls in;
Mandatory
One or
more
Course Is taken by:
Optional
One or
more
none
e. Save the completed matrix to submit as part of your lab.
Step 2: Create the initial ERD based on the matrix.
a. Open a new blank Database Model Diagram in Visio. If you
need assitance with

this, refer to the Week 1 Lab Instructions. Be sure that all
options are set
consistent to those used in previous weeks so that you generate
your model in
Crow’s Foot notation.
b. One of the issues in denormalized data is that it can result in
many-to-many
relationships that are not compatible with the relational
database. Visio does
not allow creation of a many-to-many relationship because of
this
incompatibility. Therefore, for any many-to-many relationships
in your data,
you will need to create two one-to-many relationships. See the
example
below:
Page 4 of 5
c. Based on the information from Step 1, create the initial ERD
for the College
Scheduling database including the many-to-many relationships.
If you need
assistance to create the entities, refer to labs from Weeks 1 and
2.

d. Assign the primary keys and attributes from the data
requirements to the
proper entities.
e. Save the file as YourName_Lab5A.vsd.
Step 3: Normalize the database
a. While the initial ERD is accurate, if you design a database
without deviating
from it, you will encounter problems. For example, a course is
offered many
times. If you use the course code, for example BIS245, as the
primary key,
you will only be able to list the course once. There are three
possible solutions.
1. Assign another primary key, such as an auto-number field, so
that
the course can be listed multiple times. However, this is not
acceptable because it introduces redundancy rather than
reducing it.
2. Use a composite primary key consisting of the Course Code
and the
Section code. If you create a unique section code (EXAMPLE:
YearTerm_Section or 2010SpringA_A), then you can list the
course
repeatedly. Again, this introduces redundancy, and is not an
acceptable solution.
3. Split the table to create two tables. To stay consistent with
DeVry

terminology, create a second Section table. To ensure that a
course is
not entered twice, you might modify the Section code to include
the
course: BIS245_2010SpringA_A. By consistently using this
format,
you should not be able to duplicate the section, and can avoid a
complicated composite key. However, as the Section table will
serve
as an associative entity, it is acceptable to borrow the primary
keys of
the parent tables.
b. Open the Visio file from Step 2, and add a new page. Change
the page tab to
read Revised. Revise the initial ERD based on the following
information.
1. A Course may exist without being offered. It exists in the
catalog.
Courses are scheduled for a term and given a section. It is the
schedule course (Section) that students enroll in, that are
scheduled
in rooms and assigned instructors.
2. A Student can exist without being enrolled in a course.
3. An Instructor can exist without being assigned to teach a
course.
4. A Room can exist without being scheduled for a course.
c. Save the file with your revised ERD.

of 5
Lab 5A Final Deliverables
a. YourName_Lab5A_ERMatrix.docx (Word Document) from
Lab 5A Step 1
b. YourName_Lab5A.vsd (Visio Diagram) from Lab 5A Step 3.
Submit these files to the Week 5 iLab Dropbox.
END OF LAB
DeVry University
Student Lab Activity
BIS245 Database Essentials for Business with Lab
A. Student Name:
B. Lab 5A ER Matrix:
Student
Course
Student
none
Enrolls in;
Mandatory

One or more
Course
Is taken by:
Optional
One or more
none
DeVry University
Copyright © 2010 by DeVry Educational Development
Corporation.
All rights reserved. No part of this work may be reproduced or

used in any form or by any means – graphic, electronic, or
mechanical,
including photocopying, recording, Web distribution or
information storage and retrieval systems – without the prior
consent of DeVry
Educational Development Corporation.
BIS245_W4b_iLab_Instructions.docx Page 1 of 20
A. Lab # : BSBA BIS245A-4B
B. Lab 4B of 7: Completing Queries
C. Lab Overview – Scenario / Summary:
TCOs:
# 6: Given a physical database containing tables and
relationships and business requirements,
create the necessary queries.
Scenario/Summary
The lab begins with a simple example of query development
using Access; then, evolves to more
complex queries which the student should perform after
completing the first exercise. The student
can create a query with the wizard, with query design view, or

with SQL statements. The Northwind
database will be used again in this lab.
Upon completing this lab, you should be able to:
• Create a query by following lab instruction.
• Create a query by using either query designer, or query
wizard.
• Create a query by using SQL statements.
• Interpret the results of queries
D. Deliverables:
Submit the MS Access Database file that contains the queries
created in this lab.
Step Deliverable Points
1 Query #1 – step-by-step
2 Query #2 – Compound Statements
3 Query #3 – Suppliers – step-by-step
4 Query #4 – Suppliers (more advanced)
5 Query #5 – Customers – using SQL Statements
6 Query #6 – Putting it all together
E. Lab Steps:
DeVry University

Corporation.
mechanical,
consent of DeVry
Preparation:
1. Get the Database from Doc Sharing:
a. Download the “Lab4_Start.accdb” Northwind database file
from your course “Doc
Sharing” panel (Labs view) & Save the file to your local drive.
2. Using Citrix for MS Visio and / or MS Access
instructions located in the
iLab tab in Course Home.
b. You will have to upload the “Lab4_Start.accdb” file to your
Citrix folder. Follow the
instructions located on the iLab Tab in Course Home.
3. The E-R diagram for the database is represented below:

4. Start MS Access:
a. If you are using Citrix, click on Microsoft Office
Applications folder
b. If you are using Visio on a local computer, select Microsoft
Office from your Program Menu
DeVry University
Corporation.
mechanical,
consent of DeVry

Lab:
Step 1: Query #1 using step-by-step instructions
Open the Lab4_Start.accdb in Access by going through the File
Menu, Open command.
DeVry University
Corporation.
mechanical,
consent of DeVry

Query 1: In the Create ribbon, use the Query Design function to
find the list of employees who worked
on orders placed by UK customers. The list should be presented
in ascending order of the employee
last names.
DeVry University
Corporation.

mechanical,
consent of DeVry
After clicking “Query Design”, the Tables window will open.
Hold down the Ctrl key, and click to
select three tables (Customers, Orders, and Employees). Then,
click "Add".
DeVry University

Corporation.
mechanical,
consent of DeVry
The tables are added to the query design panel. Drag and drop
(or double click on the field names) to
add the FirstName and LastName fields from the Employees
table onto the query design grid. Add
the Country field from the Customers table.
In the Country field, Criteria Row, enter “UK” to filter so that
only the UK customers will show in the
query results. Also, set the Last Name field, Sort Row to
Ascending.
The grid now looks like the following. (Note that the tables
have been rearranged to better show the
relationships. You may choose to do this also.)

DeVry University
Corporation.
mechanical,
consent of DeVry
Select the Property Sheet function from the Query Tools,
Design ribbon. Set the “Unique Value”
property to Yes. Notice that the properties shown are for the
query rather than a particular field. If you
are not seeing the appropriate properties, move your cursor to
the upper part of the design grid
displaying the tables.

DeVry University
Corporation.
mechanical,
consent of DeVry
Click the "Run" icon to run the query.

The query result should appear as below.
DeVry University
Corporation.
mechanical,
consent of DeVry
Save the query by clicking the Save button at the top left
portion of the screen. For a query name
enter “Lab4_Query1”.
Step 2: Query #2 Using Compound Statements

Using the same procedures described in step 1, find the list of
employees who worked on orders
placed by Germany, UK, and USA customers. The list should be
presented in ascending order of the
employee last names. Make sure Unique Values is set to No.
Hint: in the criteria row, under Country, key in “UK” OR
“Germany” OR “USA”
The results will look like the following (only partial table is
displayed to save space. You should
produce 300 records):
DeVry University
Corporation.
mechanical,
consent of DeVry

Save the query as “Lab4_Query2”.
Step 3: Query #3 using step-by-step instructions
Query 3: Make a list of suppliers, who supply products ordered
by USA customers.
Note that for this query, only the major steps are demonstrated
here. Refer to previous steps if you
need further assistance.
Create a new query using the Query wizard and add the
following tables. Name the query as
DeVry University
Corporation.

mechanical,
consent of DeVry
“Lab4_Query3”.
Tables to add:
• Customers
• Order Details
• Orders
• Products
• Suppliers
DeVry University

Corporation.
mechanical,
consent of DeVry
Here’s a snapshot of how your query should look like in the
Design mode.
Note that you need to set the properties to display only the
unique values (just like Query1). Also,
notice that even though the CompanyName and Country fields
from the Customers table are added to
the grid, the Show check boxes are unchecked. These two fields
will not appear in the query results.

DeVry University
Corporation.
mechanical,
consent of DeVry
When executed, your query should return 29 records.
DeVry University

Corporation.
mechanical,
consent of DeVry
Step 4: Query #4
Using the procedures described in step 3, find the list of
suppliers who supply products ordered by
German customers.
When executed, your query should return 29 records, a part of
which is displayed.
Save the query as “Lab4_Query4”.
Note that you need to set the properties to display only the
unique values (just like Query1).
Step 5: Query #5

DeVry University
Corporation.
mechanical,
consent of DeVry
Query 5: Find the customer details of all your customers in
USA. Use the straight SQL approach (as
opposed to Query wizard).
In this query, we won’t use the Query Designer or Query
wizard. This is to demonstrate the SQL
coding approach. SQL (Structured Query Language) is a very
powerful language. It has rich set of
features to manipulate data in a number of ways.

Guidelines for SQL Query
-‐ Select the fields for the query
-‐ Determine which table or tables contain those fields
-‐ Determine criteria
-‐ Determine Sort order
-‐ Determine grouping
-‐ Determine any update operations to be performed
Basic SQL Commands
The basic form of SQL expression is quite simple:
SELECT – FROM – WHERE
The statement begins with SELECT clause, which consists of
the word SELECT, followed by
a list of those fields you want to include.
Next, there is a FROM clause, which consists of the word
FROM, followed by a list of tables
involved in the query
Finally, there is an OPTIONAL WHERE clause, which consists
of the word WHERE, followed
by any criteria that the data must satisfy.
The command ends with a Semicolon (;).
Simple criteria: The criterion following the word WHERE is
called a Simple Criterion. A Simple
Criterion has the form: Field name, Comparison Operator, then
either another field name or a
value
Comparison Operators

= Equal to
< Less than
> Greater than
<= Less than or equal to
>= Greater than or equal to
<> or ! Not equal to.
DeVry University
Corporation.
mechanical,
consent of DeVry

Create a new query by clicking “Query Design”. However, close
the “Show Table” dialog box
without selecting any tables. The Query is shown in Design
View. Using the View option, change to
SQL View as shown below.
DeVry University
Corporation.
mechanical,
consent of DeVry

Enter the following query:
DeVry University
Corporation.

mechanical,
consent of DeVry
Run the query. The result should look like the following:
Save the query as “Lab4_Query5”. Save the database file.
DeVry University

Corporation.
mechanical,
consent of DeVry
Step 6: Query #6
In this query, you will demonstrate your understanding of
queries.
Using the steps described in step 5, create a new query using
SQL View.
Enter the following query:
SELECT Customers.CompanyName, Customers.ContactName,
Orders.EmployeeID,
Orders.OrderDate, Orders.ShippedDate, Orders.ShipVia
FROM Employees INNER JOIN (Customers INNER JOIN
Orders ON Customers.CustomerID =
Orders.CustomerID) ON Employees.EmployeeID =
Orders.EmployeeID;
The results will look like the following, with 830 records

Save the query as “Lab4_Query6”. Save the database file.
When you upload your lab, use the comment area of the
Dropbox to explain what you accomplished in
DeVry University
Corporation.
mechanical,
consent of DeVry
this query.
Step 7: Submit Deliverables

Save your MS Access “Lab4_Start.accdb” file as
“YourName_Lab4 _Finitial.accdb”
Submit the Access file created during this assignment to the
weekly iLab Dropbox located on the
silver tab at the top of this page.
Do not forget to provide your comments from Step 6 in the
comments area of the Dropbox.
(See Syllabus/"Due Dates for Assignments & Exams" for due
dates.
End of Lab 4b
Page 1 of 5
A. Lab # : BSBA BIS245A-4A
B. Lab 4A of 7: Database design based on data requirements and
business rules
focusing on interpreting business rules to determine
relationships.

C. Lab Overview --Scenario/Summary
TCO(s):
1. Given a business situation in which managers require
information
from a database, determine, analyze and classify that
information
so that reports can be designed to meet the requirements.
requirements, create the conceptual model of the database using
a
database modeling tool.
Scenario:
You have been asked to create a database model using MS Visio
Database
Model Diagram Template. The purpose of this lab is to provide
experience
designing, with limited instructions, a simple database based on
a list of
data requirements and associated business rules.
1. create a new Visio file for database design; and
develop
a conceptual model (ERD), including attribute data types and

required field lengths.
D. Deliverables
Step 6 YourNameLab4A.vsd (Visio Diagram)
E. Lab Steps
Preparation
instructions located in the iLab tab in Course Home.
2. Start Visio
a. Open Microsoft Office 2010, Visio application, or
Page 2 of 5
b. if you are using Citrix, click on Microsoft Office 2010
Applications folder to start Visio.
Lab:
Step 1: Identify and create the entities

a. Open a new blank Database Model Diagram. If you need
assitance with this,
refer to the Week 1 Lab Instructions. Be sure that all options are
set consistent
to those used in previous weeks so that you generate your model
in Crows
Foot notation.
b. Save the file as YourName_Lab4A.vsd.
c. Based on the information provided below, create the
necessary entities for the
Catering by Caren database. If you need assistance to create the
entities, refer
to Labs from Weeks 1 and 2.
Catering by Caren
Catering by Caren is an upscale catering company focusing on
full, four-
course gourmet dinners for groups from two to forty.
Owner/chef James
Caren is wonderful in the kitchen, but has become overwhelmed
with the
business side of running his rapidly growing operation. You
have been
hired as his business manager, and you’ve decided to
computerize
information on the engagements.
Chef Caren is excited about this project and has provided you

with the
following information. He doesn’t know databases nearly as
well as he
knows haute cuisine, so the data requirements are not well-
organized,
nor is data in its smallest parts. He has noted whether the menu
items
are appetizers, salads, main courses, or desserts. He has also
provided a
list of the information he keeps on each customer and each
booking.
By talking with Chef Caren, you feel you have enough
information on the
company’s business rules to understand the relationships
between the
data. Chef Caren is particularly concerned that you capture the
exact
requirements for the menu for each engagement. For instance, if
20
people are to be served, he wants to know how many want the
vegetarian main course, the Kosher meals, and so forth.
At this point, you are going to use the following information to
put
together an entity relationship diagram that you will then use
with Chef
Caren to verify that you have accurately captured the
requirements.
Page 3 of 5

Customers
Name
Phone
Address
E-mail Address
Approved for credit or not
Engagements
Date
Time
Location
Menu
Number of Attendees
Special Diet Plates
Assistant Chef Assigned
Employees Assigned
Payment Method (AmEx, Visa, MasterCard, Check, Cash, Bill)
Deposit Amount
Deposit Paid Date
Total Charges
Balance Paid Date
Menu Items
Item Name
Description
Classification (Appetizer, Salad, Main Course, Dessert)
Special Diet Item (Kosher, Vegetarian)
Employees
Name
Position
NOTE: You may find it helpful to consider the business rules in
Step 4
in creating your entities.

Step 2: Identify and create attributes (fields)
NOTE: Because you are creating your diagram in Visio, it will
be easier to
create the attributes prior to the relationships.
a. Refer to the data requirements from Step 1 of this lab. If you
have not already
Page 4 of 5
created the attributes (fields) in your ERD, add them at this
time.
b. Save your file and continue to Step 3.
Step 3: Identify and designate the keys
a. Detemine whether an attribute exists in each table that will
satisfy the
requirements of a primary key. If no appropriate field exists,
create a field for
this purpose.

b. Check the Primary Key property for the field(s) in each table
using the Visio
column properties.
Step 4: Identify the relationships
a. Using the information below on the business rules for
Catering by Caren,
create the relationships between the entities created in Steps 1
and 2.
b. Notice that, where Many-to-Many relationships exist, you
will need to create
associative entities. If you are not sure of the process to create
relationships in
Visio, refer to the Labs for Weeks 1 and 2. You created an
associative entity in
Week 2.
c. For any associative entities created, enter necessary fields.
You may also need
to designate or create a primary key. NOTE: If the relationship
is mandatory
(must have at least one…) you will go to the relationship
Miscellaneous
property and change it from Zero to Many to One to Many.
BUSINESS RULES
Business rules help determine the relationships between data
that
should help you design the relationships between your entities.

1. Each customer can book many engagements over time, but
each
engagement is placed by only one customer.
2. One assistant chef is assigned to each engagement. An
assistant
chef may work many engagements over time, but each
engagement will have only one assistant chef assigned.
3. Each engagement will have many menu items. Each menu
item
may be served at many engagements. When a menu item is
selected, the number of servings required for the event must be
recorded. (Hint: Remember that an associative entity may have
attributes!)
4. Each engagement must have at least one assistant chef
assigned.
There may be many other employees assigned to the
engagement.
Each employee may work many engagements. However, some
employees never work engagements.
5. Only one engagement may be scheduled for any particular
date
and time.
Page 5 of 5

Step 5: Determine and specify the data types
a. Using the information below select the data type for each
attribute (field) in
your diagram, and set the type in the attribute properties. (Refer
to the Week
2 Lab if you are not sure how to do this. Where allowed,
estimate the field
length needed.)
As the data types and field lengths are not included in the data
requirements, you should make a selection based on your
knowledge
of the type of data and approximation of length required. The
Visio
equivalents are shown below
Access Visio
Number Integer
Text Text
Memo LongText
Date/Time DateTime
Currency Currency
Yes/No Binary
AutoNumber Long
Hyperlink No equivalent—use Text
Step 6: Modify the Visio Settings to show the Data type and
field size in the
diagram.
a. Change your Visio settings so that the data type and field size

appear on the
actual diagram. If you are unsure of the steps to do this, refer to
the Week 3
Lab.
b. Be sure to save the final version of your file.
Lab 4A Final Deliverables
a. YourNameLab4A.vsd (Visio Diagram)--from Lab 4A
Submit this file to the Week 4 iLab Dropbox.
END OF LAB
IDEngagement DateEngagement TimeType of menuNumber of
AttendeesAssistant Chef assignedEmployees assignedPayment
methodDeposit amountDeposit paid dateTotal chargesBalance
paid dateIDCustomer NamePhone NumberAddressE-mail
addressApproved credit r notIDEmployee NamePosition
heldIDMenu TypeSpecial dietDescription1AppetizerKocher or
Vegeterian2Main Course3Salad4DessertIDCompany's main
activityDirectors2Four course gourmet dinner set for groups of
two to fortyJames Caren
SELECT DISTINCTROW *
FROM [Customer Engagements];
SELECT DISTINCTROW *
FROM [Menu Items];
TRANSFORM Avg([Customer Engagements].[Payment
method]) AS [AvgOfPayment method]
SELECT [Customer Engagements].[Engagement Date],

[Customer Engagements].[Employees assigned], [Customer
Engagements].[Balance paid date], Avg([Customer
Engagements].[Payment method]) AS [Total Of Payment
method]
FROM [Customer Engagements]
GROUP BY [Customer Engagements].[Engagement Date],
[Customer Engagements].[Employees assigned], [Customer
Engagements].[Balance paid date]
PIVOT [Customer Engagements].[Type of menu];
TRANSFORM Count([Customer Engagements].[Engagement
Date]) AS [CountOfEngagement Date]
SELECT [Customer Engagements].[Deposit paid date],
[Customer Engagements].[Type of menu], [Customer
Engagements].[Deposit amount], Count([Customer
Engagements].[Engagement Date]) AS [Total Of Engagement
Date]
FROM [Customer Engagements]
GROUP BY [Customer Engagements].[Deposit paid date],
[Customer Engagements].[Type of menu], [Customer
Engagements].[Deposit amount]
PIVOT [Customer Engagements].[ID];
Page 1 of 6
A. Lab # : BSBA BIS245A-3
B. Lab 3 of 7: Database Design Using Visio and Based on Data
Requirements
and Business Rules
C. Lab Overview--Scenario/Summary

TCOs:
requirements, create the conceptual model of the database using
a
database modeling tool.
3. Given an existing relational database schema, evaluate and
alter the
database design for efficiency.
4. Given an existing database structure demonstrating efficiency
and
integrity, design the physical tables.
Scenario
You have been asked to create a database model using MS Visio
Database Model
Diagram Template. The purpose of this lab is to provide
experience designing,
with limited instructions, a simple database based on a list of
data requirements
and associated business rules.
You will then complete an MS Access database based on the
model developed in
Visio, creating the necessary tables and relationships.
1. create a new Visio file for database design;
develop a

conceptual model (ERD), including attribute data types and
required field
lengths; and
3. create a new MS Access database based on the ERD.
D. Deliverables
Part A Step
7
YourNameLab3.vsd (Visio Diagram)
Part B Step
3
YourNameLab3.accdb (Access Database)
E. Lab Steps
Page 2 of 6
Preparation
1. If you are using Citrix for MS Visio and/or MS Access,

follow the login
instructions located in the iLab tab in Course Home.
Lab
Part A: Create a Visio ERD from Data Requirements and
Business Rules
Step 1: Open Visio
a. Open Microsoft Office, Visio application or
b. If you are using Citrix, click on Microsoft Office
Applications folder to start
Visio.
Step 2: Identify and create the entities
a. Open a new blank Database Model Diagram. If you need
assitance with this,
refer to the Week 1 Lab Instructions. Be sure that all options are
set
consistent to those used in previous weeks so that you generate
your model
in Crows Foot notation.
b. Save the file as YourName_Lab3.vsd.
c. Based on the information provided below, create the
necessary entities for
the Pages in Time database. If you need assistance to create the

entities,
refer to labs from Weeks 1 and 2.
Pages in Time
Pages in Time is a small bookstore carrying a variety of books.
The
owners have decided to computerize the books available through
the
store so that they can determine more easily what books are on
hand and which books need to be special ordered to meet
customer
needs. Because customers do not always remember the name of
a
desired book, the owners want to be able to look for books by
author
or by type (genre). They also want to be able to find the
publisher’s
information using the system so that they can order books more
easily.
After visiting with the owners, you have gathered the following
information on data requirements and business rules to develop
a
conceptual design (ERD), prepare it for conversion to an Access
database, and then create the actual database.
Page 3 of 6
DATA REQUIREMENTS
You have determined that you will need at least the following

entities
to resolve the relationships that exist in the data.
CUSTOMERS
ID
Name (store data in its smallest parts)
Phone
Address (store data in its smallest parts)
Phone Number
E-mail Address
Preferred Contact Method
ORDERS
Number
Date
Received Date
Customer Contacted (Yes or No)
BOOKS
ISBN Number
Title
Purchase Price
Year Published
Fiction or Nonfiction
Type (Genre)
In stock
AUTHOR
ID
Name (store data in smallest parts!)
Short Biography
PUBLISHER
ID
Name

Address
Phone number
Contact Person
Fax Number
Website
Step 3: Identify and create attributes (fields)
Page 4 of 6
NOTE: Because you are creating your diagram in Visio, it will
be easier to
create the attributes prior to the relationships.
a. Refer to the data requirements from Step 2 of this lab. If you
have not
already created the attributes (fields) in your ERD, add them at
this time.
b. Be sure that you store data in its smallest parts.
c. Save your file, and continue to Step 4.
Step 4: Identify and designate the keys
a. Detemine whether an attribute exists in each table that will
satisfy the
requirements of a primary key. If no appropriate field exists,

create a field for
this purpose.
b. Check the Primary Key property for the field in each table
using the Visio
column properties.
Step 5: Identify the relationships
a. Using the information below on the business rules for Pages
in Time, create
the relationships between the entities created in Step 2.
b. Notice that when Many-to-Many relationships exist, you will
need to create
associative entities. If you are not sure of the process to create
relationships
in Visio, refer to the Labs for Weeks 1 and 2. You created an
associative
entity in Week 2.
c. For any associative entities created, enter necessary fields.
You may also
need to designate or create a primary key.
BUSINESS RULES
Business rules help determine the relationships between data
that
should help you design the relationships between your entities.
1. Each customer can place many orders over time, but each
order is

placed by only one customer.
2. Each order may include many books, and a book may be
included
on many orders.
3. Each book may have multiple authors, and each author may
have
written multiple books.
4. Each book has only one publisher, but a publisher may
publish
many books.
Step 6: Determine and specify the data types
a. Using the information below, select the data type for each
attribute (field) in
your diagram, and set the type in the attribute properties. (Refer
to the Week
Page 5 of 6
2 Lab if you are not sure how to do this. Where allowed,
estimate the field
length needed.)
As the data types and field lengths are not included in the data
requirements, you should make a selection based on your
knowledge
of the type of data and approximation of length required. The

Visio
and Access data type equivalents are shown below:
Access Visio
Number Integer
Text Text
Memo LongText
Date/Time DateTime
Currency Currency
Yes/No Binary
AutoNumber Long
Hyperlink No equivalent--use Text
Step 7: Modify the Visio Settings to show the Data type and
field size in the
diagram.
a. Change your Visio settings so that these appear on the actual
diagram. To do
this, go to the Database ribbon, Display Options. In the Display
Options dialog
box, select the Table tab. You will then change the data types to
Show
Physical. Click the OK button to apply the new setting. They
data types will
then appear in your diagram. Note that you may need to move
the entities so
that they are easily viewed as they are now larger.
b. Be sure to save the final version of your file.

End of Part A
Part B: Create the Access Database from the ERD
Preparation
Open the Visio file created in Part A of this lab, you will
reference this file in Part
B.
Page 6 of 6
Step 1: Start MS Access and Open a New Blank Database.
a. Create a new Blank Database; refer to the Week 2 Lab for
more detailed
instructions.
b. Save the database as YourNameLab3.
c. Note: If you are unsure how to complete any steps in this
iLab, refer to the
previous week's iLabs.
Step 2: Create the Tables
a. Based on the Visio diagram from Part A, create the tables for
your database.
b. Enter the field names and the data type.

c. Designate the primary keys for each table
d. Set the attribute properties as needed for
a. Field length
b. Required
Step 3: Create the relationships
a. Open the database relationships window.
b. Based on the Visio diagram from Part A, create the
relationships for your
database.
c. Be sure to enforce referential integrity for each relationship.
Save your file.
End of Part B
Lab 3 Final Deliverables
a. YourNameLab3.vsd (Visio Diagram)--from Lab 3 Part A
b. YourNameLab3.accdb (Access Database)--from Lab 3 Part B
Submit these files to the Week 3 iLab Dropbox.
END OF LAB

of 11 A. Lab # BSBA BIS245A-5B B.docx

Page 1 of 11 A. Lab # BSBA BIS245A-5B B.docx

Recommended

Recommended

More Related Content

Similar to Page 1 of 11 A. Lab # BSBA BIS245A-5B B.docx

Similar to Page 1 of 11 A. Lab # BSBA BIS245A-5B B.docx (18)

More from joyjonna282

More from joyjonna282 (20)

Recently uploaded

Recently uploaded (20)

Page 1 of 11 A. Lab # BSBA BIS245A-5B B.docx