Browse Prior Art Database

Method for deriving the supported Analytical Requirements for a given set of Structured and Unstructured data sources

IP.com Disclosure Number: IPCOM000240377D
Publication Date: 2015-Jan-28
Document File: 5 page(s) / 86K

Publishing Venue

The IP.com Prior Art Database

Abstract

When unifying data source systems for analytical purposes, thousands of mappings can be made from the data source systems to Analytical Requirements. This disclosure describes a method to quickly determine from these mappings the Analytical Requirements that are supported across the entire organisation.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 32% of the total text.

Page 01 of 5

Method for deriving the supported Analytical Requirements for a given set of Structured and Unstructured data sources

Disclosed is a method to quickly determine the Analytical Requirements that are supported across the whole organisation by its unified data source systems (structured data sources such as operational system databases and unstructured data sources such as streams).

    Many large organisations with data source systems unify these data source systems by mapping them to a Requirements Model for Business Intelligence purposes, enabling business reports to be produced that span the entire organisation. The term Requirements Model in the context presented here refers to an expression of business reporting requirements (see Figure 1). Such a model is intended for business users and is used in a Data Warehousing context. It can be used to identify the business analysis supported by a data warehouse model which can be either Kimball style Star Schema and conformed Dimensions or Inmon style Third Normal Form. The Requirements Model contains a set of Measures which measure Facts about the business. These Measures are related to Dimensions which provide axes of analysis for the Measures.

    When an organisation grows through the acquisition of another organisation, if it wants to continue to use the same business reports across the now larger organisation it will need to map the data source systems of the acquired organisation to the Requirements Model of the main organisation. The type of data in the data source systems of the acquired organisation is very unlikely to match exactly the type of date in the source systems of the main organisation. So the data source systems of the acquired organisation may or may not possess all of the data required for the business reports that the main organisation is accustomed to producing.

    For a large acquisition that has a large number of data source systems, the number of mappings to be made between these data source systems and the Requirements Model in the unifying process may be in the many thousands, making it a) difficult to determine quickly if the usual business reports that the main organisation is accustomed to producing is still possible across the now enlarged organisation; and b) in the case where these reports are not fully supported in the acquired organisation, which parts of these reports are present or missing in the acquired organisation.

    The disclosure outlined here presents a method that answers these questions relatively easily.

Background

    The Requirements Model has mappings from the Measures and Dimensions to objects (Entities and Attributes) in a Kimball style Dimensional Warehouse Model (DWM). This Dimensional Warehouse Model has mappings to objects (Entities and Attributes) in an Inmon type Data Warehouse.


Page 02 of 5

Figure 1.

    When defining requirements using the Requirements Model, a business user selects a Requirement in the Requirements Model and some Measure(s) a...