PowerDesigner® vs.

ERwin Technical Comparison

A white paper from Sybase, Inc.

W H ITE PA P E R
Table of Contents
Section I: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
PowerDesigner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
ERwin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Philosophy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Versions and Pricing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
PowerDesigner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
ERwin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Section II: Physical Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Raw Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Test System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
PowerDesigner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
ERwin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Component Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Section III: Features and Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Supported DBMS Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Supported Object-Oriented Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Supported Methodologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
PowerDesigner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
ERwin/BPwin/ACM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
PowerDesigner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
ERwin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Component Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Ease of Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Windows Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Modeling Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Integration with other Modeling Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Reporting Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Process Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
PowerDesigner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
BPwin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Dimensional Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
PowerDesigner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
ERwin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Object Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
PowerDesigner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Component Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
PowerDesigner Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
ModelMart Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
About the Author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Section I: Introduction
Purpose
The purpose of this document is to compare PowerDesigner® against ERwin, BPwin and
Component Modeler (ACM) at a detailed technical level. This will primarily cover the data
modeling functionality, but will also address the business process, object-oriented and other
modeling capabilities included in each tool. Additionally, overall tool set stability and
performance will be evaluated and compared.
History

PowerDesigner
PowerDesigner started life as S-Designor, which was written by Xiao Wang of SDP Technologies,
a French company that was started in 1983. Powersoft purchased SDP in 1995, and Sybase
purchased Powersoft later that same year. Sybase currently owns all rights to PowerDesigner.
The first commercial release of S-Designor (version 2.0) in France was in 1989, and in the US in
1992. ProcessAnalyst was added to the suite in 1994. The first version of PowerDesigner (6.0)
was released in 1997. WarehouseArchitect was added in 1998.
In 1999, PowerDesigner (7.0) was rewritten to take advantage of newer technologies and to
provide an interface more consistent with other Sybase products. The latest version of
PowerDesigner (10) was released in February of 2004.

ERwin
ERwin was created by Logic Works, which was founded in 1988, by Professor Ben Cohen.
Platinum purchased Logic Works in 1998, and Computer Associates purchased Platinum in
1999. Computer Associates currently owns all rights to ERwin, BPwin and Component Modeler.
The first commercial version of ERwin was released in 1990. The latest version of ERwin (4.0
SP2) was released in March of 2002. The first version of BPwin was released in 1994 and the
current version (4.1 SP1a) was released in April of 2003. The current version of Component
Modeler (5.0.0.1205) was released in May of 2003.
Philosophy
There is a considerable difference in the basic philosophy behind the two companies.
PowerDesigner is inclined to use multiple loosely coupled models within a single adaptable
interface. This includes business, data and object modeling components. Contrary to this
approach, ERwin, BPwin and ACM are separate applications that do not share the same look
and feel. ERwin prefers to use a single tightly mapped logical/physical model (although the user
can separate them).
First, a short description of the models used by the tools:
Business Process models (BPM) describe the processes in a portion of the business at a very
high level.
Conceptual data models (CDM) are at a high level of abstraction and describe the information
needs of a business.
Logical data models (LDM) describe most of the elements needed for a database, but remain
independent from any specific database.
Physical data models (PDM) accurately describe a specific database language and structure.
Dimensional data models (DDM) are used to model decision support system layouts and
typically are not normalized database structures.
Object oriented models (OOM) are standard UML diagrams and provide a solid method for
mapping business processes to application code.
1
XML models provide hierarchical diagrams of the distinctly non-relational aspects of XML
elements. They provide a graphical view of the elements, grouping and other components
 defined in the XML Schema Definition and Document Type Definition languages.
Entities and relationships in a CDM are business “things” that are important enough to describe.
Everything is intended to communicate at the business user’s point of view without using
implementation terminology (indexing and foreign keys). The LDM is closer to the database,
being considered by most to be a link between CDM and PDM. One would find references to
indexes and foreign keys, but not exactly how to implement them in a specific database. The
PDM matches either an existing database, or represents a planned database, and has all of the
database-specific information, such as database creation commands, storage layouts, etc.
The DDM is a diagram option for both PowerDesigner and ERwin. One or many PDMs can
be the source for a DDM, thus enabling complex data migration paths to be modeled.
The BPM and OOM are similarly related; as the high-level process’s descriptions eventually
become associated with specific programmatic solutions in the coding language.
ERwin does not implement a CDM, which means that ERwin doesn’t have a built-in, coupled
business level view of the business data requirements. Furthermore, terminology is used from
the CDM (Entity, Attribute, etc.) in the ERwin LDM, which could be confusing. As stated
earlier, ERwin can separate the logical and physical models, and derive from either model to
the other. ERwin also has an interface called Saphir to provide access to the SAP metadata,
allowing users to import and work with SAP models.
PowerDesigner, does have the CDM, and has added LDM support by modifying the PDM.
The major consideration at this point is that virtually any model can be derived (Sybase
prefers the term “generate”) from any other model. Specifically, a CDM can be generated
from another CDM, allowing a high-level subject area model and a low-level fully attributed
model. This loose coupling in PowerDesigner is a powerful concept, but it loads the models
with information about the links between them.
The BPwin and ACM applications are completely different not only from ERwin, but from
each other. BPwin is a very formal tool with a specific methodology. ACM supports multiple
methodologies and flows through the methodologies.
Versions and Pricing
The pricing information listed below was gathered from the Sybase web site and various
software resellers (CA doesn’t offer pricing data on their web site) and is the standard pricing
for new purchases (not upgrades) with no discounts or competitive pricing deals applied.
Pricing does not include shipping and tax dollars. ODBC drivers were added to ERwin
since they are not included in the standard package. The Object Oriented module from
PowerDesigner is equivalent to Computer Associate’s AllFusion Component Modeler.

