Question

Pick a company (Coffee Shop) do the following:

1. Describe the business

2. Identify at least 4 data marts, describe the analytic or business functions they would support, and identify what data they will need, and where this data will come from. Include at least 10 fields for each data mart. No data mart should pull data from only one source system.

Answer 1

Answer:- A analytic or business functions DART MART focuses on a functional area for an organization and contains a set of data stored in a data warehouse. A Data Mart is a robust version of the Data Warehouse and is designed to be used by departments, units or sets of users specific to the organization. For example, Marketing, Sales, HR or finance. It is often controlled by a department within an organization.

Data Mart usually pulls data from just a few sources compared to a data warehouse. Data mart is smaller and more flexible compared to Datawarehouse. Data Mart helps increase user response time by reducing data volume
It provides easy access to frequently requested data.
Data mart is simpler to apply compared to Datawarehouse company. At the same time, the cost of implementing Data Mart is definitely lower compared to implementing a complete data warehouse.
Compared to Data Warehouse, datamart is agile. If there is a model change, datamart can be built faster because of its smaller size.
Datamart is defined by a Basic Matter. Conversely data warehousing is defined by interdisciplinary SMEs from a variety of domains. Thus, Data mart is more open to change compared to Datawarehouse.
Data is separated and allows very granular access control permissions.

Determine the Scope of the Mart Data Project

Before you start implementing data mart, you need to develop a plan for delivery. The critical input into this plan is the information requirements and priorities of your users. Once this information has been established and approved by your business sponsor, you can develop your key delivery list and assign responsibilities to your team.
Your first task is to judge the scope of the project. The scope of the data mart defines project boundaries and is typically expressed in some combination of geography, organization and application, or business function. Determining the scope usually requires compromising when you are trying to balance resources (such as people, systems, and budgets) with the scheduled completion date and the capabilities you promised to deliver. Defining your scope and making it clear to anyone involved is important because:

Set realistic expectations
Development priorities increase
Highlights of risks and problems
Allows you to estimate costs
Defining Requirements for Data Mart

To start implementing data mart, you need to judge your business and technical requirements. However, you should expect the requirements to change when users use the initial implementation and are better able to communicate the requirements. Data mart development is an iterative process, as data mart evolves in response to responses from users.

Determining Analytic & Business Functions

The purpose of the data mart is to provide access to data specific to a particular department or functional area. Data should be at a level that is meaningful to the type of analysis that end users want to perform, and should be presented in business terms that they understand. The hope is that data analysis in the data mart will lead to better business decisions. Therefore, you need to understand how business people make decisions - what questions users ask in the decision-making process, and what data is needed to answer those questions. The best way to understand business processes is through interviews with business people. The requirements identified as a result of this interview contain business requirements for your mart data.
When you collect requirements to mart data, you should focus your efforts on the information needs for a subject. Keep in mind that there are not enough documentation requirements to get all the information in the beginning, and you need to design a data mart to meet the changing needs. However, if you introduce new subjects or deviate from your main theme, you will lose focus and your schedule.
Although data mart addresses a key area, it usually has many business users, each with different requirements and expectations. Try to make sure at least one representative from each business area for your interview. For example, if you are building a marketing data mart, interview some people who are involved in some aspects of the marketing function (such as marketing analyst, channel specialist, direct marketing manager, and promotion manager).
Use a set of fixed questions or an interview template for each interview. Questions should focus on user information requirements, such as content, frequency of updates, priorities, and level of detail. Finally, set definite time limits at the interview stage and collection requirements; Otherwise, it can continue indefinitely as you try to filter each requirement. You cannot collect all the requirements within this time frame, but you will be sufficient to create a road map. Needs will change during the implementation period, and you will need a way to evaluate and accommodate the change request or reject and consider it for the next phase.

Identify Technical Requirements

You need to identify the technical requirements. This determines where you get the data that feeds the data mart. The main data source for the data mart is the operational system that manages the day-to-day transactional activities. Typically, this operational system is an online transaction processing system (OLTP). Your data mart can be eaten from more than one such operational source. However, you can usually not transfer data from the operating system to the data mart without intermediate processing. You need to understand how clean the operational data is and how much formatting or translation is needed to integrate it with other sources. Also, you need to judge how often you need to refresh or update the data. For example, if you use data for long-term planning and analytical horizons, you think you need a weekly or monthly feed rather than a daily feed.

Data can be shared and stored on different hardware / software platforms.

There are three main types of data mart:
Dependent: The dependent data mart is created by drawing data directly from operational, external or both sources.
Independent: An independent data mart is created without using a central data warehouse.
Hybrid: This type of data mart can take data from a data warehouse or operating system.