Project Deliverable 3

profileJOVANNI
Section1_DesignDocument.docx

Project Deliverable 3: Database and Data Warehousing Design

DATABASE AND DATA WAREHOUSING

A data warehouse is simply defined as a relational database which is planned purposely for request an examination and not for the processes of transactions. It is known of containing data of the past that is gotten from transaction data although supplementary bases can be used to get the data. Additionally, the environment of the data warehouse also includes extracting, transporting, transforming and ETL solution loading, and an online engine of processing, tools used in analyzing clients, among many more applications which are used in managing the whole process of gathering and delivering data to the user in the business (Chevalier, et al., 2016).

A relational database makes it easier to compare information since data is columnar arranged. The relational database model takes the benefit of this standardization in building absolutely different tables out of the statistics that are required from the initial tables. This is to mean that, this model uses the connection of analogous data in increasing the rapidity and the flexibility of the catalog. A typical large database like the one used by the big websites such as Amazon comprises of very many tables which are used together in rapidly finding the precise data which is required at any specified time. Relational databases are produced by a distinct computer language, SQL, which is the typical interoperability (Santos, & Costa, 2016).

Intel enterprises (IE) Collects very huge amount of data from their internet business and therefore there is a need for analyzing this data. All the individuals who visit this page get huge data amounts. The major task that faces this company is the transformation of the data available into information. One of the best methods that can be used by this institution is through the use of relational databases and warehousing. These methods are very essential when it comes to all the business that are looking at remaining competitive in the market environment they work in. relational databases have been known as the most effective and most widely accepted database models use by many businesses and executives in the business environment today and it composes of tables that are connected logically showing the relationships of business data.

Enterprise data is multidimensional and which exists internally or on external systems. Data analysis across different systems by location, times and channel is also very important So as to be able to store and organize data in a single system. This helps because it cuts down the time and the long process which has for a long time been used while generating processes. This involves different steps which strips and extracts data from one source then sorting it and merging the data. Apart from acting as a reliable data storage platform, data warehousing is fully integrated, it time variant, it is not volatile, and it is subject oriented. This is very useful since the businesses can be able to view their organization fully. Additionally, it empowers clients to effectively sort and information storage that can later be interrogated and detached to extricate explicit statistics for information, they are easier to widen and are not reliant on the state of the organization physically. After the principal database construction, extra information class might be encompassed minus every single current application being attuned. Through using relational databases and creating a database management system for a data warehouse, an enterprise raises operational efficiency as well as how the customers interact with the business.

Increasing operational efficiency

The operational efficiency of this enterprise will be increased when the plan the company has of using internet data for enterprise resource planning (ERP) is completed. Many organizations see the ERP system as one of the major parts of the organization quality. Various researches have indicated that when an ERP system is successfully implemented in a company using the data warehouse, there is a very big reduction of the cost that incurred in shipping, production, labor, as well as many maintenance costs of the IT department. The efficiency of the company increases and there is a better competitive edge when dealing with strategic initiatives as well as the response to the clients. It also now becomes very easy to look at the key performance indicators (KPIs) which are the measurements that are used in tracking performances against the objectives that have been set by the business.

In business, KIPs are very essential since they normally have ranges or a target which makes it easier to know if the company is improving or I the company is deteriorating in terms of the performances of the major activities of the business. They are however different depending on the type of businesses. ERP systems have many advantages to businesses. Some of the major importance of these systems includes

· Product profitability- there increased profits to the business since it becomes easier to analyze data from the data warehouse. By measuring the performance, it tells the company about the capacity the organization can make profits and the amount that is left over from all the costs and the expenses comparative to making returns. It is possible to indicate if the company is doing well or not which makes appropriate actions to be made so as to increase productivity.

· Using ERP, managing risks and compliance makes it easier to come up with a single solution for things such as policies, procedures, as well as the key indicators of risks. This will help mitigate risks which will, in turn, reduce the costs that are related to compliance (Jha, et al., 2017).

