PowerDesigner Interface

21 May 1996 updated

Platform independence (read "web enabled metabrowser"). at the top, the ERD should be a browsable clickable imagemap. at the bottom, interrogate the actual rdbms server's data (ie select distinct on a given column).

A generic viewer that would allow anyone to only view or print a CDM or PDM without actually opening the model in PowerDesigner. This would allow us to distribute copies of the CDM or PDM to developers or DBA thorough E-Mail.

More customization with respect to what can be displayed on the model. ie. cascade/restrict on delete.
Increased flexibility with the data model notation (the symbol for a dependent key, although quite accurate, is not easily understood by the business. Perhaps if the foreign keys were shown on the model there would be no need for a different relationship symbol.

Allow a snap to grid option in the CDM and PDM workspace.
Give greater control to the user in how the relationship lines are routed through the diagrams. Also, a cross over designator displayed when one relationship crosses another would be helpful.
We like to use color coding to designate different types of groups of entities, or tables created as a result of associations. Allowing user defined entity groups or classes with specific properties would be helpful.

Refer to the Microsoft Style Guide for accepted GUI practices.
New GUI concepts seem to assume unlimited screen space - many users are still on 14" screens.

We have considered PowerDesigner’s easy to use and understand interface is one of the tools strengths. However, we are a predominately a Microsoft shop and there are several areas that do not conform to the norm in Windows GUI standards. While they work correctly, I have received feedback many times that this makes the product feel inferior.
For many functions there are many ways to do the same thing, or set the same parameter or property. For easy of use I think that cutting back on some of this duplication would make a good interface even better.
Many of the dictionary lists, and entity property boxes bring up response windows that do not allow you to have other windows open for comparison. I can not see any reason why you would not allow the user to have more than one of these windows open and available.

GUI Standard Interface:

Adhere to Microsoft standards. Like it or not, most users are familiar with Microsoft’s standards. Anything written to this standard becomes easier to understand and use. These are mostly cosmetic changes but they will greatly increase the user’s satisfaction. It will also reduce the "clunky" feeling one gets when something acts differently than expected.
Eliminate extra controls. There are at least 3 ways to accomplish everything. This creates a sensory overload until the user figures out what he can ignore. The PowerDesigner interface might be a case where ‘less is more’.
On-screen editing. PowerDesigner sports a very productive interface already. However, it could be even better if I could edit names right on the diagram. It would be kind of like renaming icons under Windows 95 or OS/2.

Incorporate the data on lower level menus into their parent menus eliminating extra layers of menus.

Maintain views and scales between sessions. For example if I select Global View, then quit and re-enter the application, I get the default view provided by PowerDesigner and must reset it. Same is true if I select a percentage scale.
Maintain printer setup options between sessions. For example if I select landscape mode and a scaling factor, then quit and re-enter the application, I get the default values for these options.

We create our design deliverables in Microsoft word and it is difficult to place the CDM in a document. Currently, we cut and copy but this does not always work. Support for OLE would greatly assist us in this area.