Project Deliverable 3: Database and Data Warehousing Design This assignment consists of two (2) sections: a design document and a revised project plan. You must submit both sections as separate files for the completion of this assignment. Label each file name according to the section of the assignment it is written for. Additionally, you may create and / or assume all necessary assumptions needed for the completion of this assignment. One of the main functions of any business is to transform data into information. The use of relational databases and data warehousing has gained recognition as a standard for organizations. A quality database design makes the flow of data seamless. The database schema is the foundation of the relational database. The schema defines the tables, fields, relationships, views, indexes, and other elements. The schema should be created by envisioning the business, processes, and workflow of the company. Since your company is an innovative Internet-based company, movement toward data warehousing seems to be one of the most viable options to give your company a competitive advantage; however, these concepts must be explained to the executive board in a manner to garner support.   Section 1: Design Document Write a six to ten (6-10) page design document in which you: Support the need for the use of relational databases and data warehousing. From a management standpoint, it may be important to show the efficiencies that can be gained for executive oversight.  Create a database schema that supports the company’s business and processes. Explain and support the database schema with relevant arguments that support the rationale for the structure. Note: The minimum requirement for the schema should entail the tables, fields, relationships, views, and indexes. Identify and create database tables with appropriate field-naming conventions. Then, identify primary keys and foreign keys, and explain how referential integrity will be achieved. Normalize the database tables to third normal form (3NF).  Identify and create an Entity-Relationship (E-R) Diagram relating the tables of the database schema through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia. Note: The graphically depicted solution is not included in the required page length but must be included in the design document appendix. Explain your rationale behind the design of the E-R Diagram.  Identify and create a Data Flow Diagram (DFD) relating the tables of your database schema through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia. Note: The graphically depicted solution is not included in the required page length but must be included in the design document appendix. Explain the rationale behind the design of your DFD.  Illustrate the flow of data including both inputs and outputs for the use of a data warehouse. The diagram should map data between source systems, operational systems, data w.

1. Project Deliverable 3: Database and Data Warehousing Design
This assignment consists of two (2) sections: a design document
and a revised project plan. You must submit both sections as
separate files for the completion of this assignment. Label each
file name according to the section of the assignment it is written
for. Additionally, you may create and / or assume all necessary
assumptions needed for the completion of this assignment.
One of the main functions of any business is to transform data
into information. The use of relational databases and data
warehousing has gained recognition as a standard for
organizations. A quality database design makes the flow of data
seamless. The database schema is the foundation of the
relational database. The schema defines the tables, fields,
relationships, views, indexes, and other elements. The schema
should be created by envisioning the business, processes, and
workflow of the company. Since your company is an innovative
Internet-based company, movement toward data warehousing
seems to be one of the most viable options to give your
company a competitive advantage; however, these concepts
must be explained to the executive board in a manner to garner
support.
Section 1: Design Document
Write a six to ten (6-10) page design document in which you:
Support the need for the use of relational databases and data
warehousing. From a management standpoint, it may be
important to show the efficiencies that can be gained for
executive oversight.
Create a database schema that supports the company’s business
and processes. Explain and support the database schema with
relevant arguments that support the rationale for the structure.
Note: The minimum requirement for the schema should entail
the tables, fields, relationships, views, and indexes.
Identify and create database tables with appropriate field-
naming conventions. Then, identify primary keys and foreign
keys, and explain how referential integrity will be achieved.

