Click below
link for Answers
BIS 261 Week 1 iLab
BIS 261 Week 1 iLab
BIS-245
Week 1 iLabDevry University
A. Lab # : BSBA BIS245A-1
B. Lab 1 of 7 : Introduction to MS Visio and MS Access
C. Lab Overview--Scenario/Summary
B. Lab 1 of 7 : Introduction to MS Visio and MS Access
C. Lab Overview--Scenario/Summary
TCOs:
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.
2. Given a situation containing entities, business rules, and data requirements, create the conceptual model of the database using a database modeling tool.
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.
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 two conceptual database models using MS Visio Database Model Diagram Template. The purpose of this lab is to have you gain familiarity with the various modeling tools needed to create a conceptual model (entity relationship diagram) of a database. You will create two conceptual models.
You will then open an existing Access database to explore database objects and to experiment with simple data manipulation using filters and sorts and to begin elementary work with relationships.
Upon completing this lab, you will be able to
1. relying on detailed instructions, create a simple conceptual model for a two-table database using MS Visio;
2. use experience gained in creating the first model to construct a similar conceptual model without the instructions; and
3. download an existing Microsoft Access database file. Open the database; find and identify different database objects in this database.
You have been asked to create two conceptual database models using MS Visio Database Model Diagram Template. The purpose of this lab is to have you gain familiarity with the various modeling tools needed to create a conceptual model (entity relationship diagram) of a database. You will create two conceptual models.
You will then open an existing Access database to explore database objects and to experiment with simple data manipulation using filters and sorts and to begin elementary work with relationships.
Upon completing this lab, you will be able to
1. relying on detailed instructions, create a simple conceptual model for a two-table database using MS Visio;
2. use experience gained in creating the first model to construct a similar conceptual model without the instructions; and
3. download an existing Microsoft Access database file. Open the database; find and identify different database objects in this database.
BIS245
Week 2 Lab - Skills Development in Visio
A. Lab # : BSBA BIS245A-2
B. Lab 2 of 7 : Skills
Development in Visio; Creation of MS Access Database
C. Lab Overview--Scenario / Summary:
TCOs:
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.
2. Given
a situation containing entities, business rules, and data 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 conceptual database model using MS Visio Database
Model Diagram Template. The purpose of this lab is to have you gain experience
with the various modeling tools needed to create a conceptual model (entity
relationship diagram) of a database. You will then modify the model for
implementation as a MS Access database. You will create and modify one
conceptual model.
You
will then create a MS Access database based on the model developed in Visio,
creating the necessary tables and relationships.
Upon
completing this lab, you will be able to
1.
relying on detailed instructions, add two entities to the existing conceptual
model (ERD), including attribute data types and required field lengths;
2.
create a new MS Access database file;
3.
using the model from Parts A and B of the lab, and relying on detailed
instructions; create the first two tables in the database;
4. use
the experience gained in creating the first two tables to add the remaining
tables;
5.
using the model from Parts A and B of the lab, and relying on detailed
instructions; create the relationship between the first two tables in the
database; and
6. use
the experience gained in creating the first relationship to create the
remaining relationships between the tables.
BIS245
Week 3 Lab - Visio ERD
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.
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.
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)
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.
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.
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.
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
BIS245
Week 4 Lab - ER Diagram
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.
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 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.
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 6
YourNameLab4A.vsd
(Visio Diagram)
E. Lab
Steps
Preparation
1.
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.
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.
BIS245
Week 5 Lab - ER Diagram and ER Matrix
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.
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.
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.Page 5 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
BIS245
Week 6 iLab Creating Reports
BIS245 Database Essentials for Business with Lab
A. Lab # BSBA BIS245A-6
B. Lab 6 of 7 : Creating Reports
C. Lab Overview – Scenario / Summary:
B. Lab 6 of 7 : Creating Reports
C. Lab Overview – Scenario / Summary:
TCO(s):
7. Given a database application with a completed relational schema, populated
tables, and business reporting requirements, create the necessary reports and
make a business decision.
Scenario: The purpose
of this lab is to create Access Reports. After a report is created, the student
will sort the fields in different ways. Also the Student can also delete fields
in layout view and modify the appearance of the report by applying Themes. In
addition to the report generated by Access, the lab also uses Report Design to
allow users to design their own reports. Upon completing this lab, you should
be able to:
• Create a report and apply a theme for professional appearance of the report.
• Use Report Design to generate your own report.
• Create a report and apply a theme for professional appearance of the report.
• Use Report Design to generate your own report.
D. Deliverables: Upload the
modified Lab6_Start.accdb file that you saved as YourName_Lab6.accdb to the
Week 6 iLab Dropbox.
Part A Step 1: Create a Simple Report – Lab6_Report1
Part A Step 2: Create a report using Report Design – Lab6_Report2
Part A Step 3: Creating Multi-table Reports – Lab6_Report3
Part A Step 4: Adding a Subreport – Lab6_Report4
Part A Step 5: Create Mailing Labels – Lab6_Report5
Part B Step 1: Create a Report – Lab6_Report6
Part B Step 2: Create a Multi-table Report – Lab6_Report7
Part A Step 1: Create a Simple Report – Lab6_Report1
Part A Step 2: Create a report using Report Design – Lab6_Report2
Part A Step 3: Creating Multi-table Reports – Lab6_Report3
Part A Step 4: Adding a Subreport – Lab6_Report4
Part A Step 5: Create Mailing Labels – Lab6_Report5
Part B Step 1: Create a Report – Lab6_Report6
Part B Step 2: Create a Multi-table Report – Lab6_Report7
BIS-245
All 7 Weeks Discussions
w1 dq1 - Databases and Gathering Requirements
w1 dq2
- Choosing a Database
w2 dq1
- Entity Relationship (ER) Modeling
w2 dq2
- Database Table Design
w3 dq1
- Conceptual Database Design
w3 dq2
- Requirements Analysis
w4 dq1
- Creating Queries from Woodcraft Database
w4 dq2
- Creating Queries from Northwind Database
w5 dq1
- Data Normalization
w5 dq2
- Data Validation
w6 dq1
- Data Reporting
w6 dq2
- Presenting Data Effectively
w7 dq1
- Database Navigation
w7 dq2
- Database Security
(TCO 1) Which object would you use to enter, delete, or
modify data?
(TCO
1) Which object would you use to retrieve customers who live in Germany and the
United States?
(TCO
1) To design a report you should do all of the following EXCEPT
(TCO
1) Which of the following is NOT a Report Section?
(TCO BIS-245
Final Exam
1) A
Detail line is used to
(TCO
2) For the following image, which of the following is TRUE?
(TCO
2) A symbol used in ER diagrams for an entity is a
(TCO
3) A property that provides a "user friendly" name to a column in
Datasheet View is a
(TCO
3) Summarized data in an easy-to-read view is known as a
(TCO
3) Which of the following is NOT true of a property?
(TCO
4) Which of the following does NOT describe the following one-to-one
relationship?
(TCO
5) Which form type displays records in a tabular format similar to a Datasheet
view but has more editing options such as adding graphics?
(TCO
5) A calculated control
(TCO
6) Which of the following is a term used to describe the names of controls,
fields, or properties?
(TCO
6) Data aggregates
(TCO
7) When making vertical data comparisons, you should use the following chart.
(TCO
7) Discrete data
(TCO
8) A switchboard is a
(TCO
9) To secure an Access database, all of the following should be done EXCEPT
(TCO
9) All of the following describe a certification authority EXCEPT
(TCO
10) Which of the following file format types removes all VBA code from the
database and prohibits users from making changes to forms and reports?
(TCO
4) The term "cascading" refers to
(TCO
1) Describe three-tier architecture. Explain the functions performed by each
tier.
(TCO
2) Explain business logic and describe how it relates to a relational database
(TCO
4) From first normal form, second normal form, or third normal form, select one
of these forms and explain (1) how that normal form is often violated by
inexperienced database designers and (2) how to correct such a violation of
that normal form
(TCO
4) Explain 1NF, 2NF, and 3NF as related to database design