· The balanced scorecard is a strategic planning and management system that allows giving allot of credit to the data warehouse. This is very useful in measuring the performance of the company against the goals and the objectives the company has set. Executives, therefore, get an easier time in aligning the activities of the business to the vision of the company and the strategy of the company in general.

· Another very important aspect is global sourcing. This helps capture the value from field proficiency, cross-industry paramount practices, cutting edge technology, as well as processes that are if very high quality.

· A company can benefit from logistics through helping it in achieving faster and transformation that is sustainably focusing on achieving outcomes that will impact the organization’s operation rather than driving value in a silo-like business segment.

Customer interaction

With ERP, executives, managers, and employees easily share standardized information through all departments in the correct time. This allows planning of the issues that are related to customer service be done time before this becomes a problem for the company. Also, using the ERP system, sales analysis becomes smooth. One is able to analyze the product's sales by territory, workers, products and the types of customers. God insight becomes easy so that one can improve the business process in different areas such as;

1. Cross-selling- this helps one to be able to advise the clients on the products or services which are closely related to what they are looking for. This will ensure that all customers get products and services and they do not walk out empty handle. This is very essential and has been known to increase the returns of business and a very big margin.

2. Segmentation- segmentation ensures that every group of the population get their needs addressed.

3. Forecasting of the sales- projecting future sales ensures that business is able to plan and order enough stocks. By this, they will not overstock nor under stock. The business will, therefore, maximize profits and reduce losses.

4. Customer profitability- here, one will be able to determine all the activities, the costs, and the profits which are associated with serving a particular type of customers. This will, therefore, improve the services offered to the clients which will, in turn, boost the customer's loyalty and in turn increase the profits in the long run. Without necessary techniques and tools, it very difficult to build customer loyalty, but with them, it becomes easier and enjoys creating a good and strong customer base.

A database schema is an established formula termed as integrity constraints that are enacted on a database. The integrities are used in ensuring compatibility between the different parts of a schema. Every constraint is expressible in similar semantic. A database can be reflected as a configuration in recognition of the database language. It is the knowledge of the administrator which helps a database schema to specify possible applications or those that are of concern to the consumers.

A schema will define the structure of the table. For instance, it will;

· Give the location of the office, the phone number, address and state

· Give the name of the customer, their address, code, city, email, etc.

· It will identify the order ID, description, the location among other things,

· The details of the employees such as the first and the last name, ID no, etc.

· The payment method (cash or card, amount, card Id) will be identified

· The product details such as the type, name, quality, and price

· Order details such as the order ID attributes among others

Running Head: DATABASE AND DATA WAREHOUSING DESIGN 1

DATABASE AND DATA WAREHOUSING 2

OFFICES

EMPLOYEE

CUSTOMER

PAYMENT

ORDER

ORDER_

DETAIL

PRODUCT

PRODUCT

SALE

PROUCT_LINE

OFFICE_ID

Emp_Num

Cust_ID

Cust_ID

Order ID

Order_ID

Product_ID

Product_ID

Product Line

CITY

FirstName

Customer

First_name

Check

Number

Created

Attribute_

Name

Product_Name

Order

TextDescripiton

Phone_Number

LastName

Last_name

Payment

Date

Customer

Product_ID

Product

Time

Count

HTMLDescription

Address

Extension

Phone

Amount

Total

Quantity

Ordered

Quantity

Price

Image

State

Email

Address

Summary

PriceEach

Price

Discount

Country

Office_ID

City

Opinion

OrderLine

Number

Condition

Optimal

LockFiled

PostalCode

ReportTo

State

Cust_ID

Product

Version

GoRecord

Territory

JobTitle

Postal_code

GoRecord

Country

Emp_Num

RDBMS are proficient of applying referential reliability done by either erasing the foreign key rows to maintaining the integrity or to return a fault or not executing the delete task. The technique used here may relay on the referential integrity constraint which is known as a data dictionary (Kumar, & Azad, 2017).