PowerDesigner
Base Update Basic
PowerDesigner 10.0 Price Subscription Maintenance

Business Process Architect (BPM) Standalone $1,495 $329/yr $568/yr

Business Process Architect (BPM) Enterprise $3,490 $769/yr $1,326/yr
PhysicalArchitect (PDM) Standalone $995 $219/yr $378/yr
PhysicalArchitect (PDM) Enterprise $2,990 n/a $1,136/yr
DataArchitect (CDM & PDM) Standalone $2,995 $655/yr $1,138/yr
DataArchitect (CDM & PDM) Enterprise $4,990 $1,095/yr $1,896/yr
Developer (OOM & PDM) Standalone $2,995 $659/yr $1,138/yr
Developer (OOM & PDM) Enterprise $4,990 n/a $1,896/yr
ObjectArchitect (OOM, CDM & PDM) Standalone $4,995 $1,095/yr $1,898/yr
ObjectArchitect (OOM, CDM & PDM) Enterprise $6,990 $1,535/yr $2,656/yr
Studio (BPM, OOM, CDM & PDM) Standalone $5,995 $1,315/yr $2,278/yr
Studio (BPM, OOM, CDM & PDM) Enterprise $7,495 n/a $2,848/yr
2
Update Subscription Plan provides 1 year of major and minor updates.
Basic includes USP plus tech support.
ERwin
Base Update Solution
AllFusion Modeling Suite 4.1 Price Protection Kit
ERwin Data Modeler MLP Version 4.1 $2,847 $799/yr $19
ERWin Data Modeler OLP Version 4.1 $2,829 $799/yr $19
Data Model Validator 4.1 MLP $1,374 $154/yr $19
Data Model Validator 4.1 OLP $1,410 $154/yr $19
Process Modeler MLP Version 4.1 $1,921 $538/yr $19
Process Modeler OLP Version 4.1 $1,890 $538/yr $19
Component Modeler OLP Version 4.1 $1,470 $399/yr $19
Model Manager 1 User Connection MLP 4.1 $1,137 $312/yr $19
Model Manager 1 User Connection OLP 4.1 $1,149 $312/yr $19
Model Manager 5 User Connection MLP 4.1 $5,569 $312/yr $19
Model Manager 5 User Connection OLP 4.1 $5,518 $312/yr $19
Model Manager 10 User Connection MLP 4.1 $10,799 $312/yr $19
Model Manager 10 User Connection OLP 4.1 $10,807 $312/yr $19
Suite (ERwin, BPwin and Examiner) $6,000 $1,600/yr $19
ODBC Drivers (DataDirect) $125
Note that the Erwin components are all sold as “license only”. The Solution Kit is the actual media.
MLP – Multiple License Program – discounts for large numbers of product
OLP – Open License Program

Section II: Physical Attributes

Both tools are marketed as enterprise-level modeling tools. They have a repository to support
many of these functions, such as version control and model ownership. This section compares
the tools with respect to the physical implementation of their respective model management
techniques.
Minimum System Requirements
PowerDesigner
• Microsoft Windows 98/NT version ERwin/BPwin
4.0/2000/XP • Windows NT, Windows 95/98/Windows
• 96 MB of RAM minimum 2000/ME, XP
• 170 MB of hard disk space for local- • 64 MB RAM (128 MB RAM recommended
machine installation of entire suite for large models)
(including BPM, CDM, PDM, and OOM) • Minimum 120 MB hard disk space for
(more may be required depending on both ERwin and BPwin
some installation options) • Minimum 125 MB for Component
• Total of 250 MB in test configuration Modeler
Raw Performance
In short, both tools use files to store the individual models and can handle large models easily.
The usage of memory and disk is very similar; however, ERwin supports a single file format to
store both logical and physical information as well as a separate logical model and physical
model. Both tools support an XML format. When using XML format ERwin was significantly
slower. s XML is a verbose file format, the XML files were understandably significantly larger
than their binary compliments, but the XML format is mainly intended for publishing and
model sharing outside of the scope of the individual tools.
Test System
The computer used to perform the tests is a Gateway laptop (2.8 GHz, 512 MB RAM).
Timing was calculated using a standard stopwatch, initiating on mouse click and stopping
when the task appeared to be complete. Most of these were obvious, as the cursor changes to 3
an hourglass through the processing and changes back to a pointer at the end. The file and
memory usage statistics were read directly from the Windows Task Manager and Explorer
dialog boxes.
 Test Case
A 500 table sample model was used in the tests below, starting with the same SQL script for
both tools. For the ERwin tests, both the combined Logical/Physical and the Physical-only
model are shown.
Test Results
PowerDesigner ERwin
Model Access Method File-based File-based
Maximum Objects Per Model Unlimited Unlimited
File Format XML text file or proprietary XML text file or proprietary
binary file binary file
Reverse Engineer 63 Sec 9 Sec
Binary File Combined Physical
File Size 1,365KB 1,704KB 1,720 KB
Load Time 2 Sec 2 Sec 2 Sec
Save Time 3 Sec 2 Sec 2 Sec
XML File
File Size 3,550KB 4,987 KB 4,980 KB
Load Time 4 Sec 13 Sec 13 Sec
Save Time 4 Sec 7 Sec 7 Sec
Minimum Memory Footprint Mem Usage 46,168KB Mem Usage 22,752KB
VM Size 26,624KB VM Size 13,852KB
Nominal Memory Footprint Mem Usage 70,500KB Mem Usage 29,256KB
VM Size 46,000KB VM Size 20,036KB

Notes:
The memory numbers for PowerDesigner are for the entire suite, which loads data, business process,
object oriented and XML modeling components. ERwin was just the data modeling piece.
The file sizes for ERwin do seem strange, as there was no difference if physical-only or combined was
selected.

