This document provides instructions for an assignment to design a normalized database based on a business scenario. Students are asked to:
1) Create an ERD based on the provided business scenario of a clothing retail company.
2) Complete a normalization table to normalize the database design by applying three normal forms - 1st, 2nd, and 3rd normal form.
3) Identify sensible entity names for each group of normalized fields which will become database tables.
The goal is for students to analyze the business data needs, design logical database tables, and normalize the design to eliminate data anomalies and ensure each table serves a clear purpose.
HMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptx
AssessmentStudents should demonstrate that they can distinguish.docx
1. Assessment:
Students should demonstrate that they can distinguish the
relevant points that form a logically coherent argument. They
should also be able to construct criticisms which effectively
undermine, through the use of appropriate counter-examples,
some premise of that argument.
Your assignment is to select any ONE of the following four
articles found in the last chapter of our textbook, Competing
Visions:
Frivolity of Evil
How--and How Not--to Love Mankind
Ibsen and His Discontents
What is Poverty?
NOTE: THIS IS NOT A RESEARCH PAPER, SO DO NOT USE
ANY OUTSIDE SOURCES. This assignment is designed to test
your ability (after several weeks of reading difficult primary
sources in philosophy) to comprehend, explain, analyze, and
evaluate a philosophic essay of college-level difficulty. This is
all about YOU wrestling with a difficult text and ascertaining
its meaning in addition to articulating and defending your own
position on the issues discussed in your chosen Dalrymple
article. It is for this reason that the use of any sources other
than your Dalrymple article and our textbook will result in an
automatic 50 point deduction. The use of outside sources
without proper attribution constitutes plagiarism and will earn
you a ZERO for this assignment with no chance to make it up.
FOR THE ARTICLE YOU CHOOSE TO WRITE ON, you will
type a 1000-1500 word response in which you address EACH of
the following points IN YOUR OWN WORDS: 1) What is the
author's main argument? 2) How does he support his main
argument (evidence, ancillary arguments, etc.)? 3) Do you agree
or disagree with him? 4) Why or why not? 5) Apply the insights
of at least two of the readings we have studied in this course (in
chapters 1-10) to your analysis. Make sure to explain how the
2. philosophers' insights are relevant to the topic you are
discussing.
A WORD OF WARNING: These articles are rather long and
complex. The author likes to make extensive use of his rather
copious vocabulary, so I strongly urge you to
have dictionary.com handy as you work your way through your
chosen article. The purpose of this essay assignment is for you
to demonstrate your ability to discuss, analyze, and
evaluate complex philosophic arguments. I am confident that
the reading assignments, tests, and discussion boards will have
prepared you for this final, and no doubt challenging, essay
assignment.
DBM/380 v14
Create a Database
DBM/380 v14
Page 2 of 2Create a Database
The following assignment is based on the business scenario for
which you created both an entity-relationship diagram and a
normalized database design in Week 2.
For this assignment, you will create multiple related tables that
match your normalized database design. In other words, you
will implement a physical design (an actual, usable database)
based on a logical design.
Refer to the linked W3Schools.com articles “SQL CREATE
TABLE Statement,” “SQL PRIMARY KEY Constraint,” “SQL
FOREIGN KEY Constraint,” and “SQL INSERT INTO
Statement” for help in completing this assignment.
Note: In the industry, even the most carefully thought out
database designs can contain mistakes. Feel free to correct in
your tables any mistakes you notice in your normalized database
design. Also, note that in Microsoft® Access®, you follow the
steps below to launch the SQL editor:
Figure 1. To create a SQL query in Microsoft® Access®, begin
3. by clicking the CREATE tab.
To Complete This Assignment:
1. Use the CREATE TABLE statement to create each table in
your design. Note that a table in a RDMS corresponds to an
entity in an entity-relationship diagram. Recommended tables
for this assignment are CUSTOMER, ORDER,
ORDER_DETAIL, PRODUCT, EMPLOYEE, and STORE.
2. As part of each CREATE TABLE statement, define all of the
columns, or fields, that you want each particular table to
contain. Give them short, meaningful names and include
constraints; that is, describe what type of data each column
(field) is allowed to hold and any other constraints, such as
size, range, or uniqueness.
3. Note that any field you marked as a unique identifier in your
normalized database design is a key field. Key fields must be
described as both UNIQUE and NOT NULL, which means a
value must exist for each record and that value must be unique
across all records.
4. After you have created all six tables, including relationships
between the tables as appropriate (matching the primary key in
one table to a foreign key in another table), use the INSERT
INTO statement to insert 10 records into each of your tables.
You will need to make up the data you insert into your tables.
For example, to insert one record into the CUSTOMER table,
you will need to invent a customer number, a customer name,
and so on—one value for each of the fields you defined for the
CUSTOMER table—to insert into the table.
5. To ensure that your INSERT INTO statements succeeded in
populating your tables, use the SELECT statement described in
Ch. 7, “Introduction to Structured Query Language,” in
Database Systems: Design, Implementation, and Management.to
retrieve the records you inserted. For example, to see all 10
records you inserted into the CUSTOMER table, you might
apply the following SQL statement: SELECT * FROM
CUSTOMER;
After you have created all six tables and populated ten records
5. and customer service coordinators, shipping and receiving
personnel, and facilities maintenance personnel. All locations
stock a full complement of Brewton products for delivery to
purchasing customers. In addition to these functions,
headquarters, located in Eugene, also provides human resources,
purchasing analysts, sales and marketing personnel,
accountants, systems personnel, and operations personnel.
Mark Brewton, the company’s founder, wants to implement a
relational database management system (RDBMS) that would
support his long-term vision in implementing comprehensive
Enterprise Resource Planning (ERP) application to support the
business now and in the future. He believes the business has
grown to the point that such a system will streamline business
processes, help control business expenditures, and better
manage inventory levels, which presently do not seem to reflect
accurate numbers for each distribution center. The new system
will replace almost all of the computer applications currently in
use in the company.The Current System Environment
Users in the business functions of the organization use
standalone software packages, each with its own database. The
standalone software packages include a purchasing system,
accounting and payroll applications, and a personnel-tracking
system used by Human Resources. Because these applications
do not share files, there are frequently situations in which
employee and customer data do not match. When this happens,
research must be conducted—and data updated in multiple
places--to make the data consistent across all the standalone
systems. The IT organization runs special programs developed
to cross-compare the information and report mismatches among
data files, which are then updated to reflect the correct
information. The company currently does not have a disaster
recovery plan or a business continuity plan to be followed in the
event of a contingency situation, such as flooding or an
earthquake, and management feels this situation should be
addressed. The company needs to back up its databases to
prevent data loss in the case of a disaster or other emergency.
6. Sales Department and Order Processing Form
Below is an example of the order processing form that needs to
be entered into the sales system. It currently resides in a
spreadsheet and the company is hoping to migrate this system to
sales-specific software with an RDBMS backend.Order Form
Order number: 1234
Order Date: 5/12/18
Customer number 9876
Customer name: John Doe
Customer address: 456 Bishop Street Honolulu, Hawaii 96813
Tel: (808) 8650990
Sales agent: Lloyd JohnsonSales agent number: S99
Product No.
Description
Quantity
Unit Price
8. on.
ii. In the UNF column, designate any field names that seem to
uniquely identify a person, place, or thing (noun) by typing an
asterisk next to that field name. These are your potential keys.
ID numbers (such as student IDs, order IDs, and social security
numbers) that are unique to a specific individual, transaction, or
other noun make good keys.
· For example, field names that can hold the same value in
different situations (such as “John Smith” or “freshman”) are
not unique and therefore not suitable for keys.
iii. Also in the UNF column, designate any field names that
seem to represent repeating values. Use a closing parenthesis
“)” to designate repeating values.
· For example, students typically take many classes, so in an
educational scenario where “student ID” is a key, “class name”
is an example of a repeating value. Because one customer can
place many orders, in a business scenario where “customer ID”
is a key, “order” is an example of a repeating value.
iv. Also in the UNF column, for any group of repeating values
you have identified (the values you marked with a parenthesis),
identify the key, or unique identifier, for that group of repeating
values. Type an asterisk next to the key associated with each
group of repeating values.
· For example, in an educational setting that has repeating
values of “class name,” “class ID,” and “class instructor,”
“class ID” would be a suitable unique identifier/key. In a
business scenario that has repeating values of “order,” “order
ID” would be a suitable unique identifier/key.
b. Apply the first normal form rule. 1NF states that each group
of related field names should have a unique identifier (primary
key), and each field name should represent one and only one
value and contain no repeating groups. The result of applying
1NF to the field names in the UNF column will be a grouping of
9. related fields and a repetition of one or more keys.
· For example, you may find you will move all of the fields
designated with a parenthesis in the UNF column to the 1NF
column and then repeat the key in both columns. The key you
repeat will be considered the primary key in the UNF column
and the foreign key in the 1NF column. In an educational
scenario, you might retain the primary key “class ID” in the
UNF column; move all of the fields marked with a parenthesis
that have to do with classes to the 1NF column; and repeat the
“class ID” field in the 1NF column. This repetition allows you
to “match” the value of a primary key to the value of a foreign
key and relate the eventual data groups/entities/tables.
c. Apply the second normal form rule. 2NF states that any non-
key field must be dependent on the entire primary key.
Conceptually, this means that any non-key field must be able to
be located uniquely, based on concatenated or compound keys if
necessary. The result of applying 2NF to the field names in the
1NF column is typically groups split apart into smaller groups
with additional (and repeated) keys.
d. Identify sensible entity names for each group of fields. The
result of applying this last step to the groups of related field
names in the 3NF column is one entity name listed in the Entity
Name field for each group.
· For example, if the 3NF column contains groups of fields
related to customers, orders, and sales reps, sensible entity
names may be Customer, Order, and Sales Representative,
respectively. If the 3NF column contains groups of fields
related to students, classes, and teachers, sensible entity names
might be Student, Class, and Teacher. Because each entity will
eventually be implemented as a relational table, take a moment
at this point to double-check that each group in the 3NF form
that corresponds to an entity name (that is, each eventual table)
contains one primary key. If tables are related, they must have a
10. second foreign key that matches the primary key of the table(s)
to which they relate
Brewton Enterprises, Inc. Order Form
Order number: 1234
Order Date: 5/12/18
Customer number: 9876
Customer name: John Doe
Customer address: 456 Bishop Street Honolulu, Hawaii 96813
Tel: (808) 8650990
Sales agent: Lloyd Johnson
Sales agent number: S99
Product No.
Description
Quantity
Unit Price
Normalization of Brewton Enterprises, Inc. Order Form
(Brewton Business Scenario)
UNF
1NF