In 3NF, it requires that all columns reference in referenced data which does not depend on the primary key should be removed. 3NF is there defined as a data principle which allows one to be able to organize the table cleanly by building upon the database normalization principles that are provided by 1NF and 2NF (Kumar, & Azad, 2017).

Fig 1. ER diagram

Fig 2. ER diagram

In software engineering, an entity ER model is a model of data that describes a database in an intellectual mode. In the instance of the relational database, that is used in storing data in the tables. The tables that are formed in planning these entities, as well as relations, are known as entity relationships diagrams (ERDs).

The major objective is developing a simple system that will be used in managing the purchase orders of customers. To start with, one must be able to identify the business entities that are involved and their relationships. Doing this, it starts by drawing an ER diagram. ER modeling is a data displaying system that is used in software engineering for the production of an abstract data model of statistics structure. The tables that are made by means of this model of ER system are identified as ERDs. ERDs are used in illustrating the rational organization of databases. Entity relationship model was founded by DR Peter Chen.

The data flow diagram is used in showing the relationship between different components in a system. This is a very crucial system for forming a great level system detail by displaying the transformation of data to productivity outcomes through a categorization of useful changes. There are four main constituents in the data flow diagram. It includes entities, processes, and data stores as well as data flows. There are simple and easy to comprehend symbols used in depicting the interaction of these components. This is the method of choice when it comes to transmission of statistics through a structure. The main reason is that; they are easier to comprehend both by official and non-official audiences, they offer high-level coordination synopsis, which is comprehensive with borders and networks to the other structures, and lastly, it provides a thorough illustration of system mechanisms.

In Quantitative data, the data will become available in an online database, made accessible through a graphical user interface with flow diagram outputs in the improvement of the usability. This means that it becomes possible for users to enter any specific god or process and combining this with a starting and ending point for the previous and successive process, obtaining energy and resource flow within the boundaries. A data mart is a representative of a project that brings to the conclusion rather than being an incredible enormous responsibility. A data warehouse is therefore formed of the combination of the entirely data marts. The data mart is possibly supported by and builds by one part of the corporate and a data mart is frequently structured about a solitary business method. Every data mart is imposed with some very specific design requirement. Without imitated proportions and kowtowed evidence, data mart becomes useless.

References

Alotaibi, Y., & Ramadan, B. (2017). A Novel Normalization Forms for Relational Database Design throughout Matching Related Data Attribute. International Journal of Engineering and Manufacturing7(5), 65.

Chevalier, M., El Malki, M., Kopliku, A., Teste, O., & Tournier, R. (2016). Document-oriented models for data warehouses.

Jha, S., Jha, M., O’Brien, L., & Wells, M. (2017, December). Supporting Decision Making with Big Data: Integrating Legacy Systems and Data.

Kumar, K., & Azad, S. K. (2017). Relational Database Normalization under Tabular Approach: A Design Methodology. International Journal of Advanced Research in Computer Science8(5).

Kumar, K., & Azad, S. K. (2017, October). Database normalization design pattern. In 2017 4th IEEE Uttar Pradesh Section International Conference on Electrical, Computer and Electronics (UPCON) (pp. 318-322). IEEE.

Santos, M. Y., & Costa, C. (2016, June). Data models in NoSQL databases for big data contexts. In International Conference on Data Mining and Big Data (pp. 475-485). Springer, Cham.

PRODUCTSALEORDERPRODUCTCUSTOMERSORDER-DETAILSPAYMENTPRODUCT_LINEOFFICESEMPLOYEESProduct_IDFKOrderCountOrder_IDPKCreatedCustomerProduct_IDPKProduct_NameProductLineQuantityPriceConditionProductVendersPriceDiscountOptimisticLockFieldGCRecordTotalSummeryOptimisticLockFieldGCRecordCust_IDPKCustomerFirst_NameCustomerLast_NamePhoneAddressCityStatePosta_codeCountryOrder_IDFKProduct_IDFKQuantityOrderedPriceEachOrderLineNumberCust_IDPKCheckNumberPaymentDateAmountProductLinePKTextDescriptionHTMLDescriptionImageOFFICE_IDPKCityPhone_numberAddressStateCountryPostalCodeTerritoryEmp_NumPKFirstNameLastNameExtentionEmailOffice_IDFKReportToJobTitleEmp_numFKCust_IDFKattribute namePK