2. Normalize the database tables to third normal form (3NF).
Identify and create an Entity-Relationship (E-R) Diagram
relating the tables of the database schema through the use of
graphical tools in Microsoft Visio or an open source alternative
such as Dia. Note: The graphically depicted solution is not
included in the required page length but must be included in the
design document appendix. Explain your rationale behind the
design of the E-R Diagram.
Identify and create a Data Flow Diagram (DFD) relating the
tables of your database schema through the use of graphical
tools in Microsoft Visio or an open source alternative such as
Dia. Note: The graphically depicted solution is not included in
the required page length but must be included in the design
document appendix. Explain the rationale behind the design of
your DFD.
Illustrate the flow of data including both inputs and outputs for
the use of a data warehouse. The diagram should map data
between source systems, operational systems, data warehouses
and specified data marts. Note: The graphically depicted
solution is not included in the required page length.
Your assignment must follow these formatting requirements:
Be typed, double spaced, using Times New Roman font (size
12), with one-inch margins on all sides; citations and references
must follow APA or school-specific format. Check with your
professor for any additional instructions.
Include a cover page containing the title of the assignment, the
student’s name, the professor’s name, the course title, and the
date. The cover page and the reference page are not included in
the required assignment page length.
Include charts or diagrams created in MS Visio or Dia as an
appendix of the design document. All references to these
diagrams must be included in the body of the design document.
Section 2: Revised Project Plan
Use Microsoft Project to:
Update the project plan (summary and detail) template, from
Project Deliverable 2: Business Requirements, with three to five

3. (3-5) new project tasks each consisting of five to ten (5-10)
subtasks.
The specific course learning outcomes associated with this
assignment are:
Describe the methods and best practices in implementing
process change in IT organizations.
Describe the role and methods of technology-induced process
improvement in organizations.
Use technology and information resources to research issues in
information systems.
Write clearly and concisely about leadership issues and
strategic insight of the Information systems domain using
proper writing mechanics and technical style conventions.
Points: 120
Project Deliverable 3: Database and Data Warehousing Design
Criteria
Unacceptable
Below 70% F
Fair
70-79% C
Proficient
80-89% B
Exemplary
90-100% A
Section 1: Design Document
1a. Support the need for the use of relational databases and data
warehousing.
Weight: 15%
Did not submit or incompletely supported the need for the use
of relational databases and data warehousing.
Partially supported the need for the use of relational databases
and data warehousing.

4. Satisfactorily supported the need for the use of relational
databases and data warehousing.
Thoroughly supported the need for the use of relational
databases and data warehousing.
1b. Create a database schema that supports the company’s
business and processes. Explain and support the database
schema with relevant arguments that support the rationale for
the structure.
Weight: 15%
Did not submit or incompletely created a database schema that
supports the company’s business and processes. Did not submit
or incompletely explained and supported the database schema
with relevant arguments that support the rationale for the
structure.
Partially
created a database schema that supports the company’s business
and processes. Partially explained and supported the database
schema with relevant arguments that support the rationale for
the structure.
Satisfactorily
created a database schema that supports the company’s business
and processes. Satisfactorily explained and supported the
database schema with relevant arguments that support the
rationale for the structure.
Thoroughly
created a database schema that supports the company’s business
and processes. Thoroughly explained and supported the database
schema with relevant arguments that support the rationale for
the structure.
1c. Identify and create database tables with appropriate field-
naming conventions. Then, identify primary keys and foreign
keys, and explain how referential integrity will be achieved.
Normalize the database tables to third normal form (3NF).
Weight: 10%

5. Did not submit or incompletely identified and created database
tables within appropriate field-naming conventions. Did not
submit or incompletely identified primary keys and foreign
keys, and did not submit or incompletely explained how
referential integrity will be achieved. Did not submit or
incompletely normalized the database tables to third normal
form (3NF).
Partially identified and created database tables within
appropriate field-naming conventions. Partially identified
primary keys and foreign keys, and partially explained how
referential integrity will be achieved. Partially normalized the
database tables to third normal form (3NF).
Satisfactorily identified and created database tables within
appropriate field-naming conventions. Satisfactorily identified
primary keys and foreign keys, and satisfactorily explained how
referential integrity will be achieved. Satisfactorily normalized
the database tables to third normal form (3NF).
Thoroughly identified and created database tables within
appropriate field-naming conventions. Thoroughly identified
primary keys and foreign keys, and thoroughly explained how
referential integrity will be achieved. Thoroughly normalized
the database tables to third normal form (3NF).
1d. Identify and create an Entity-Relationship (E-R) Diagram
relating the tables of the database schema through the use of
graphical tools in Microsoft Visio or an open source alternative
such as Dia. Explain the rationale behind the design of your E-R
Diagram.
Weight: 15%
Did not submit or incompletely identified and created an Entity-
Relationship (E-R) Diagram relating the tables of the database
schema through the use of graphical tools in Microsoft Visio or
an open source alternative such as Dia. Did not submit or
incompletely explained the rationale behind the design of your
E-R Diagram.
Partially identified and created an Entity-Relationship (E-R)
Diagram relating the tables of the database schema through the

