CASE Tool evaluation for DWH development 12 Each

  • Slides: 2
Download presentation
CASE Tool evaluation for DWH development (1/2) Each of the tools provides all necessary

CASE Tool evaluation for DWH development (1/2) Each of the tools provides all necessary features for data modeling in general. There are various comparisons available on internet to provide various perspectives and opinions. The following overview provides Adastra‘s opinion relating to those functions which are important for data warehouse development projects. Feature Tool Er. Win Enterprise Architect Key concept of the CASE tool Universal data modeling tool Data modeling is supported as part of a complete UML modeling CASE tol. Supported data models Conceptual Logical Physical Class diagram Complete UML modeling Requirements model Other supported modeling Business Terms definitions Requirements management Universal data modeling tool with extended functions for data warehouse development Conceptual Logical Physical Multi-dimensional Requirements Model Enterprise Architecture Model Information Liquidity Model (data movement/ETL) Process model Free model X X X Data modeling X X X Transform Logical to Physical X X DB Reverse engineering X X X Custom extensions X X X Infrastructure artefacts Forward engineering (DDL) X X X (including code customization) Model-to-model comparison X X X Data models merging Data movement modeling (Mapping definitions) Lineage/Tracability X Customizable report generation Scripting and automation 1 Power. Designer X X X (. html, . pdf, . rtf, . txt) X X (. html, . rtf) X

CASE Tool evaluation for DWH development (2/2) The following overview provides Adastra‘s opinion relating

CASE Tool evaluation for DWH development (2/2) The following overview provides Adastra‘s opinion relating to those functions which are important for data warehouse development projects. Er. Win • Valued for its data modeling features • Strong data modeling support and navigation features Evaluation • Lack of support for mapping management which would need to be maintained outside the tool. • Our clients now use it only for data model documentation • Most clients convert to Power. Designer. Verdict 2 FOR DATA MODELING AND DATA MODEL MANAGEMENT Enterprise Architect Power. Designer • The tool is suitable for application system development - Data modeling is not in focus • Developed for Data Warehousing projects. • Data architects would lack flexibility found in the other data modeling tools. • No support for data movement modeling • We and our clients use the tool for projects which are –NOT- data warehouse oriented • Occasionally, used only to document partial data models WE DO NOT RECOMMEND FOR DWH PROJECT! • Strong data modeling support and navigation features • Information liquidity model for ETL mapping definitions. • Strong extension and scripting capabilities can be used to support metadata-driven ETL development • The tool is used by most our clients implementing DWH! FOR ENTERPRISE DATA WAREHOUSE DEVELOPMENT PROJECT