Stability
To measure stability, both tools were run for an extended period of time on a workstation
with other applications running concurrently. Models were opened and closed and standard
functions from the on-line documentation were attempted. When ODBC or other direct
links were used to reverse or forward engineer a database, there were typical vulnerabilities
to the third party software. However, the Merant drivers shipped with PowerDesigner are
considered extremely stable and, as in the case of the Oracle database, many vendors recom-
mend using Merant drivers rather than their own drivers.
ERwin does not ship with any ODBC drivers.

PowerDesigner
There were no stability issues with PowerDesigner. All tests were performed without incident.
The user interface was solid, requiring no “refreshes” to correct any graphic anomalies. There
were no crashes or system failures during the test.

ERwin
The basic user interface (UI) has not changed much since 3.5, although it is much more stable.
All tests were performed without incident, and the user interface was solid through the entire
experience. There were no crashes or other system failures. However, in the tests, there were
problems with the test model where it insisted that there were foreign key migration issues
4
(there were none) and the auto-layout was incorrect.
Component Modeler
The UI is clumsy and hard to understand. Just creating a new model is difficult, as the termi-
nology is totally different from ERwin (a “model” is called a “workspace” in ACM, and a
“model” in ACM is actually the class of models in the UML specification. However, the
application was stable and there were no crashes.

Section III: Features and Functionality

Basic performance is only one indicator in comparing design tools. The features a tool offers
can balance many performance problems, although the absence of certain features makes
even top performance irrelevant, since the desired function is either impossible or extremely
difficult to accomplish.
Supported DBMS Platforms
The chart below details the DBMS platforms explicitly supported by both tools. For clarification
purposes, “support” means that the tool can both create objects for and reverse engineer
objects from the specified database.
Erwin does include the ability to directly connect to some databases, notably Sybase’s SQL
Server via dblib or ctlib (which are Sybase connection products that must be purchased
separately). PowerDesigner ships with a full set of Merant ODBC drivers. Erwin users must
buy drivers separately.
Worth noting is that PowerDesigner uses “definition files” to store the information used to
reverse and forward engineer the databases. Within the PowerDesigner interface, users can
edit the definition for any database, create a new one based on an existing definition, or
merge two other definitions together. This gives the user much more flexibility to handle
minor changes published by database vendors and to support new databases unknown to
PowerDesigner. Beyond this is the ability to customize the appearance of the generated DDL
text to conform to any existing corporate standards.
Erwin’s list of databases is coded into the application and cannot be changed.
Database Vendor, Name and Version PowerDesigner ERwin
ADABAS D ◆
ALLBASE/SQL G.1 ◆*
ANSI Level 2 ◆
CA Clipper 5.01 ◆
dBase IV (SQL) ◆
FoxPro ◆
HiRDB ◆
IBM AS/400 ◆* ◆
IBM DB2 MVS Version 4 & 5 ◆* ◆
IBM DB2 UDB 5.x Common Server ◆ ◆
IBM DB2 UUDB 6 OS/390 ◆* ◆
IBM DB2 UDB 6.x Common Server ◆ ◆
IBM DB2 UDB 7 OS/390 ◆
IBM DB2 UDB 7.x Common Server ◆
IBM DB2 UDB 8 OS / 390 ◆
IBM DB2 UDB 8.x Common Server ◆
Informix SQL 7.x ◆ ◆
Informix SQL 8.x ◆*
Informix SQL 9.x ◆ ◆
Ingres 2.x ◆
Ingres Version 6.4 ◆ 5
InterBase 4.0 ◆ ◆
InterBase 5.x & 6.x ◆
 Database Vendor, Name and Version PowerDesigner ERwin
Microsoft Access 95 ◆
Microsoft Access 97 ◆ ◆
Microsoft Access 2000 ◆ ◆
Microsoft SQL Server 6.x, 7.x & 2000 ◆ ◆
MySQL 3.22, 3.23 & 4.0 ◆
NonStop SQL ◆*
ODBC 2.0 ◆
ODBC 3.0 ◆ ◆
Oracle Version 7.3 ◆
Oracle Version 7 ◆
Oracle Version 8 ◆ ◆
Oracle Version 8i (8.1.5) ◆
Oracle Version 8i2 (8.1.6) ◆
Oracle Version 9i ◆
Paradox 7 for Windows ◆
PostgreSQL 7.3 ◆
Progress 8.x ◆
RDB 7.0 ◆
Red Brick Warehouse 5.xx ◆ ◆
SAS ◆
SQLBase 5.0 & 6.0 ◆
Sybase AS Anywhere 6, 7, 8 & 9 ◆
Sybase AS Enterprise 11.x ◆ ◆
Sybase AS Enterprise 11.0, 11.5 - 11.9 ◆
Sybase AS Enterprise 12.0 & 12.5 ◆
Sybase AS IQ 12.0 & 12.4.3 ◆
Sybase SQL Anywhere 5.x ◆ ◆
Teradata ◆*
Teradata 2.x ◆
*Not Certified – Sybase does not have access to that database environment for testing, so cannot verify
fixes and updates. The customer having a problem would need help in the verification process.

Supported Object-Oriented Languages

The chart below details the languages explicitly supported by PowerDesigner OOM and
AllFusion Component Modeler (ACM). For clarification purposes, “support” means that the
tool can both create objects for and reverse engineer objects from the specified language
source code.

Database Vendor, Name and Version PowerDesigner ACM

C# ◆
C++ ◆ ◆
CORBA ◆ ◆
Java™ ◆ ◆
Sybase PowerBuilder® 7, 8, 9 ◆
Microsoft Visual Basic .NET ◆
Microsoft Visual Basic 6 ◆*
Microsoft Visual Studio .NET Import only
RTM - Requirements Traceability Management ◆
XML – Data (BizTalk) ◆
XML – DTD ◆
XML – Schema ◆
6
*Not Certified – Sybase does not have access to that database environment for testing, so cannot verify
fixes and updates. The customer having a problem would need help in the verification process.
Supported Methodologies
The tools differ in their implementation of relational theory; it is worthwhile to point out
these differences in methodology and notation. Erwin is founded primarily in the Integration
Definition for Information Modeling set of standards while PowerDesigner is based on the
Information Engineering/Relational concept.

PowerDesigner
Process • Control Flow Diagram
• ebXML
• Business Process Execution Language for Web Services (BPEL4WS)
• Sybase Integration Orchestrator (SOA)
• Service Oriented Architecture
Conceptual • Information Engineering (IE)
• IDEF1X
Physical • Relational
• Information Engineering (IE)
• CODASYL
• Dimensional Modeling
• IDEF1X
Object Oriented Model • Class Diagram • Statechart Diagram
• Object Diagram • Activity Diagram
• Use Case Diagram • Component Diagram
• Collaboration Diagram • Deployment Diagram
• Sequence Diagram
XML Model • XML Schema Definition • Document Type Definition

ERwin/BPwin/ACM
Bpwin • IDEF0 • Gane & Sarson
• IDEF3
Logical • IDEF1X • Information Engineering (IE)
Physical • Information Engineering (IE) • Dimensional Modeling
Component Modeler • Class Diagram • Collaboration Diagram
• Use Case Diagram • Component Diagram

User Interface
The user interface is the first experience users have with the product; therefore, it cannot be
overemphasized how important a robust user interface is to the overall acceptance of the tool.
PowerDesigner
The user interface in version 10.0 is mature and stable. The graphic design features built into
PowerDesigner are comparable to many commercial drawing tools. Adhering to UML concepts, any
model can contain packages that can contain other packages. At any level, from the model down,
multiple diagrams of the objects at that level can be created and maintained. Objects created
in one package or model can be referenced via a “shortcut” placed in any other package or model.
ERwin
ERwin has always had a slightly more cumbersome interface, with a general lack of graphic
functionality. The interface has improved in 4.0, adding a number of very nice features, such
as the Explorer view and graphic elements similar to those found in PowerDesigner. However,
the general impression of the interface is still clumsy.

Component Modeler
Component Modeler sports a very crude user interface, lacking most features that other
modeling tools typically have, such as being able to route lines properly when objects are
moved. The terminology used is completely different even from ERwin, calling models 7
workspaces, which causes a lot of confusion.
 Ease of Use
These features include those that make the tools particularly easy to use. This includes being
able to add additional graphic objects to the model to help explain or identify objects.
Model Organization
Workspace
Multiple Diagrams
inside a model
Subject Areas in Model
Convert Diagrams into
Packages
Move Diagrams to Packages
Object placement
Freeform text
Edit text directly on graphic
Boxes, polygons and lines
Symbol, text, and line color
and other graphic highlighting
Line and symbol outline style
Text font, sizing and alignment
Auto-layout
Vertical and horizontal
alignment
Grid and snap-to-grid
Group and ungroup, arrange,
back and front
Protect and unprotect
graphic items
Facility to find objects
Page Grid
Help facility
On-line documentation
8 Leverage one module when
learning another
PowerDesigner
Yes, a workspace with folders
to group models
Yes, specific configurations
of folders and models can
be saved.
Yes
Yes, via UML standard
packages allowing nesting
Yes
Yes
High degree of control
Yes
Yes–Major object names only
(entity, relationship)
Yes, can place any graphic
with text on the diagram and
attach them to objects
Yes
Yes
Yes
Yes, both as a part of the
reverse engineering process
and on-demand from a
menu. Can be executed
repeatedly to try different
layouts. Very good.
Yes, left, center, right, top,
middle, bottom and evenly
spaced horizontally or
vertically.
Yes, with customization
for each diagram
Yes, symbols and/or graphic
objects can be grouped and
moved behind/before others
Yes
Yes, find in diagram and flexible
search for object by criteria
Yes
Yes, standard help
Yes, available for free via the
Sybase web site
Yes, because all modules share
the same interface, it is very easy
to transition from data mod-
eling to proces or object modeling
ERwin
No
No
Yes
Yes, but only one level deep
No
No
High degree of control
Yes, but difficult to associate
with specific model objects
Yes, any text can be edited
directly in-place
Yes, but cannot attach them
to model objects. Also, in
logical/physical model,
graphics have to be in the
same place on both diagrams
Yes
Yes
Yes
Yes, both as a part of the reverse
engineering process and on-
demand from a menu. Not
very good with larger models.
Yes, left, center, right, top,
middle, bottom and evenly
spaced horizontally or
vertically.
No, appears to be broken
Yes, symbols and/or graphic
objects can be grouped and
moved behind/before others
No
Yes, but only to find entities/
tables in current diagram
Yes, but line segments tended
to disappear
Yes, advanced on-line tutorial
and product walk-through
Yes, but incomplete
No, since each tool is a completely
separate product, very little is
similar between the model types
Windows Features
These features are specific to the Windows operating systems and the concern is that the
tools will interoperate with other Windows applications seamlessly and have a common
look-and-feel when compared with other software typically found on user workstations.
PowerDesigner ERwin
Object Linking and Yes, both as client and server No
Embedding (OLE)
Cut, Copy and Paste to/from Yes Somewhat. Could paste
windows clipboard between ERwin models, but
not other applications
Drag and drop Yes, only between Yes, using the mouse alone
dialog boxes moves the attribute/column
while Ctrl-mouse copies the
object
Toolbars and dialog boxes Yes, fully customizable Not Windows standard, but
conform to Windows toolbars it is fully customizable
standards.
Field-level Help in Yes No
dialog boxes
Dockable toolbars Yes, fully customizable Yes, fully customizable
Undo/Redo Yes, unlimited No
Multiple Document Interface Yes Yes
(MDI) – more than one
model open at a time
Graphic printing Yes, standard Windows Yes, standard Windows
printing capabilities printing capabilities

Modeling Features
These are advanced modeling capabilities that make some complex modeling tasks possible
and the rest much easier. Note that for model validation, the ERwin Model Validator is a
separate package, and has more capabilities than the PowerDesigner built-in model check
feature. Specifically, it checks for normalization violations.
PowerDesigner ERwin
Menu add-ins Yes, VB scripts can be written Yes, an open API and links
and menu items added with 3rd party vendors to
extend
Conceptual data items Yes, can import lists of data No, must create attribute/
independent of entities items and work with them column in context of
independently entity/table
Domain Hierarchy No Yes, and can drag & drop
domain into entity/table to
create attribute/column
Extended objects in model to Yes, can add user-defined No
describe additional concepts objects with their own meta-
not already in the tool data to any model

Modeled objects independent
of graphic
Merise modeling
Transformation Wizard
Yes, objects can be removed No, only visible objects exist
from all diagrams without in the model.
deleting the object itself
Yes, associations and links No
supported in the CDM
Yes, under Tools -> Denorm- Yes, with a number of
alization we have wizards to predefined denormalization
perform all forms of denor- techniques 9
malization techniques – LDM
and PDM only...(why demor-
nalize a CDM?)

Naming Standards Editor
Naming Standards
Compliance Checker
Datatype Standards Editor
Graphic synonyms or
duplicates of objects
Shortcuts to objects in
other models
Composite view of objects
that contain diagrams
Templates to speed up
model creation
Compare with database
Model Validation
DDL Customization
Volumetrics
Stored Procedures
Triggers
Test Data Generation
Viewer or “read/only” mode
Metadata sharing between
model types
Model Driven Architecture
(MDA)
Event handlers to modify the
object creation process
10
Simulation in the BPM
PowerDesigner ERwin
Yes Yes, more comprehensive
No Yes
No Yes
Yes No
No
Yes
Yes, BPM and OOM objects No
that suport sub-objects have a
compostie view that puts the
diagram inside the symbol
Yes–V10.0 allows for a “Create Yes
Model from Template” using
another model as the template
for a new one (Radio button at
top of New dialog)
Yes, full database synchroniza- Yes, full database synchro-
tion capability, but changes to nization capability,
and from database are separate bi-directional in single step
steps for some actions only. For
instance, table options must
be done one-way
Yes, very powerful model There are reports that provide
checking facility with con- some information.The Model
trolled updates to the model Validator has more function-
ality, but is a separate product
Yes, through definition files There is some control, but
have good control over result- not much
ing DDL appearance.
Yes, comprehensive sizing Yes, complex sizing and
abilities future growth estimation
Yes, can create and reverse Yes, can create them and
engineer them, and make tem- reverse engineer them
plates for common code blocks
Yes, can create and reverse Yes, can create them and
engineer them, and make tem- reverse engineer them
plates for common code blocks
Yes, with good control over No, this is a separate product
datatypes and referential
integrity
Yes, PowerDesigner Viewer is a Yes, Model Navigator is a sep-
separate product with read/ arate product with read/ only
only access to models access to the models and the
ModelMart repository
Yes, because of the common No, there is very limited func-
user interface and underlying tionality to share metadata
meta-model, there are many between the individual products
opportunities to share metadata
between model types
Yes Yes, in ACM
Yes, can use VB code to cause No
additional things to happen
when objects are created on
the diagram
Yes, with 3rd part Simul8 No
integration
Integration with other Modeling Tools
These features allow users to work with multiple modeling tools, either as a transition from
one to another or as a business requirement. Most modeling tools do not have very good
support for integration with other tools, but that there are 3rd party tools available to
convert much of the model information from one format to another.

Data Model PowerDesigner ERwin

Import/Export ERwin Yes/No N/A

Import/Export N/A No/No
PowerDesigner
Import/Export Oracle No/No Yes/Yes
Designer 2000

Process Model PowerDesigner ERwin

Import/Export BPwin No/No N/A

Import/Export N/A No/No
PowerDesigner
Import/Export eb XML Yes/No No/No
Import/Export EasyABC No/No Yes/Yes
Import/Export ERwin No/No Yes/Yes
Import/Export BPSimulator No/No No/Yes
Import/Export Arena
No/No No/Process Flow Diagram
Business Edition
Import/Export IDL format No/No Yes/All except DFD
(IDF0)
Import/Export SIMUL8 Yes/Yes No/No

Object Model PowerDesigner Component Modeler

Import/Export ACM No/No N/A
Import/Export
N/A No/No
PowerDesigner
Import/Export Rational Rose Yes/No No/No
Import/Export XMI com-
Yes/Yes Yes/Yes
mon format

11
 Reporting Features
Both tools have a reporting facility. The basic purpose of this facility is to generate model-level
documentation. ERwin seems to lack some of the higher-end documenting capabilities to be
expected in an enterprise-level modeling tool. PowerDesigner includes multi-model reports
that provide a single report for many models at once. ERwin has a graphic facility to edit the
report layout and save templates for reports.

PowerDesigner ERwin

Basic Reporting Yes Yes

Multi-Model Reporting Yes, models of any type can Yes
be combined into a single
report
Report templates Yes Yes
Include Graphics in Report Yes No
WYSIWYG report layout editor No Yes
Reports directly to Printer Yes Yes
Save Reports as HTML Yes Yes
Graphics in the Reports are Yes Yes
hyperlinked
Save Reports as RTF Yes No
Save Reports as CSV No Yes
Save Reports via DDE to No Yes
other Windows applications

Process Modeling
PowerDesigner
Sybase's PowerDesigner has entered into the Business Process Modeling arena with the BPM
module. The model is a control flow diagram, similar in principle to a UML activity diagram,
but without the technical complexity. It can capture much of the business process information,
and can be extended to support various methodologies (ebXML and BPEL4WS) or to add
simulation functionality (SIMUL8 integration). It supports a CRUD chart (Create, Read,
Update and Delete), Swim Lanes, and organizational units. Since the BPM is integrated into
the rest of PowerDesigner, it has a consistent interface and similar functionality.

BPwin
BPwin is a mature, full-featured process modeling tool, although a completely separate package
from ERwin. From the start it supports Business Process (IDEF0), Process Flow (IDEF3) and
Data Flow (DFD). It supports CRUD (Create, Read, Update and Delete) both as a chart and as
a modeling constraint on other activities. Many diagrams are supported, including Swim Lane,
Organization Charts, Node Tree, Scenario and "For Exposition Only" (FEO) diagrams (useful
when IDEF0 or IDEF3 aren’t descriptive enough). Costing information for the process is
supported in many different forms throughout the diagrams.
Within the tool, the screen/page resembles an architectural or engineering diagram. The graphics
controls are similar to ERwin, with an Explorer pane, dockable toolbars and a main graphic
area, although also limited by lack of an Undo feature.

12
Dimensional Modeling
PowerDesigner
PowerDesigner provides a dimensional model diagram in the PDM. Tables are identified as
Fact or Dimension and the multidimensional hierarchy of dimensions can be maintained.
Data source and transformation information is kept, with shortcuts used to refer to the
source transactional model.

ERwin
ERwin provides the basic functionality to do dimensional modeling, marking tables as fact
and dimension, but without the multidimensional hierarchy capabilities.

Object Modeling
PowerDesigner
In addition to data modeling tasks, PowerDesigner supports object modeling in a variety of
styles, including a generic Object Oriented Analysis and Design (OOA&D) model and three
distinct flavors of XML (BizTalk, DTD and Schema). It fully supports the UML 1.4 standard,
including all of the standard diagrams. Application code can be reverse engineered much like
a database structure, resulting in a diagram of the object structures. That information can be
used to synchronize with the data and business models. Code can be generated in the lan-
guage of choice.

Component Modeler
AllFusion Component Modeler (ACM) is a separate product with a completely different look
and feel to the interface, and the differences are confusing (workspace vs. model). It supports
UML 1.4 and all of the standard diagrams. It also provides for multiple methodologies, such
as the Unified Process from Rational and the Catalysis Process from Computer Associates.
ACM includes its own repository, separate from and incompatible with the ModelMart
repository included with ERwin. ACM does interact with ERwin to share model elements. It
can reverse engineer from and forward engineer to many OO languages.

Repository
Both ModelMart and PowerDesigner’s Repository are intended to provide the capabilities of an
“enterprise” tool, such as version control, permission management, and configuration management.

PowerDesigner Repository
The PowerDesigner Repository was redesigned when PowerDesigner itself was rewritten after
version 6. It is a very abstract database that can handle many types of models without needing
structural changes. It also can be installed on virtually any ODBC database platform, using
no DBMS-specific structures or access methods. This means slower performance, but almost
universal installation capabilities.

ModelMart Repository
Navigator is a read/only viewer product that compliments ERwin and BPwin. It can access ModelMart
as well as the model files themselves. Note that the Component Modeler is not included in this, as it
doesn’t work with ModelMart and does not support a viewer.
The PowerDesigner Viewer is able to accesses the Repository In read/only mode.

13
 PowerDesigner ERwin
Model organization into
Yes Yes
folders
Version control of models
Yes Yes
and model elements
Merge elements from one Yes
Yes
model to another
Consolidate models into the
Yes Yes
repository
Extract models from the Yes Yes
repository
Extract portions of models
Yes Yes
from the repository
Configurations of models Yes Yes
Configurations can be easily No Yes
edited over time
Non-proprietary tables Yes Yes
Multiple repositories can
co-exist Yes No

User management, security,

permissions Yes Yes

User groups supported Yes Yes

Any document can be stored
Yes No
in the repository

14
Conclusion
In conclusion, both of these data modeling tools are very popular and provide the user with
a many useful functions. However, PowerDesigner has a more sophisticated user interface
and functions that are easier to find and use for the novice. With its advanced control over
graphics and its stronger reporting facility, PowerDesigner produces better quality documen-
tation than ERwin. ERwin has a good handle on the databases it supports, but PowerDesigner
starts with better support and lets the user customize the database definitions. ERwin has
some sophisticated features when dealing with standard domains and naming conventions
that are superior to PowerDesigner. PowerDesigner is stronger in the dimensional modeling
area, having more functions specifically for handling multi-dimensional hierarchies.
ERwin has made strides in loosening their link between logical and physical models, but
still the lack of true conceptual modeling is a detriment. The fundamental differences in
philosophy concerning conceptual, logical and physical models and the limitations ERwin
enforces concerning attributes and data items give PowerDesigner an edge when creating
business-oriented models.
BPwin is a more mature tool than the BPM module and does a good job of modeling
business processes and functions, but it is a separate package.
The ACM is disappointing, with a poor user interface and a steep learning curve when
moving from the other CA tools. It is also crippled by not being able to share the same
repository as the other tools. If CA can somehow merge their modeling tools together,
things would be much better.
Although they both share the ability to integrate multiple models, only PowerDesigner was
truly able to share objects between models. The bottom line is that PowerDesigner is a tightly
integrated suite of modules with a strong common user interface while CA’s tools are obviously
from different sources without any consistency between them.

15
 Appendix
Glossary of Terms

BPEL4WS Business Process Execution Language for Web Services pro-

vides a language for the formal specification of business
processes and business interaction protocols. By doing so, it
extends the Web Services interaction model and enables it to
support business transactions. BPEL4WS defines an interop-
erable integration model that should facilitate the expansion
of automated process integration in both the intra-corporate
and the business-to-business spaces.
CODASYL COnference on Data SYstems Languages. Pronounced “code-
a-sill”, CODASYL is an organization founded in 1957 by the
U.S. Department of Defense to develop computer program-
ming languages.
CODASYL was responsible for developing COBOL. The
organization no longer exists, but the term CODASYL is still
used sometimes to refer to COBOL.

CSV Comma delimited file format contains only text values in a

columnar layout, representing rows and columns of data,
each element separated by commas and each row terminated
by a carriage return.

DBMS DataBase Management System. This is sometimes referred to

as the “target platform” or “target server” in the two tools.
This is the source of reverse engineering tasks and the eventual
target for objects created in the model.

DDE Dynamic Data Exchange. This is a Windows data interchange

functionality which lets two applications transfer data directly
between them, bypassing intermediate files and clipboards.
DDL Data Description Language. This is a set of instructions
passed to a SQL compliant database engine to create, delete
or alter the physical structures in a database.

DML Data Modification/Manipulation Language. This is a set of

instructions passed to a SQL compliant database engine to
affect the contents of tables by inserting, updating or deleting
sets of records.
DTD Document Type Definition – A group of statements that
define XML element names and their attributes specifying the
rules for combinations and sequences. It is the DTD that
defines which elements can or cannot be inserted in the given
context within an XML document. See also XSD.
ebXML BPSS The "e-business" Business Process Specification Schema is a
set of specifications for standardizing XML, providing a stan-
dard framework by which business systems may be config-
ured to support execution of business collaborations consist-
ing of business transactions.
Gane & Sarson A methodology created by former Yourdon associates to build
Methodology on the Yourdon/DeMarco methodology. Although the sym-
16 bols differ significantly in the graphic display, the same basic
information is stored in the model.
HTML HyperText Mark-up Language. HTML is used extensively on
the Internet as a method to embed graphic properties into
streams of text. In documentation terms, HTML can be used
for rudimentary layout control of a document’s contents.

IDEF0 Integration DEFinition for Information Modeling. An IDEF0

model takes a real-world activity and represents it as a
square-cornered box labeled with a verb phrase.
If the real-world activity has resources it uses, they are noted
as arrows in the IDEF0 diagram as follows:
Things consumed enter the box from the left side.
Things used in but not consumed enter the box from the
bottom.
Things used to ensure or enforce enter the box from the top.
The result of the real-world activity is that something is pro-
duced. This is represented on an arrow leaving from the right
side of the box.

IDEF1X IDEF1X is a method for designing relational databases with a

syntax designed to support the semantic constructs necessary
in developing a conceptual schema. A conceptual schema is a
single integrated definition of the enterprise data that is unbi-
ased toward any single application and independent of its
access and physical storage. IDEF1X is most useful for logical
database design after the information requirements are
known and the decision to implement a relational database
has been made. Hence, the IDEF1X system perspective is
focused on the actual data elements in a relational database.
If the target system is not a relational system, for example, an
object-oriented system, IDEF1X is not the best method.

IDEF3 IDEF3 is based loosely upon situation theory. According to

situation theory, the world contains several kinds of things:
objects, situations, activities, processes, and process activations.
Objects are simply things like people, numbers, machines,
etc. that are not situations, i.e., concrete or abstract objects
that have properties and stand in relations to other objects
in situations. A situation is a real world event across some
portion of space and time. For example, a meeting between
8:00am and 8:30am yesterday at a specific location is a
situation. It comprises some set of objects (the attendees),
which have properties and stand in certain relations to each
other in the situation.
In most physical systems one observes multiple occurrences
of situations that are similar in some respect. In such cases,
the similar situations are said to be of the same type.
Situation types are thus general, repeatable patterns that can
be exhibited by many different specific situations. The notion
of an activity in IDEF3 is identified with an instance of a
situation type.

17
 Merise Merise is a French conceptual modeling methodology. In
Merise an association is used to connect several entities that
each represent clearly defined objects, but are linked by an
event which may not be so clearly represented by another entity.
OLAP On-Line Analytical Processing. This has been called
“Reporting on steroids” and involves being able to change the
point of view of the report, for instance, initially looking at
product by week, then switching quickly to product by geo-
graphic region. Another example would be “zooming in” on
data by specifying increasingly tight limits on the query ranges,
again rapidly. Most operations in OLAP happen in sub-
second time frames.
OLTP On-Line Transaction Processing. These are the “legacy systems”
that run the day-to-day operations of any business. They are
large, old, complex and critical to the company. Those attributes
are the primary reasons that we model data in the first place.
OOA&D Object Oriented Analysis and Design. This is a practice of
modeling the system functions and data at the same time,
demonstrating the expected interactions between the system,
its users and with other systems, documenting internal func-
tional dependencies, timing, static and transient data structures.
Repository A repository stores model information in a centralized database,
allowing the user to use it as a library of models. Expected
functions include checking in, checking out, security, merging,
mass update, impact analysis and version control.
Reverse Engineering The process of capturing information from a down-stream
target platform and populating a model at a desired level.
For example, a physical model might be initially created by
scanning an existing database and creating model objects for
each table, column or index found. The phrase would be, “the
database was reverse engineered into the model”.
RTF Rich Text Format. Common word processing file format
which preserves all formatting information and any images
imbedded into the document.

SQL Structured Query Language. Pronounced either “Ess-Que-Ell”

or “Sequel”, this is the formal language that most relational
databases understand. It include DDL (database structural
change statements) and DML (database content change
statements).
SSADM Structured Systems Analysis and Design Method. This
method differs only slightly in presentation from Yourdon/
DeMarco, OMT or Ganes & Sarsen. The basic information
stored in the model remains the same.
XSD XML Schema Definition - from the World Wide Web
Consortium (W3C), specifies how to formally describe the
elements in an XML document. This description can be used
to verify that each item of content in a document adheres to
the description of the element in which the content is to be
placed. See also DTD.
18
UML Unified Modeling Language. This is a language for specifying,
visualizing, constructing, and documenting the artifacts of
software systems. It simplifies the complex process of software
design, making a “blueprint” for construction. The UML def-
inition was led by Rational Software’s industry-leading method-
ologists: Grady Booch, Ivar Jacobson, and Jim Rumbaugh.
UML Diagram The individual diagrams found in the UML standard are:
Activity - describes the flows driven by internal processing
from a start point to several potential end points.
Class – shows a set of classes, interfaces, and their relationships
that together represent the logical static design view of a system.
Collaboration - shows objects performing a particular goal
(a functionality of the system)
Component - shows the organizations and dependencies
among components of a system.
Deployment - shows the physical configuration of run-time
processing elements (nodes) on an instance level. The nodes
contain instances of component that will be deployed into
database, application or web servers
Object - describes the structure of model as instances: it
represents instances of class, association, and dependencies.
Sequence – shows object interactions in a time sequence.
Statechart - shows the behavior of classes in response to
external stimuli, depicting the dynamic flow of control from
state to state within a system.
Use Case – shows interactions between users and a system
being designed.
Volumetrics The practice of fairly accurately determining the size of a set
of database objects during the design phase based on certain
factors (number of columns and indexes, etc.) and estimated
row counts. Algorithms are used to calculate average row
width, index space and database overhead for system catalogs.
Reports can then be generated that let a DBA create initial
device allocations for the proposed database.

XML EXtensible Mark-up Language. Very similar to HTML, being

based on tags placed into a text stream/file. In HTML, the
tags serve to format the appearance of the text while in XML
they provide data compartmentalization and organization.
XML is used to make data transmitted between systems
more readable and consistent.

19
 About the Author
Michael Nicewarner is a data modeler and database designer with over 12 years of experience
in data processing, specializing at times in mainframe development, configuration management,
data administration and database administration. Mike has used S-Designor, PowerDesigner,
ERwin, Popkin’s System Architect, Embarcadero’s ER/Studio and a host of other modeling
tools. This background gives him a unique perspective and a strong voice in the modeling
community.

Acknowledgements
First and foremost, thanks to my wife who doesn’t understand a thing that I do, but still
allows me to “play” on the computer endlessly. Thanks to the PowerDesigner team at Sybase
and the ERwin team at Computer Associates for their patience and wonderful assistance.
Finally, thanks to my friends and co-workers who have allowed me to use them as sounding
boards and proofreading services.

20
International Contacts
Argentina Korea
+5411 4313 4488 +82 2 3451 5200
Australia Malaysia
+612 9936 8800 +603 2142 4218
Austria Mexico
+43 1 504 8510 +5255 5093 8500
Belgium Netherlands
+32 2 713 15 03 +31 20 346 9290
Brazil New Zealand
+5511 3046 7388 +64 4473 3661
Bulgaria Nigeria
+359 2 986 1287 +234 12 62 5120
Canada Norway
+905 273 8500 +47 231 621 45
Central America Panama
+506 204 7151 +507 263 4349
Chile Peru
+56 2 330 6700 +511 221 4190
China Philippines
+8610 6856 8488 +632 750 2550
Colombia Poland
+57 1 218 8266 +48 22 844 55 55
Croatia Portugal
+385 42 33 1812 +351 21 424 6710
Czech Republic Puerto Rico
+420 2 24 31 08 08 +787 289 7895
Denmark Romania
+45 3927 7913 +40 1 231 08 70
Ecuador Russian Federation
+59 322 508 593 +7 095 797 4774
El Salvador Slovak Republic
+503 245 1128 +421 26 478 2281
Finland Slovenia
+358 9 7250 200 +385 42 33 1812
France South Africa
+33 1 41 91 96 80 +27 11 804 3740
Germany South Korea
+49 69 9508 6182 +82 2 3451 5200
Greece Spain
+30 1 98 89 300 +34 91 749 7605
Guatemala Sweden
+502 366 4348 +46 8 568 512 00
Honduras Switzerland
+504 239 5483 +41 1 800 9220
Hong Kong Taiwan
+852 2506 6000 +886 2 2715 6000
Hungary Thailand
+36 1 248 2919 +662 618 8638
India Turkey
+91 22 655 0258 +90 212 325 4114
Indonesia Ukraine
+62 21 526 7690 +380 44 227 3230
Israel United Arab Emirates
+972 3 548 3555 +971 2 627 5911
Italy United Kingdom
+39 02 696 820 64 +44 870 240 2255
Ivory Coast Venezuela
+225 22 43 73 73 +58 212 267 5670
Japan Asian Solutions Center
+81 3 5210 6000 +852 2506 8700
Kazakstan
+7 3272 64 1566
For other Europe, Middle East, or Africa inquiries:
+33 1 41 90 41 64 (Sybase Europe)
For other Asia Pacific inquiries:
+852 2506 8700 (Hong Kong)
For other Latin America inquiries:
+925 236 6820

Sybase, Inc.
Worldwide Headquarters
One Sybase Drive
Dublin, CA 94568-7902 USA
Copyright © 2004 Sybase, Inc. All rights reserved. Unpublished rights reserved under U.S. copyright laws. Sybase, the Sybase logo, and
Tel: +800 8 SYBASE PowerDesigner are trademarks of Sybase, Inc. All other trademarks are property of their respective owners. ® indicates registration in the
www.sybase.com United States. L02151 1/04