ERwin r8.2 – see what’s new on Feb 1st

CA have announced two new products, along with ERwin r8.2:

  • CA ERwin® Web Portal: Visualize Information from the Web
  • CA ERwin® Data Modeler for Microsoft® SQL Azure™: Managing Data – both On-Premise and in the Cloud
  • CA ERwin® Data Modeler r8.2: Collaboration Facilitated

You can find out more at their webcast on February 1st from 1:00 to 12:00 EST – click this link to register.

Advertisements

Let’s get down to Business – webcasts from CA

CA have announced a series of webcasts to take place in February, which they’re calling “Let’s Get Down to Business”. The series focusses on the business value of data modelling, with a great set of speakers who are all well worth listening to – Alec Sharp, Karen Lopez, and Peter Aiken.

Worried How Data Quality in your Organization may be affected by a move to the Cloud?
February 6th, 2012
1:00 p.m. – 2:00 p.m. EST

Help your Business Love its Data (Models): Tailoring Data Models for your Audience
February 7th, 2012
1:00 p.m. – 2:00 p.m. EST

Getting the “Business” into Business-Oriented Data Modeling – Practical Techniques and Examples
February 9th, 2012
1:00 p.m. – 2:00 p.m. EST

Follow this link to find out more http://erwin.com/events/detail/lets_get_down_to_business/

Adding existing relationships to a diagram in PowerDesigner

I remember the first time I came across Sybase PowerDesigner. It was version 12, re-badged by Quest Software as QDesigner. I had multiple ERDs in my CDM, and I wanted to include existing relationships on a new ERD I was putting together. I was used to a command in Oracle Designer that would add all missing relationships (including inheritances) to the diagram – every existing relationship that connects two entities that already appear on the diagram would be included. After a search, I found the equivalent command in PowerDesigner. However, I often just wanted to include selected relationships on the diagram, so I tried dragging them onto the diagram from the browser. I was really annoyed at the result, and took a while to understand what was going on, and I know I wasn’t the only one. I don’t think it’s a problem with PowerDesigner really, but a symptom of the fact that it doesn’t always work in the same way as other tools.

The confusion still exists today, as evidenced by a recent thread on the Info Advisors PD group – “Even when dragging a relationship / reference from the browser into a diagram where the participating entities have already been included as symbols, PD creates new symbols for them, rather than connect the relationship’s symbol to the existing entities’ symbols. One has to manually delete the extra ones; a nuisance...”.

When you drag a relationship onto a diagram from the browser, PD will automatically include the two entity symbols as well, even if the entities already appear on the diagram. These new entity symbols are called ‘graphical synonyms’, and can actually be very useful. If you do create unwanted graphical synonyms, all you need to do is delete the new entity symbols, and the relationship symbol will move to the original entity symbols. This could be a real pain in the neck if you added a lot relationships at the same time.

Prevention is better than cure, so remember to hold down the <Shift> key when you drag the relationship(s) from the browser to the diagram – the relationship will be drawn between the existing entity symbols and no new graphical synonyms will be added.

One problem with dragging relationships from the browser is ‘How do I know which relationship is which?‘ Here’s the list of relationships in one of the supplied demo models:

How well do you know your model? In this model, the relationship names are short, and we have some duplicate names as well. If you want to, you can make it more difficult to create duplicate names, using the ‘unique code’ setting in the model options.  As long as you synchronise your relationship names and codes, you won’t get duplicates. In anything but the simplest model, or one you know exceptionally well, that still won’t help you know which relationship you need to drag onto your diagram. It will also force you to stop giving your relationships the same name, which is no bad thing in itself.

In this model, the two ‘Belongs to’ relationships can be referred to as “Employee Belongs to Division” and “Task Belongs to Project“. Now, you could change the relationship names to include one or both of the entity names which would certainly make the browser list easier to use:

That gives you a re-work overhead you don’t really want – if (sorry, when) you need to move a relationship end from one entity to another, you’ll have to remember to rename the relationship. By the way, don’t worry about displaying the extra-long name on diagrams, because you can choose to display one or both role names instead of the relationship name (you DO use role names don’t you?), like this:

I suggest you come up with some compromise standard for relationship names so you can make sense of the browser, but don’t put too much effort into it. I very rarely look at the list of relationships in the browser. Meaningful relationship names may be useful in reports.