PRODUCTSALE ORDER PRODUCT CUSTOMERS ORDER-DETAILS PAYMENT PRODUCT_LINE OFFICES EMPLOYEES Product_ID int FK PK Order int FK PK Count int FK PK Order_ID int FK PK Created int FK PK Customer int FK PK Product_ID int FK PK Product_Name int FK PK ProductLine int FK PK Quantity int FK PK Price int FK PK Condition int FK PK ProductVenders int FK PK int FK PK Price int FK PK Discount int FK PK OptimisticLockField int FK PK GCRecord int FK PK Total int FK PK Summery int FK PK OptimisticLockField int FK PK GCRecord int FK PK Cust_ID int FK PK CustomerFirst_Name int FK PK int FK PK CustomerLast_Name int FK PK Phone int FK PK Address int FK PK City int FK PK State int FK PK Posta_code int FK PK Country int FK PK Order_ID int FK PK Product_ID int FK PK QuantityOrdered int FK PK PriceEach int FK PK OrderLineNumber int FK PK Cust_ID int FK PK CheckNumber int FK PK PaymentDate int FK PK Amount int FK PK ProductLine int FK PK TextDescription int FK PK HTMLDescription int FK PK Image int FK PK OFFICE_ID int FK PK City int FK PK Phone_number int FK PK Address int FK PK State int FK PK Country int FK PK PostalCode int FK PK Territory int FK PK Emp_Num int FK PK FirstName int FK PK LastName int FK PK Extention int FK PK Email int FK PK Office_ID int FK PK ReportTo int FK PK JobTitle int FK PK M1 M2 M3 M4 Emp_num int FK PK M1 M2 M3 M4 M1 M2 M3 M4 Cust_ID int FK PK M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 attribute name int FK PK M1 M2 M3 M4 M1 M2 M3 M4

PRODUCTSALEORDERPRODUCTCUSTOMERSORDER-DETAILSPAYMENTPRODUCT_LINEOFFICESEMPLOYEESProduct_IDFKOrderCountOrder_IDPKCreatedCustomerProduct_IDPKProduct_NameProductLineQuantityPriceConditionProductVendersPriceDiscountOptimisticLockFieldGCRecordTotalSummeryOptimisticLockFieldGCRecordCust_IDPKCustomerFirst_NameCustomerLast_NamePhoneAddressCityStatePosta_codeCountryOrder_IDFKProduct_IDFKQuantityOrderedPriceEachOrderLineNumberCust_IDPKCheckNumberPaymentDateAmountProductLinePKTextDescriptionHTMLDescriptionImageOFFICE_IDPKCityPhone_numberAddressStateCountryPostalCodeTerritoryEmp_NumPKFirstNameLastNameExtentionEmailOffice_IDFKReportToJobTitleEmp_numFKCust_IDFKattribute namePK

