Project Deliverable 3: Database and Data Warehousing Design Due Week 5 and worth 110 points 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. The use of specific software has been suggested however equivalents including but not limited to OpenOffice, Dia, and Open Project are also permitted. If equivalent tools are used, files must be saved and submitted for grading using extensions that are readable by their equivalent Microsoft Windows edition. Assignment submissions that fail to follow this request may result in a reduced grade. One of the main functions of any business is to be able to use data to leverage a strategic competitive advantage. This feat hinges upon a company’s ability to transform data into quality information. The use of relational databases is a necessity for contemporary organizations; however, data warehousing has become a strategic priority due to the enormous amounts of data that must be analyzed along with the varying sources from which data comes. Since you are now the CIO of a data-collection company which gathers data by using Web analytics and operational systems, you must design a solution overview that incorporates data warehousing. The executive team needs to be clear about what data warehousing can provide the company. Section 1: Design Document Write a four to six (4-6) page design document in which you: Support the need for data warehousing within your company and elaborate on the best practices that the company will adhere to. Create a 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. Create an Entity-Relationship (E-R) Diagram 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 your rationale behind the design of your E-R Diagram. 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. 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 .

1. Project Deliverable 3: Database and Data Warehousing Design
Due Week 5 and worth 110 points
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.
The use of specific software has been suggested however
equivalents including but not limited to OpenOffice, Dia, and
Open Project are also permitted. If equivalent tools are used,
files must be saved and submitted for grading using extensions
that are readable by their equivalent Microsoft Windows
edition. Assignment submissions that fail to follow this request
may result in a reduced grade.
One of the main functions of any business is to be able to use
data to leverage a strategic competitive advantage. This feat
hinges upon a company’s ability to transform data into quality
information. The use of relational databases is a necessity for
contemporary organizations; however, data warehousing has
become a strategic priority due to the enormous amounts of data
that must be analyzed along with the varying sources from

2. which data comes. Since you are now the CIO of a data-
collection company which gathers data by using Web analytics
and operational systems, you must design a solution overview
that incorporates data warehousing. The executive team needs to
be clear about what data warehousing can provide the company.
Section 1: Design Document
Write a four to six (4-6) page design document in which you:
Support the need for data warehousing within your company and
elaborate on the best practices that the company will adhere to.
Create a 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.
Create an Entity-Relationship (E-R) Diagram 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 your rationale behind the design of
your E-R Diagram.
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.
Illustrate the flow of data including both inputs and outputs for

3. the use of a data warehouse. The diagram must map data
between source systems, data warehouses and specified data
marts. The diagram should map data between source systems,
data warehouses, and specified data marts.
Note:
The graphically depicted solution is not included in the
required page length.
Section 1 of 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 fromProject Deliverable 2: Business
Requirements
,
with three to five (3-5)
new
project tasks each consisting of five to ten (5-10) sub-tasks.
The specific course learning outcomes associated with this
assignment are:
Summarize how information systems represent a key source of
competitive advantage for organizations.
Develop information systems-related activities to maximize the

4. business value within and outside the organization.
Use technology and information resources to research issues in
information systems.
Write clearly and concisely about strategic issues and practices
in the information systems domain using proper writing
mechanics and technical style conventions.
Grading for this assignment will be based on answer quality,
logic / organization of the paper, and language and writing
skills, using the following rubric.
Points: 110
Project Deliverable 3: Database and Data Warehousing Design
Criteria
Unacceptable
Below 60% F
Meets Minimum Expectations
60-69% D
Fair
70-79% C
Proficient
80-89% B
Exemplary
90-100% A
Section 1: Project Introduction
1a. Support the need for data warehousing within your company
and elaborate on the best practices that the company will adhere
to.
Weight: 20%
Did not submit or incompletely supported the need for data
warehousing within your company; did not submit or
incompletely elaborated on the best practices that the company

5. will adhere to.
Insufficiently supported the need for data warehousing within
your company; insufficiently elaborated on the best practices
that the company will adhere to.
Partially supported the need for data warehousing within your
company; partially elaborated on the best practices that the
company will adhere to.
Satisfactorily supported the need for data warehousing within
your company; satisfactorily elaborated on the best practices
that the company will adhere to.
Thoroughly supported the need for data warehousing within
your company; thoroughly elaborated on the best practices that
the company will adhere to.
1b. Create a 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: 20%
Did not submit or incompletely created a 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.
Insufficiently created a schema that supports the company’s
business and processes. Insufficiently explained and supported
the database schema with relevant arguments that support the
rationale for the structure.
Partially
created a 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 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

6. created a 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. Create an Entity-Relationship (E-R) Diagram relating the
tables of your database schema through the use of graphical
tools in Microsoft Visio or an open source alternative such as
Dia. Explain your rationale behind the design of your E-R
Diagram.
Weight: 15%
Did not submit or incompletely created an Entity-Relationship
(E-R) Diagram relating the tables of your 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 your rationale behind the design of your E-R
Diagram.
Insufficiently created an Entity-Relationship (E-R) Diagram
relating the tables of your database schema through the use of
graphical tools in Microsoft Visio or an open source alternative
such as Dia. Insufficiently explained your rationale behind the
design of your E-R Diagram.
Partially created an Entity-Relationship (E-R) Diagram relating
the tables of your database schema through the use of graphical
tools in Microsoft Visio or an open source alternative such as
Dia. Partially explained your rationale behind the design of
your E-R Diagram.
Satisfactorily
created an Entity-Relationship (E-R) Diagram relating the tables
of your database schema through the use of graphical tools in
Microsoft Visio or an open source alternative such as Dia.
Satisfactorily explained your rationale behind the design of
your E-R Diagram.
Thoroughly
created an Entity-Relationship (E-R) Diagram relating the tables
of your database schema through the use of graphical tools in
Microsoft Visio or an open source alternative such as Dia.

7. Thoroughly explained your rationale behind the design of your
E-R Diagram.
1d. 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.
Weight: 15%
Did not submit or incompletely created 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.
Insufficiently created 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.
Partially
created 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.
Satisfactorily
created 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.
Thoroughly
created 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.
1e. 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
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.

8. Insufficiently illustrated the flow of data including both inputs
and outputs for the use of a data warehouse. Insufficiently
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 fromProjectDeliverable 2: Business
Requirements, with three to five (3-5)
new
project tasks each consisting of five to ten (5-10) sub-tasks.
Weight: 5%
Did not submit or incompletely updated the project plan
fromProject Deliverable 2: Business Requirements, with three to
five (3-5)
new
project tasks each consisting of five to ten (5-10) sub-tasks.
Insufficiently updated the project plan from ProjectDeliverable
2: Business Requirements, with three to five (3-5)
new
project tasks each consisting of five to ten (5-10) sub-tasks.
Partially updated the project plan fromProject Deliverable 2:
Business Requirements, with three to five (3-5)
new
project tasks each consisting of five to ten (5-10) sub-tasks.
Satisfactorily updated the project plan fromProjectDeliverable

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