6. use of graphical tools in Microsoft Visio or an open source
alternative such as Dia. Partially explained the rationale behind
the design of your E-R Diagram.
Satisfactorily identified and created an Entity-Relationship (E-
R) Diagram relating the tables of the database schema through
the use of graphical tools in Microsoft Visio or an open source
alternative such as Dia. Satisfactorily explained the rationale
behind the design of your E-R Diagram.
Thoroughly identified and created an Entity-Relationship (E-R)
Diagram relating the tables of the database schema through the
use of graphical tools in Microsoft Visio or an open source
alternative such as Dia. Thoroughly explained the rationale
behind the design of your E-R Diagram.
1e. Identify and create a Data Flow Diagram (DFD) relating the
tables of the database schema through the use of graphical tools
in Microsoft Visio or an open source alternative such as Dia.
Weight: 15%
Did not submit or incompletely identified and created a Data
Flow Diagram (DFD) relating the tables of the database schema
through the use of graphical tools in Microsoft Visio or an open
source alternative such as Dia.
Partially identified and created a Data Flow Diagram (DFD)
relating the tables of the database schema through the use of
graphical tools in Microsoft Visio or an open source alternative
such as Dia.
Satisfactorily identified and created a Data Flow Diagram
(DFD) relating the tables of the database schema through the
use of graphical tools in Microsoft Visio or an open source
alternative such as Dia.
Thoroughly identified and created a Data Flow Diagram (DFD)
relating the tables of the database schema through the use of
graphical tools in Microsoft Visio or an open source alternative
such as Dia.
1f. Illustrate the flow of data including both inputs and outputs
for the use of a data warehouse. The diagram must map data
between source systems, data warehouses, and specified data

7. marts.
Weight: 15%
Did not submit or incompletely illustrated the flow of data
including both inputs and outputs for the use of a data
warehouse. Did not submit or incompletely mapped data
between source systems, data warehouses, and specified data
marts.
Partially
illustrated the flow of data including both inputs and outputs for
the use of a data warehouse. Partially mapped data between
source systems, data warehouses, and specified data marts.
Satisfactorily
illustrated the flow of data including both inputs and outputs for
the use of a data warehouse. Satisfactorily mapped data between
source systems, data warehouses, and specified data marts.
Thoroughly
illustrated the flow of data including both inputs and outputs for
the use of a data warehouse. Thoroughly mapped data between
source systems, data warehouses, and specified data marts.
Section 2: Revised Project Plan
2. Update the project plan from
Project
Deliverable 2: Business Requirements, with three to five (3-5)
new
project tasks each consisting of five to ten (5-10) subtasks.
Weight: 5%
Did not submit or incompletely updated the project plan from
Project Deliverable 2: Business Requirements, with three to five
(3-5)
new
project tasks each consisting of five to ten (5-10) subtasks.
Partially updated the project plan from

8. Project Deliverable 2: Business Requirements, with three to five
(3-5)
new
project tasks each consisting of five to ten (5-10) subtasks.
Satisfactorily updated the project plan from
Project
Deliverable 2: Business Requirements, with three to five (3-5)
new
project tasks each consisting of five to ten (5-10) subtasks.
Thoroughly updated the project plan from
Project Deliverable 2: Business Requirements, with three to five
(3-5)
new
project tasks each consisting of five to ten (5-10) subtasks.
3. Clarity, writing mechanics, and formatting requirements
Weight: 10%
More than 6 errors present
5-6 errors present
3-4 errors present
0-2 errors present