PRODUCTSALE ORDER PRODUCT CUSTOMERS ORDER-DETAILS PAYMENT PRODUCT_LINE OFFICES EMPLOYEES Product_ID int FK PK Order int FK PK Count int FK PK Order_ID int FK PK Created int FK PK Customer int FK PK Product_ID int FK PK Product_Name int FK PK ProductLine int FK PK Quantity int FK PK Price int FK PK Condition int FK PK ProductVenders int FK PK int FK PK Price int FK PK Discount int FK PK OptimisticLockField int FK PK GCRecord int FK PK Total int FK PK Summery int FK PK OptimisticLockField int FK PK GCRecord int FK PK Cust_ID int FK PK CustomerFirst_Name int FK PK int FK PK CustomerLast_Name int FK PK Phone int FK PK Address int FK PK City int FK PK State int FK PK Posta_code int FK PK Country int FK PK Order_ID int FK PK Product_ID int FK PK QuantityOrdered int FK PK PriceEach int FK PK OrderLineNumber int FK PK Cust_ID int FK PK CheckNumber int FK PK PaymentDate int FK PK Amount int FK PK ProductLine int FK PK TextDescription int FK PK HTMLDescription int FK PK Image int FK PK OFFICE_ID int FK PK City int FK PK Phone_number int FK PK Address int FK PK State int FK PK Country int FK PK PostalCode int FK PK Territory int FK PK Emp_Num int FK PK FirstName int FK PK LastName int FK PK Extention int FK PK Email int FK PK Office_ID int FK PK ReportTo int FK PK JobTitle int FK PK M1 M2 M3 M4 Emp_num int FK PK M1 M2 M3 M4 M1 M2 M3 M4 Cust_ID int FK PK M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 attribute name int FK PK M1 M2 M3 M4 M1 M2 M3 M4

PRODUCTSALE ORDER PRODUCT CUSTOMERS ORDER-DETAILS PAYMENT PRODUCT_LINE OFFICES EMPLOYEES Product_ID int FK PK Order int FK PK Count int FK PK Order_ID int FK PK Created int FK PK Customer int FK PK Product_ID int FK PK Product_Name int FK PK ProductLine int FK PK Quantity int FK PK Price int FK PK Condition int FK PK ProductVenders int FK PK int FK PK Price int FK PK Discount int FK PK OptimisticLockField int FK PK GCRecord int FK PK Total int FK PK Summery int FK PK OptimisticLockField int FK PK GCRecord int FK PK Cust_ID int FK PK CustomerFirst_Name int FK PK int FK PK CustomerLast_Name int FK PK Phone int FK PK Address int FK PK City int FK PK State int FK PK Posta_code int FK PK Country int FK PK Order_ID int FK PK Product_ID int FK PK QuantityOrdered int FK PK PriceEach int FK PK OrderLineNumber int FK PK Cust_ID int FK PK CheckNumber int FK PK PaymentDate int FK PK Amount int FK PK ProductLine int FK PK TextDescription int FK PK HTMLDescription int FK PK Image int FK PK OFFICE_ID int FK PK City int FK PK Phone_number int FK PK Address int FK PK State int FK PK Country int FK PK PostalCode int FK PK Territory int FK PK Emp_Num int FK PK FirstName int FK PK LastName int FK PK Extention int FK PK Email int FK PK Office_ID int FK PK ReportTo int FK PK JobTitle int FK PK M1 M2 M3 M4 Emp_num int FK PK M1 M2 M3 M4 M1 M2 M3 M4 Cust_ID int FK PK M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 attribute name int FK PK M1 M2 M3 M4 M1 M2 M3 M4

CUSTOMERSEMPLOYEESPAYMENTSSELL OFFICESORDERINGPRODUCTSORDERSINCLUDESPAY PAYMENTSINVOICE STATEMENTHANDLESMANAGES

CUSTOMERS EMPLOYEES PAYMENTS SELL OFFICES ORDERING PRODUCTS ORDERS INCLUDES PAY PAYMENTS INVOICE STATEMENT HANDLES MANAGES

CUSTOMERS EMPLOYEES PAYMENTS SELL OFFICES ORDERING PRODUCTS ORDERS INCLUDES PAY PAYMENTS INVOICE STATEMENT HANDLES MANAGES

OFFICESEMPLOYEESCUSTOMERPAYMENTSEXTRACT, TRANSFORM AND LOAD PROCESSESRELATIONAL DATABASEOPERATIONAL DATA STORE (ODS)DATA WAREHOUSEDATA MARTDATA MARTDATA MART

OFFICES EMPLOYEES CUSTOMER PAYMENTS EXTRACT, TRANSFORM AND LOAD PROCESSES RELATIONAL DATABASE OPERATIONAL DATA STORE (ODS) DATA WAREHOUSE DATA MART DATA MART DATA MART