Skip to Content
Author's profile photo George McGeachie

What do you regard as essential knowledge for PowerDesigner users?

In 2011 I co-authored “Data Modeling Made Simple with PowerDesigner” with Steve Hoberman. From the title it’s obvious that data modellers were the primary audience, though I did my best to structure the book so that other users of PowerDesigner could make use of it. The book also contains Steve Hoberman’s work on ‘how to do’ data modelling, so I inevitably had to make some compromises in the PD content. I’m sure nobody would have bought a 1,000 page book that weighs 3 Kg and costs over $120. 🙂

I’m currently planning the second edition of the book, and I intend to address the compromises, to ensure that we create material of interest to the whole PD market. A number of readers have been kind enough to point out the compromises that they’ve noticed, and to suggest topics to be included later on.

Here’s my challenge to you

What would you regard as essential knowledge for PowerDesigner users, and just has to be included in the future book (or books – there will probably be more than one)?

  • for any PD user
  • for portal users
  • for PD ‘super-users’, those people who like to push the tool to the limit
  • for PD administrators
  • for a given type of user
    • data modeller
    • enterprise architect
    • business architect
    • DBA
    • application developer
    • solutions architect
    • etc

Please address suggestions via the form on my personal blog page, at

Thanks, George

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo dirk jaeckel
      dirk jaeckel

      As i see it, there is already a lot written about PD, except good examples about the API

      Author's profile photo bruce daly
      bruce daly

      I would definitely agree with that ! Samples outside the Data Modeling area would be handy. As well, the Reporting engine has limitations (although it is better with this Release) seems there are plenty of sample scripts to extend capability in that area that would be useful.

      Author's profile photo bruce daly
      bruce daly

      Obviously the majority of users are focused on Data architecture and design - these types of activity seem to be well covered in both the official Product docs and the secondary sources such as this Board. There is a very sparse set of documentation for people working in other areas such as the EA realm and developing across all architecture domains from Business to Implementation. Even sparser is the availability of examples.

      Also, for those working to a standard such as TOGAF, samples and guidance on everything from developing metamodel extensions aligned with the standard to basic repository information structure (hierarchy) would be handy. We have pretty much taken our best crack at it without a lot of public domain material being around. Would have been handy to have had something in the way of a starter set to work with or at least evaluate.