Alternatively, customise PowerDesigner by adding an Event Handler to derive relationship names, such as “Division Employs Employee” or “Project Requires Task”. If you do create such an Event Handler, remember to check for duplicate names.

If I want to include missing relationships in an ERD, there are two better ways. If I want to see a list of my relationships, there’s a better way of doing that as well.

OK, let’s get back to adding missing relationships. Here’s the first easy way – select the Show Symbols command on the Symbol menu, and choose the relationships you want to include:

Notice that one the relationships is listed as ‘Hidden’. It was previously displayed on the ERD, but I decided to hide it. I’ve selected it for inclusion, and it will re-appear in the diagram in the same position and style as it appeared before (assuming the entity symbols haven’t moved, of course). Including missing relationships this way will not result in graphical synonyms being added (unless, perhaps – I haven’t tested this – they were previously attached to graphical synonyms that are still present).

Don’t worry if your Show Symbols dialogue doesn’t look like the one above. I probably tailored mine using the customisation tool , so you can replicate it quite easily.

The second easy way to add missing relationships is the “Add missing link” tool Missing Links tool  on the Diagram Toolbar. If you have nothing selected, this will add every link symbol that is missing from the diagram, which may give you a few surprises. If you want to include all relationships for, say, the entity Team, here’s what you do:

  • select the symbol for the “Team” entity
  • click on the “Add missing link” tool

PowerDesigner presents a choice for you:

Missing Links options

  • select the first options to add all missing links for the selected entity. This will include relationships and traceability links connecting the entity other symbols that er already on the diagram.

Now for my final point, listing relationships without using the browser. Which would you rather work with, the list of names in the browser, or a list that you have control over? In the list of relationships shown below (via Relationships on the Model menu), I can choose the properties I want to see, the order in which to show them, sort the listing, and filter according to property contents:

Again, this is a customised list, so it may take you a few minutes to achieve, but the results will stay with you – I carried out this customisation several months ago. I can click on the column headings to sort the list if I want to. I can also edit any of the properties that are displayed, as long as they aren’t shown in grey. By adding new rows to the list, I can create new relationships, which will automatically be added to my current diagram.

By the way, the ‘S’ column tells me whether or not the relationship has a symbol on a diagram – the first one on the list does not have a symbol.

Read widely – here are some books data modellers should take a look at

If you’re like me, you’re a book addict. I’ve built up a large library of books related to metadata and data modelling, and also on subjects such as process management, IT service management and mind mapping. When I was working with Steve Hoberman on our recent book, I didn’t want the book to give the impression that data modellers work in isolation, so I went through my library looking for useful material. I thought I’d share some of my findings with others, so here’s a list of books you should take a look at:

  • Business Rule Concepts (Ronald G. Ross, 2009) – read pages 74, 77 about the role of verbs in describing facts. See also Chapter 1 about noun concepts and terms; I especially like the statement that a  “noun or noun phrase…represents merely the tip of an iceberg with respect to meaning”
  • Building Business Solutions: Business Analysis with Business Rules (Ronald G. Ross and Gladys S.W. Lam, 2011) – Read the chapter on Fact Models and how similar these are to Conceptual Data Models – see also my review of this book
  • Data Quality Assessment (Arkady Maydanchik, 2007) – chapter 4 provides an excellent introduction to and a detailed discussion of attribute domains
  • Document Engineering (Robert J. Glushko and Tim McGrath, 2008) – if you’re modelling the data in documents or service messages, you really must read this book
  • Mind Maps for Kids (Tony Buzan, 2003) – OK, it’s aimed at kids, but it’s a great introduction to the topic – look at the use of colour in his mind maps – how can you use colour effectively in your data models?

New TDAN article from me and Steve Hoberman

The Data Administration Newsletter (TDAN) have just published a new article by myself and Steve Hoberman, based on our recent book “Data Modeling Made Simple with PowerDesigner”.

Tools are necessary for data modeling. You can’t avoid having them, but which one suits you? Well, that depends on what you want to do with those tools, where you want to work in the Data Model Pyramid. See the article to find out what we mean.

Essential reading for data modellers – new book by Ross and Lam

Check the book reviews page for a review of a must-read volume for data modellers – “Building Business Solutions: Business Analysis with Business Rules” by Ron Ross and Gladys Lam.