CIS 499 Database and Data Warehousing Design This assignment consists of two (2) sections: a design document and a revised Gantt chart or project plan. You

CIS 499 Database and Data Warehousing Design This assignment consists of two (2) sections: a design document and a revised Gantt chart or 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.

Large companies have been using the power of business analytics for quite a while now. Your company desires to get in on the action; company executives believe that using advanced data analysis will enable the company to make smarter decisions and improve business performance. Business analytics gives companies the ability to look at past realizations and performance as well as set up new expectations and performance goals. Analytics-as-a-Service is a new delivery model that uses cloud technology to provide business insights without enormous infrastructure enhancements. The executive team has heard great things about analytics and cloud technology but is apprehensive because they are unfamiliar with the look and feel of the technology. The executive team is interested in your recommendations and eagerly awaiting your forward-thinking viewpoint.

Section 1: Design Document

Write a four to six (4-6) page design document in which you:
Support the need for the use of analytics and cloud technology within this company.
Create a workflow diagram to illustrate how analytics and cloud technology could align with the company’s business processes. Note: The graphically depicted solution is not included in the required page length but must be included in the design document appendix.
Create three to five (3-5) screen layouts that illustrate the interface that organizational users will utilize. Note: The graphically depicted solution is not included in the required page length but must be included in the design document appendix.
Give one (1) recommendation for solution providers that could help your company secure a firm advantage by using analytics and cloud technology.
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 3: Database and Data Warehousing Design, 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:
Demonstrate an understanding of existing and emerging information technologies, the functions of IS, and its impact on the organizational operations.
Evaluate an organization through the lens of non-IT senior management in deciding how information systems enable core and supportive business processes as well as those that interface with suppliers and customers.
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. Running head: PROJECT DELIVERABLE 3: DATABASE AND DATA WAREHOUSING
DESIGN
Project Deliverable 3: Database and Data Warehousing Design
Bennie Carter
CIS 499: Information Systems Capstone
Darcel Ford
Monday, February 4, 2019
1
PROJECT DELIVERABLE 3: DATABASE AND DATA WAREHOUSING DESIGN
2
Why a Data Warehouse is needed in the Company
In the contemporary business environment, it is reported that a paltry 0.6% of data
available to each organization is being utilized yet in the same breadth; companies in the US on
averagely lose businesses worth billions of dollars because of using bad data to obtain analyzed
information. Such gives an impression that the company data are not properly stored and
analyzed to accurately guide decision making processes in the company. The kind of investment
companies put towards data gathering, storage, security and processes involved in manipulating
the same data to derive logical meaning from it over and over is enough testimony how data can
remain to be core in influencing the direction a business takes (Manikandan, Lavanya, & Gokila,
2018).
In today’s business space, the culture of doing business heavily depends on data
especially while determining important business forecasts in relation to the situations in
existence. Unfortunately, the data available can only serve to perfect or spoil completely. Data
only remain powerful if it can be used while in the right state, which is a product of data
organization and analysis (Black, Keene, Lamb, & Oglesby, 2018). Archaic storage of data and
running ineffective data analytics only serves better in compounding company data-related
problems. The arrival of data warehouse technology, however, caused a paradigm shift as far as
storing data, analyzing and reporting are concerned together with the speed with which it is
accessed.
Data warehouse basically is the place from which historical and current data are stored.
In an organizational setup, the scope of the data warehouse spans across all departments hence
creating one giant data repository to ease analysis which is normally key to market research,
PROJECT DELIVERABLE 3: DATABASE AND DATA WAREHOUSING DESIGN
3
generating analytical reports and more critical decision support mechanism. A clear contrast
between traditional databases and the data warehouse in terms of the scope of data each handles.
While the former works best with a snapshot of current data, the latter houses a range of data
dating several years back up to the currently available data hence granting in-depth analysis and
reporting.
Best Practices the Company must adhere to
A company before embarking on a process to put in place a data warehouse should at
basic levels align itself to some guiding principles dubbed as best practices. The principles are
normally constructed cleverly to ensure the company benefits maximally from the data
warehouse project while at the same time ensuring areas of conflicts are minimized. Some of
these practices include aligning the project to business objectives and corporate strategy of the
company, building an incremental data warehouse, building in adaptability and have the project
be under the management of IT specialists and business professionals.
A schema that Supports Company’s Business and Processes
Basic requirements of a schema comprise fields, tables, views, relationships, and indexes.
Tables
UserData- Main purpose of the table is to contain information pertaining to each user that
accesses the system. The fields contained include username followed with a password, and
lastname, employee_id, title, and level. Another table is Usermanagement- used to monitor data
contribution that a given user is allocated in the system. The fields contained in this table include
UserID, Original_Level, DateCreated, and the New_level. The next table in the schema is Levelwhich defines levels a user can get in the system. Fields in the table include Level_number and
PROJECT DELIVERABLE 3: DATABASE AND DATA WAREHOUSING DESIGN
4
level_description. Another table worth noting is knowledge which comprises the information the
user feeds into the system for use by other system users. Fields in this table include
knowledge_ID, Created_by, Approved_by, Description, Category_name, and Approved_for.
Knowledge statistics table monitors frequency within which a piece of information
(information piece) is accessed. Fields include KsId, UserID, Date_Accessed. For the table
Media_Details, information such as data related to maps, the knowledge to the files and any
other media related details. The fields include KID, ID, MDID, and media_description. Finally,
categories become the last table to be discussed. The table comprises set information regarding
categories from which each media and knowledge fall into. The fields found in the table include
Category_Name, Category_Id, Category_Description, DateCreated, and CreatedBy.
Relationships
The relationships at the Userdata table are one to many symbolized by 1-* for the tables;
knowledge table, UserManagement table, Media_Statistics table, knowledge_statistics table and
lastly relationship with the media table. On the contrary, the UserData table relationship with the
Level table is many to one symbolized as (*-1). In the knowledge table, there is one to many (1*) relationship to the Knowledge_Statistics table. However, the relationship with the UserData
table is many to one (*-1). The Kowledge_Statistic and UserManagement table relationship is
many to one (*-1) and many to many (*-*) with the media_statistics table. The rest of the
relationships between the tables will be visibly shown on the E-R diagram.
Views
Views are query defined objects. Views sometimes are referred to as virtual tables since
they don’t store data. In this schema, views can play a key role in joining as many related tables
PROJECT DELIVERABLE 3: DATABASE AND DATA WAREHOUSING DESIGN
5
as possible. For example, the tables UserData, Knowledge, UserManagement, Media_Statistics,
Media, and Level can be joined. The use of views helps achieve quite a number of advantages
such as enforcing business rules, maintaining consistency, beef up security through table access
restrictions, introduces simplicity to the design work by creating room to join related tables, and
finally they help a great deal in saving on space.
Indexes
The relevance of index in a database is to speed up data retrievals from a mesh of tables.
A company database contains myriads of tables with multiple rows and columns. An index
initiates the quick search operation and retrieval through selected data form columns. For
example, from the above schema tables, an index syntax to perform specific data retrieval in the
table UserData would be SELECT sir_name FROM User_Data WHERE sir_name LIKE
Chambers.
Explanation and Support
The database schema structure above contains tables with fields, the relationship between
the tables, views, and indexes. Key elements such as constraints, relationships, and data items are
insightfully explained through the use of advanced data model concepts. By understanding the
schema well, one is able to travel through the journey of database design steps (the logical design
and physical design) without much difficulty. Additionally, one is equally able to appreciate the
simplicity of the whole database design process by just borrowing a little from the logical flow of
the schema with its high-level abstraction.
PROJECT DELIVERABLE 3: DATABASE AND DATA WAREHOUSING DESIGN
6
Entity Relational Diagram
The main essence of the entity-relationship diagram (ERD) is to provide a graphical
illustration of the database entities and also to define the relationship between each and every
entities (Heayyoung, Omori, & Ohnishi, 2018). The ERD becomes very crucial when designing
a standard database because of its high-level logical data model. It is a simple paper
representation of the actual complex database which in reality may prove tough to understand as
a result of the high level of abstractions. From the company ERD, one can easily deduce how the
many company database entities are associated with each other.
PROJECT DELIVERABLE 3: DATABASE AND DATA WAREHOUSING DESIGN
7
Data Flow Diagram (DFD)
USER
/EMPLOYEE
DATA
SOURCE
USER
CONTRIBUTION
(Knowledge
addition)
ID
DATA STORE
(User data)
Data
Categorization
ID
(User
data)
DATA STORE
(User data)
(User data)
USER
/EMPLOYEE
INFORMATION
ACCESS
FREQUENCY
USER /EMPLOYEE
DATA
CONTRIBUTION
MONITOR
ACCESS
LEVEL
(Extent a user
can go)
DATA SOURCE
DATA SOURCE
The Data Flow Diagrams further unravels design ambiguities by clearly showing activity flow
from the input point, all accompanying transformations until the output is achieved. DFDs
comprises 4 main components: entities, data stores, processes, and data flow. Symbols used in
DFDs to represent the interaction between the components varies depending on the model being
handled. However, the syntax for the longest time has remained the same. DFDs have gained a
PROJECT DELIVERABLE 3: DATABASE AND DATA WAREHOUSING DESIGN
8
lot of attraction from object-oriented analysts due to their strong emphasis on module-based
design.
Data Flow Diagram in a Data Warehouse (Shows inputs and Outputs)
Data Acquisition
Data Integration and Repository
Warehous
e Admin
ERP System
(Input 1)
Team of
Researchers
(Input 2)
Analytics and Presentation
Raw
Data
Mining
Metadata
Extractio
n
&
Staging
Repository
Summary
Data
Analysis
OUTPU
T
Presentation
Individual User
(Input 3)
Transform
& Load
Reporting
PROJECT DELIVERABLE 3: DATABASE AND DATA WAREHOUSING DESIGN
9
References
Black, C. M., Keene, C. T., Lamb, R., & Oglesby, B. T. (2018). U.S. Patent No. 9,934,263.
Washington, DC: U.S. Patent and Trademark Office.
Heayyoung, J., Omori, T., & Ohnishi, A. (2018, August). Ripple Effect Analysis Method of Data
Flow Diagrams in Modifying Data Flow Requirements. In Joint Conference on
Knowledge-Based Software Engineering (pp. 1-11). Springer, Cham.
Manikandan, S., Raju, K., Lavanya, R., & Gokila, R. G. (2018). Web-Enabled Data Warehouse
Answer With Application.
Rudnicki, R., Cox, A. P., Donohue, B., & Jensen, M. (2018, May). Towards a methodology for
lossless data exchange between NoSQL data structures. In-Ground/Air Multisensor
Interoperability, Integration, and Networking for Persistent ISR IX (Vol. 10635, p.
106350R). International Society for Optics and Photonics.
Cr
ea
te
a
E
nt
E
nt
T
o
C
Tell
hi
s
E
nt
BUSINESS REQUIREMENTS
DGT Data Analytica
Project Start Date:
0
Project Lead
Milestone Marker:
Milestone Description
2/9/2019
Column1
1
February
Progress
Start
No. Days
50%
2/9/2019
5
100%
2/12/2019
4
50%
2/14/2019
10
Key Stakeholders
Identification 1
Meeting 1
Meeting 2
Stakeholders
interest analysis
2/23/2019
1
10%
2/22/2019
6
60%
2/26/2019
13
RESTING 5
Stakeholders
Requirements
Individual
Interviews
Focus Groups
Building
Prototypes
50%
3/9/2019
9
33%
3/16/2019
11
RESTING
RESTING
Requirements
Categorization
Functional
Requirements 1
Operation
Requirements 2
Technical
Requirements 3
Transitional
Requirements 4
3/25/2019
4
3/27/2019
14
NEW PLANNING TO BE DONE TO TAKE CARE OF THE REMAING PERIOD
Task 5
Requirements
Harmonization
Conflict
resolution 1
Impact Change
Analysis 2
Requirements
Prioritization 3
This is an empty row
T
hi
March
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
1
2
3
4
5
S
S
M
T
W
T
F
S
S
M
T
W
T
F
S
S
M
T
W
T
F
S
S
M
T
W
T
F
S
S
M
T
W
T
F
S
S
M
T
W
T
F
S
S
M
T
W
T
F
S
S
M
T
W
T
F

Purchase answer to see full
attachment