Showing posts with label ERwin. Show all posts
Showing posts with label ERwin. Show all posts

Monday, May 2, 2011

ERwin Data Modeler r8 (new features)


The key learning below is created from webcast “Sneak Peak: CA ERwin Modeling r8 Preview Demonstration”presentation

ERwin Data Modeler goals

  1. RDBMS and Data Warehouse design
  2. BI
  3. Enterprise Application Integration (EAI)
  4. Data Administration and Governance
  5. Data Consolidation and Migration
  6. Master Data Management (MDM)
  7. Business Process Management and SOA development

You are No longer limited in space on the model.

On-demand UI windows

Productivity enhancements

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

Sunday, May 1, 2011

A quick look at the ERwin DM and PM


The key learning below is created from webcast Optimizing design of your data warehousepresentation

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:

  1. spreadsheets to capture mappings
  2. process flow diagrams in visio and power point
  3. UML diagrams in IBM and Sparx tools
  4. 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 -

  1. used to model databases (static data stores)
  2. supports logical and physical models
  3. conceptual models can be created in visio and power point
  4. 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 -

  1. previously called BPwin
  2. supports multiple diagram types
  3. 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:

  1. Activities
  2. Data Stores
  3. Data Flows
  4. 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:

  1. A01.01.01 (activity name)
  2. D01 (data store name)
  3. 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.