The key learning below is created from webcast “Sneak Peak: CA ERwin Modeling r8 Preview Demonstration” – presentation
ERwin Data Modeler goals
- RDBMS and Data Warehouse design
- Enterprise Application Integration (EAI)
- Data Administration and Governance
- Data Consolidation and Migration
- Master Data Management (MDM)
- Business Process Management and SOA development
You are No longer limited in space on the model.
On-demand UI windows
Precision object placement
User defined styles and theme settings (ex: DEV/ITG/PRO)
Place the cursor on the relationship and get callouts.
Functional Dialog Improvements
Static views of data can be captured in ERwin data modeler, but how do we capture dynamic views? Here are the most common techniques that we generally follow:
- spreadsheets to capture mappings
- process flow diagrams in visio and power point
- UML diagrams in IBM and Sparx tools
- Data Flow Diagrams (DFD) using visio
The problem with all this is that it is hard to maintain.
Solution – ERwin Data Modeler (DM) and ERwin Process Modeler (PM)
ERwin DM -
- used to model databases (static data stores)
- supports logical and physical models
- conceptual models can be created in visio and power point
- User Defined Properties (UDP) is used to define the actual type of a table (UDP can be defined to represent Flat files, SQL tables, Oracle tables etc)
ERwin only supports one type of database per model. So, if we use both Oracle and SQL Server, we can have one logical model but two physical models in ERwin. Data warehouses deals with flat files, SQL Server, Oracle, Cubes etc..
ERwin PM -
- previously called BPwin
- supports multiple diagram types
- used to design the processing of data
Process Modeler Diagram
Drill into Customer Profitability
The diagram shows all the key components of the solution.
Drill down further into Commercial BI Data. You can decompose the model until you are comfortable or decompose until one developer can build it. These diagrams can show:
- Data Stores
- Data Flows
- External Entities
The above can be tied back to ERwin Data Modeler. It can give the developer the level of details needed. We can use naming conventions such as:
- A01.01.01 (activity name)
- D01 (data store name)
- E01 (external entity)
Example of Customer Loan external Entity in ERwin DM
With the DM, PM and the narrative in the PM, the developer has all the information to develop portion of the solution.
With ERwin DM and PM, we can model both the static views of a data warehouse and the flow of data. Use PM to decompose the solution. Use DM to model the database.