Data Warehouse Engineering: Techniques, Processes, and Implementation

Verified

Added on  2023/04/19

|3
|784
|370
Presentation
AI Summary
This presentation provides a comprehensive overview of data warehouse engineering techniques, focusing on the Unified Modeling Language (UML) and Unified Process (UP). It explores the implementation methods for data warehouses, emphasizing the importance of UML as a visual modeling technique and UP as an iterative process framework. The presentation covers various stages of data warehouse design, from information sources to final implementation, including ETL techniques and user needs. It also discusses the relationships between different data warehouse components, the Common Warehouse Metamodel, and the application of Unified Software Development Processing. Furthermore, the presentation addresses the analysis, design, and implementation of warehouse processes, user requirements, testing, maintenance, and post-development reviews, highlighting both top-down and bottom-up strategies for building data warehouses. The goal is to provide a structured and detailed understanding of data warehouse engineering.
Document Page
Slide-2
In this slide I will mention about what actually Data Warehouse Engineering is. This
slide also include methods on how Data Warehouse can be implemented. The slide also
discusses about Unified Modelling language and united process. Unified Modelling
Language can be considered as a general-purpose modelling language that intends to provide
a standard way to visualize the system designing. Unified Process is defined as iterative
process framework. Examples are Open UP and Agile United Process. The structure of the
paper include some important analysis and points out from shortcomings. In this region I
have given a summary on the DW engineering technique, the diagram is presented and then
description of different workflows are provided that make up the processes.
Slide-3
In this slide I will suggest certain premises by which goal of developing the DW
engineering process can be achieved. In order to get the goal, best suggestion would be UML
as visual modelling technique. UML is extended because it presents accurately, the different
parts of Data Warehouse and UML process is used extensively for UML packages with target
to provide numerous levels in a detailed manner. Data Warehouse tackles every Data
Warehouse designing stages in a well-organized manner, from sources of information to the
final implementation and which include defining of every ETL techniques and finalize the
user needs.
Slide-4
In this slide a basic diagram of Data Warehouse is provided. DW is not independent
from each other instead they are overlapping because they depend on each other in different
ways. If any change is made in one diagram the result also reflects on another diagram. An
example can be taken as DM is created from SCS and DWCS. Description regarding
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Common Warehouse Metamodel is provided. It is basically defined as an open industrial
standard of the Object Managing Groups used for integrating data-warehousing and also to
understand the tools required for business, based on shared metadata.
Slide-5
In this slide I am going to discuss about Data -Warehouse Engineering Techniques
which is confined to Unified Software Development Processing. The UP canbe defined as the
industrial standard of the Software Engineering Processes from the authors of the UML. UP
is basically a generic SEP that is being instantiated from the organization to that of the
domain. Project lifecycle four phases consist of Inception, Elaboration, Transition and
Construction. During the development of project there is a shift over iterations and then
finally leads to the maintenance and reviews after post development. Each workflow consist
of UML diagrams and development process. Different approach to the model and documents
the developing processes, but the structure is reconstructed based on different phase as every
models evolve over time. In this parts of the slide the explanation is about the main
information of workflow and it is highlighted in previous diagram.
Slide-6
This slide discusses about analysis, design and implementation of Warehouse process.
The diagram shown in the slide describes the entire process in a pictorial manner. The main
diagram include Conceptual Schema CCS and Data Mapping.
Slide-7
This slide discusses about the requirements that the user must specify. The UML is
used for providing visual modelling. Built the common template which specifies the name ,
Document Page
unique identifier are basically followed by us. This slide focuses on the discussion related to
testing, maintenance and post-development reviews. Goal is to verify the implementation. In
maintenance section goal of workflow is defining refresh and loading process. In post-
development review improving the operation is to be focused. If tracking of the system is
done the data that is basically used in estimation of time and the needs of future works. The
two strategies is building a Data Warehouse, it is top-down as well as a bottom-up approach.
In top-down kind of approach the DW is developed first and then DW becomes only
information sources. In bottom-up technique, DMs are build first from the transactional
systems, then Data warehouse is developed and then information sources in the DM is
genereated.
Conclusion Slide-
Now in this slide I am going to conclude my presentation that was related to Data
Warehousing. In the previous slides that I have explained was related to Data Warehousing,
its requirements, processes, tests any many more. If any questions arise regarding the entire
presentation please share with me so that I could resolve all the droughts related to this topic.
chevron_up_icon
1 out of 3
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]