PowerDesigner 9.5 - Sybase

QUARTERLY NEWSLETTER
PowerDesigner ®
Blueprint
SEPTEMBER
Newsletter
2002 / ISSUE 7
EDITORIAL
Dear Blueprint reader,
PowerDesigner 9.5 officially launched on
September 19, 2002 at the Gartner Application
Development Summit at the Grand Cypress
Hotel in Orlando, Florida and created quite a
buzz with analysts and IT professionals. We’re
very excited about the new functionality 9.5
offers — supporting all nine UML diagrams,
enhanced data modeling capabilities and much
more! I encourage you to return the enclosed
business reply card or download the free evaluation
copy and see for yourself!
In our feature article, Creating Web Services with
PowerDesigner 9.5, Xiao Wang, PowerDesigner’s
Chief Architect, simplifies the complexities of
Web Services using PowerDesigner 9.5. If you
know how to create a class and a method, you
know how to create Web Services! You can use
PowerDesigner to design, create, reverse engineer
and document Web Services. You will learn
how you can create libraries of Web Service
components for reuse. You will also learn how to
manage versions of Web Services using the
Repository. Check out this very valuable article!
Also in this issue, David Dichmann,
PowerDesigner Product Manager, has provided a
concise listing of the features and benefits of
PowerDesigner 9.5, based on each role in the
development lifecycle.
In the article, PowerDesigner Profile, Gabriel
Kevorkian, Software Engineer for PowerDesigner,
documents the enhancements made in
PowerDesigner 9.5, improving on it’s long history
of customizable options, making it the most
flexible tool on the market! Read about how the
new “Free Model” will allow you to represent any
domain-specific system by defining your own
semantics for model-to-system mapping.
I’d also like to encourage you to check out the
PowerDesigner product page, where you will find
several 5-20 minute video demonstrations of the
features of PowerDesigner. Visit
www.sybase.com/powerdesigner and click on
Demonstration Videos, these demos have been
created based on job function and will prove to
be very valuable tools to help you become more
familiar with the benefits of PowerDesigner.
If this is your first issue of Blueprint, please check
out www.sybase.com/powerdesigner for the
online versions of previous issues.
Regards,
Laurie Barker
lbarker@sybase.com
PowerDesigner Marketing Program Manager
Sybase e-Business Division
Creating Web Services with
PowerDesigner 9.5
By Xiao Wang, PowerDesigner Chief Architect, Sybase Inc
WEB SERVICES ALLOW YOU TO EXPOSE EXISTING OR
NEW FUNCTIONALITIES IN A STANDARD FORMAT.
USERS MAY ALSO ACCESS APPLICATIONS FROM ANY
LOCATION.
POWERDESIGNER 9.5 INTRODUCES COMPLETE
WEB
SERVICES DESIGN AND GENERATION FOR BOTH
MICROSOFT .NET ® AND JAVA TM . WITH
POWERDESIGNER ® 9.5, YOU CAN CONCENTRATE ON
THE DESIGN OF YOUR WEB SERVICES AND LET
POWERDESIGNER GENERATE ALL THE NECESSARY
IMPLEMENTATION ARTIFACTS.
WEB SERVICES OVERVIEW
A Web Service is an interface that describes a collection
of operations that are accessible on the network
through SOAP messages.
A Web Service’s interface and deployment location
(optional) are described by WSDL. WSDL is a XML
document that declares the data types, messages,
port types and ports (optional). WSDL allows a user
to understand which format of the SOAP message
should be sent to invoke the service and what is the
expected return message format.
To allow users to find desired Web Services, a service
provider can publish a WSDL in a UDDI registry,
and then users can search a Web Service using the
UDDI registry.
To invoke a Web Service, users can send a SOAP message
to the access point URL where the Web Service
is deployed or use a proxy class that simplifies the
invocation. A SOAP message is a XML document.
POWERDESIGNER’S WEB SERVICES
FEATURES
PowerDesigner 9.5 allows you to: create new Web
Service components, reverse engineer WSDL to create
Web Service components, browse UDDI to
search WSDL, generate WSDL from Web Service
component definition, generate server side code for
.NET (C# and VB .NET), generate client proxy for
.NET, generate server side code for Java (JAX-RPC
and JAXM) and generate client proxy for Java.
To design Web Service components, PowerDesigner
uses UML Class Diagrams, Component Diagrams
and Deployment Diagrams. A Web Service is represented
by a Component in a Component Diagram.
A deployed Web Service is represented by a
Component Instance in a Deployment Diagram
CREATING WEB SERVICE COMPONENTS
There are five steps to creating a Web Service component.
The first step is creating an Object-Oriented
Model (OOM). You can choose one of the following
languages: C#, Visual Basic .NET or Java. An
Extended Model Definition (XEM) for WSDL is
automatically attached to the model. It defines
WSDL generation templates and Extended Attributes.
The second step is creating a class. It is recommended
to create a Package first then create the class under
the package.
The third step is converting the class to a Web
Service component using the Web Service wizard.
You can right click on the class then select the Create
Web Service Component command or select the
class then choose the Tools> Create Web Service
Component command. FIGURE 1 is an example of
the Web Service wizard. The Web Service type could
be interface or implementation. Interface means
that you only want to define the Web Service interface
and generate the WSDL. For .NET, the component
type is Standard and the Web Service will be
implemented by an .asmx file. For Java, the component
type could be Standard, Servlet or Stateless
Session Bean. The Java Standard Web Service will be
implemented using JAX-RPC. The Servlet Web
Service will be implemented using JAXM. The
Stateless Session Bean Web Service will be implemented
using the Web Services for J2EE (JSR109)
specification. At the end of the wizard, a Component
and a Class are created. FIGURE 2 is an example of
Component symbol in Component Diagram.
FIGURE 1 Web Service wizard.

Stock Quote
Implementation
FIGURE 2 Component symbol.
The fourth step is adding a web method. You need to
create a new Operation, open the property sheet of
the operation, click on the Web method check box,
define parameters and return type and write code to
implement the operation. FIGURE 3 is an example of
implementation for the GetStockQuote web method.
FIGURE 3 Example of implementation for the
GetStockQuote web method.
The last step is customizing the WSDL generation.
You can customize the parameters and the return
value’s WSDL data types, the operation extended
attributes and the component properties and extended
attributes. To verify the generated WSDL, you can
open the WSDL tab of the Component property
sheet. You can let PowerDesigner generate the WSDL
or define your own (user-defined). If a Web Service
component is reverse engineered from a WSDL, the
original WSDL will be preserved. FIGURE 4 is an
example of generated WSDL.
FIGURE 4 Example of generated WSDL.
You can preview the generated implementation code
in the Preview tab of the Class property sheet.
You can model a deployed Web Service component
using Deployment Diagram, Node and Component
Instance. You can define the server URL in Node and
the service URL in Component Instance.
REVERSE ENGINEERING WSDL
A WSDL could define the Web Service interface only
or define the interface and the access point URL. The
Web Service interface can be used by multiple service
providers to offer the same service but with different
implementation and access points. If you have a
WSDL document file path or URL, you can reverse
engineer it to create a Web Service component then
defines your own implementation or keep the Web
Service component in a library for future use. If you
don’t know where to find an interesting WSDL, you
can use the UDDI browser to search WSDL in a
UDDI registry.
To reverse engineer a WSDL, you need to create an
OOM with one of the following the languages: C#,
VB .NET or Java. Then select the Language>Import
WSDL command, enter the WSDL file path or URL.
After reverse engineering, a Component will be created
in Component Diagram and a Class will be created
in Class Diagram. The created class will only contain
the signature of the operations of the Web Service. If
you want to implement the Web Service, you need to
define the implement code of these operations.
SEARCHING WSDL IN UDDI REGISTRY
If you want to search WSDL registered in UDDI registry,
open the Import WSDL window, click on the
Browse UDDI button. The Browse UDDI window,
shown in FIGURE 5, allows you to select UDDI operator,
the search criteria and the search type. You can
search by business entity name, service name or
WSDL name. The WSDL can be previewed.
FIGURE 5 Browse UDDI window.
GENERATING WEB SERVICES FOR .NET
For .NET server side code, PowerDesigner generates
an .asmx file. The Web Service implementation class
could be generated inside the .asmx file or outside.
The implementation class could be in C# or VB .NET.
You can preview the .asmx file and the implementation
class code in the Preview tab of the Class property
sheet. FIGURE 6 is an example of .asmx file for C#.
FIGURE 6 Example of .asmx file for C#.
PowerDesigner can also generate a client proxy class
to simplify the invocation of the Web Service. To generate
the client proxy class, PowerDesigner uses the
wsdl.exe program that comes with Visual Studio .NET.
To generate the WSDL, the server side code and/or
the client proxy, select the Language>Generate C#
Code or Language>Generate VB .NET Code command.
If you want to generate client proxy, you can
select the Generate Web Service client proxy option
in the Tasks tab. FIGURE 7 shows the available Tasks
for the generation. You can compile the C# or VB
.NET code if the classes are not generated inside the
.asmx files. To compile C# or VB .NET files, you have
to define a variable CSC or VBC to indicate where is
the csc.exe or vbc.exe command.
To deploy the Web Service, copy the .asmx file and
the class files under the IIS directory
C:\Inetpub\wwwroot\, where is the name of the
package. To test the Web Service, enter the
URL in the browser:
http:////.asmx
FIGURE 7 Web Service generation tasks.
GENERATING WEB SERVICES FOR JAVA
If the Web Service implementation type is Standard,
PowerDesigner uses JAX-RPC for the implementation.
If the implementation type is Servlet,
PowerDesigner uses JAXM for the implementation.
If the implementation type is Stateless Session Bean,
PowerDesigner uses Web Services for J2EE (JSR109)
specification for the implementation. JSR109 is not
finalized yet.
JAX-RPC defines RPC type invocation for Web
Services. It is easy to develop and use. But it is limited
to simple message formats to avoid complex
Objects/XML mapping. JAXM based Web Service
components give you the flexibility to handle complex
message structures.
To use JAX-RPC or JAXM, you need to install the
Java Web Services Developer Pack (JWSDP). You can
download it from Sun Microsystem’s web site. To
deploy JAX-RPC or JAXM Web Service components,
you will need a server that supports JAX-RPC or
JAXM. JWSDP ships with Apache Tomcat that supports
JAX-RPC and JAXM.
For JAX-RPC based Web Service component, you
only need to implement the web method code. To
Continued on page 3
2

PowerDesigner
FEATURES & BENEFITS
By David Dichmann,
PowerDesigner Product Manager
PowerDesigner offers the following features and benefits
for each role in the development lifecycle:
For Business-centric Managers
PowerDesigner enables you to model business-driven
application using simple, non-IT, and intuitive techniques.
PowerDesigner is the easy to use and learn way to model
and design business processes and maximize collaboration
with your IT department.
With PowerDesigner Version 9.5, you will:
! Document and model your business and business
processes using business-oriented diagrams.
By using this non-IT, non-technical, intuitive, business-centric
model, you focus on the business
processes themselves, before handing this off to the
IT professionals who will incorporate the technical
details.
! Work in a state-of-the-art, graphical, highly intuitive
user interface, with new advanced graphic capabilities
that dramatically improve the expressiveness
of the resulting diagrams. This GUI makes
PowerDesigner easy to learn, easy to use, and a very
powerful medium for communicating ideas across
multiple disciplines.
! Centralize all your work in a secure, enterprise-class
repository. The repository provides a global view of all
models, shared across all team members, increasing
collaboration throughout the enterprise. Store,
manage, version and share all your business
models throughout the enterprise.
! Take advantage of the business process model’s
advanced features, like the ability to track Data flows,
CRUD Matrix and data model integration, UML model
generation and ebXML support, both generation and
reverse engineering. By leveraging the business models
everywhere, IT will be more efficient in developing
projects or applications that meet business goals.
For IT-centric Managers:
PowerDesigner streamlines collaboration, accelerates
the learning curve and reduces time and cost of software
development. PowerDesigner is a single, easy-to-use,
standards-based environment that will capture business
needs and requirements and effectively model the software
that meets them.
With PowerDesigner Version 9.5, you will:
! Use multiple standard modeling techniques for both
IT-centric and Business-centric information in one
modular, integrated package. Combining UML with
non-UML business and data modeling streamlines
communication between the business and IT.
! Use comprehensive and highly iterative bi-directional
model synchronization and linking capabilities to
streamline response to change, anywhere in the
development lifecycle, flattening the change cost
curve.
! Work in a state-of-the-art, graphical, highly intuitive
user interface. With PowerDesigner’s short learning
curve, users will be productive right away.
! Centralize all your work in a secure, enterprise-class
repository. The repository provides a global view of all
models, shared across all team members, increasing
collaboration through-out the enterprise.
For IT-centric Technical Staff – Developer:
PowerDesigner provides for increased development productivity
through practical, results-driven UML.
PowerDesigner’s code generation and synchronization
facilities, including support for Java and .Net, ensure the
model and development efforts are always the same.
With PowerDesigner Version 9.5, you will:
! Work in an easy to use, simplified, practical environment
for UML, with all 9 diagrams and powerful
extension mechanisms supported. A practical and
applied approach to UML modeling allows the developer
to focus on results, not concepts. This will
reduce the tendency to over analyze before getting to
the desired stage – writing and deploying code
and applications.
! Reverse-engineer existing systems with support for
Java, XML, PowerBuilder and all manner of Web
Services. Being able to document and understand
existing systems quickly makes integration or
enhancement projects easier to manage, scope and
execute.
! Use complete, round-trip code generation for multiple
environments including the Java (J2EE with support
for EJB, JSP and servlett) and the .Net (WSDL and
UDDI support) platforms. With this, you have support
for both leading e-Business platforms, and you have
significantly improved Java developer productivity.
You may also model heterogeneous environments
across multiple technologies.
! Use your favorite development environments through
integration with popular IDEs and Application Servers.
Continued on page 4
Creating Web Services with PowerDesigner 9.5, continued...
generate the WSDL, the server side code and/or the
client proxy, select Language>Generate Java Code,
select the Generate WSDL using XRPCC tool (server
side) and/or the generate Web Service proxy code using
XRPCC tool command (SEE FIGURE 8). The XRPCC
command is a tool of JWSDP. It can generate server
side code or client proxy for JAX-RPC. To deploy the
generated Web Service, you need to create a .WAR file
that contains all the generated files and deploy the
.WAR file in a server that supports JAX-RPC
(ex: Apache Tomcat).
FIGURE 8 JAX-RPC generation tasks.
For JAXM based Web Service component, you need to
implement the onMessage operation. The onMessage
operation will take the input SOAP message, process it,
construct a return message as described in WSDL and
return the message. To generate the WSDL and the
JAXM Web Services, select the Language>Generate
Java Code command, select the Build Web
Components, Create Web Application WAR command
(SEE FIGURE 9). This command compiles the JAXM
servlet code and creates a WAR file. To deploy the
JAXM servlet, you can deploy the WAR file in a server
that supports JAXM, (ex: Apache Tomcat).
FIGURE 9 JAXM generation task.
Since the JSR109 specification is not finalized, it is not
possible to use the Stateless Session Bean based Web
Service component.
FUTURE ENHANCEMENTS
The Web Services for J2EE (JSR109) specification will
be available soon. It will allow you to use a Stateless
Session Bean as a Web Service implementation artifact.
PowerDesigner 9.5 comes with a non-certified version
of JSR109 support based on an early version of the
specification. When the specification is finalized, a
maintenance release will be issued.
Future versions of PowerDesigner will also support
Web Services orchestration standards.
CONCLUSION
PowerDesigner 9.5 simplifies Web Services design and
implementation. If you know how to create a class and
a method, you know how to create Web Services! You
can use PowerDesigner to design, create, reverse engineer
and document Web Services. You can create
libraries of Web Service components for reuse. You can
also manage versions of Web Services using the
Repository.
3

FEATURES & BENEFITS Continued from page 2
By having support for leading IDEs and Application
Servers you have a choice in environments and are
not locked into a single vendor solution.
! Use data modeling integrated with UML, including
design-time support for Object/Relational mapping.
This allows management and the team to
leverages data models in business logic design as
well as facilitates object/relational mapping, or
persistence management, for the business logic.
For IT-centric Technical Staff –Database
Developer and Administrator
PowerDesigner increases database manageability,
facilitates database maintenance and increases ability
to change. PowerDesigner boosts productivity through
effective database design with complete DDL or change
script generation.
With PowerDesigner Version 9.5, you will:
! Create database designs using iterative multi-level
design. By having a separate models for the fully
normalized formal data-analysis, the database
independent logical models and a separate model
for the optimized physical schema, you will be able
to create more robust database systems.
! Have support for over 40 different types and versions
of leading relational databases. Multiple
database support not only ensures openness, but
also allows for heterogeneous database environments
to be modeled in a single tool, leading to
greater understanding and control over the enterprise
database architecture. Models may be linked
to reflect cross-database and cross platform
dependencies. Custom support for each database
gives faster, easier database system deployment.
! Reverse-engineer existing database systems for all
supported RDBMS or with generic support for practically
any RDBMS in production. Use this for complete
database systems understanding when documentation
does not exist, or for incorporating
changes made outside the model back into an
existing design to ensure 100% accuracy between
the models and the production environment.
PowerDesigner Profile
By Gabriel Kevorkian, Software Engineer
! Work in an easy to use, simplified, practical environment
for physical database design, complete
with advanced productivity wizards for common
tasks like denormalizing tables and columns,
defining views, creating indexes, triggers, and
more. A practical and applied approach to data
modeling allows you to focus on results, not
concepts.
! Use complete, round-trip database object generation,
which provides greater flexibility when
deploying iterative design changes to a running
production server without any loss of existing data,
while respecting the changes made to the database
server outside the model.
! Use data modeling integrated with UML, including
design-time support for Object/Relational mapping.
This allows management and the team to
leverages data models in business logic design as
well as facilitates object/relational mapping, or
persistence management, for the business logic.
POWERDESIGNER V9.5 BUILDS UPON THE EXISTING
METAMODEL EXTENSION CAPABILITIES OFFERED BY
PREVIOUS VERSIONS AND NOW PROVIDES A FULL-
FLEDGED METAMODEL PROFILING FUNCTIONALITY THAT
GOES BEYOND THE STANDARD UML PROFILE AND IS
MADE AVAILABLE TO ALL MODULES (CDM, PDM,
OOM...). THIS FEATURE TAKES ON A PARTICULAR
SIGNIFICANCE WITH THE NEWLY RELEASED FREE
MODEL AS IT ALLOWS YOU TO REPRESENT ANY
DOMAIN-SPECIFIC SYSTEM BY DEFINING YOUR OWN
SEMANTICS FOR MODEL-TO-SYSTEM MAPPING.
UML PROFILE
The idea of profile as expressed in the UML specification,
is to allow the UML metamodel to be customized
to address domain-specific needs. A UML
Profile is basically a grouping of additional properties
(a.k.a. tagged values) and constraints
(expressed in OCL (object constraint language)
that can be applied to instances of the UML metaclasses.
UML defines the concept of stereotype as a
metaclass subtyping mechanism that allows metaclass
extensions to be applied to model elements on
a per-instance basis.
POWERDESIGNER PROFILE
PowerDesigner 9 offered a metamodel extension
mechanism through the XEM/XOL/XDB target
definitions. Extended attributes (UML tagged values)
provided a way of extending concrete metaclasses
(ie instantiable metaclasses). Once a target
was associated with a given model, these extended
attributes would become available to all instances of
the corresponding metaclasses. In other words,
XEM/XOL/XDB definitions provided an implicit
stereotyping mechanism for adding extended
attributes to model elements. The ability to associate
more than one XEM with a given model somewhat
addressed the need for applying more than
one stereotype to a given element although this
could not be done at the instance level.
In PowerDesigner 9.5, the structure of the target
definitions has been vastly improved in order to
enable metamodel extensions to be defined with
respect to any metaclass, whether its abstract or
concrete. Extensions defined with respect to an
abstract metaclass are made available to the
instances of the metaclass' concrete descendants.
Extensions that do not bear any relevance for a
given metaclass are simply ignored (eg. custom
symbols defined for non-visible objects).
PowerDesigner's unified meta-extension framework
facilitates the definition of profiles through an
intuitive interface that groups all the extensions by
metaclass or meta-extension container. You only
need to add the metaclass of your choice under the
profile node using the Add metaclass...selection
dialog and then right-click on the metaclass to
define the desired extension(s).
FIGURE 1 Defining meta-extensions.
Meta-extensions fall into two categories: standard
extensions that actually extend the metamodel by
adding structure or behavior to model elements
and meta-extension container extensions that
define groupings of standard extensions to be
applied on a per-instance basis. Extended attributes,
Custom symbols, Custom Checks, Templates
and Generated Files fall in the former category
whereas Stereotypes and Criteria belong to the latter.
STANDARD META-EXTENSIONS
Extended attributes are properties that correspond
to UML tagged values. They may be associated with
a user-defined data type.
FIGURE 2 Extended attribute.
Meta-extensions fall into two categories: standard
extensions that actually extend the metamodel by
adding structure or behavior to model elements
Continued on page 5
4

PowerDesigner Profile, continued...
and meta-extension container extensions that
define groupings of standard extensions to be
applied on a per-instance basis. Extended attributes,
Custom symbols, Custom Checks, Templates
and Generated Files fall in the former category
whereas Stereotypes and Criteria belong to the latter.
Custom symbols are formats that are to be
applied to the symbols of the objects they are
defined for. They are especially useful when
defined under a stereotype or a criterion for visually
differentiating objects in a diagram.
FIGURE 3 Custom symbol.
Custom checks are VBScript extensions to the
standard "Check model" functionality. They allow
for the enforcement of domain-specific constraints
upon a model.
FIGURE 6 Generated File.
META-EXTENSION CONTAINERS
In PowerDesigner, stereotypes are tightly coupled
with metaclasses through a 1-1 association (UML
defines a weaker relationship between stereotypes
and metaclasses based on a delegation mechanism
that allows a given stereotype to be applied to
instances of unrelated metaclasses). A stereotype
may be derived from another stereotype that
extends the same metaclass or one of its ancestors.
Applying a stereotype to a given element provides
it with all the extensions defined for the given
stereotype and its ancestors. Hence, common
extensions may be factored out at an abstract level
and reused through stereotype inheritance.
Custom tools may be defined as part of a stereotype
specification in order to let users create
stereotyped objects using the tool palette.
FIGURE 8 Criterion.
an ancestor metaclass is redefined, the new definition
shadows the original. The same principle
holds true for extension defined on stereotypes.
Stereotypes are considered to be stronger than criteria.
In other words, in case of a conflict between
two extensions, the one defined under a stereotype
overrides the one defined under a criterion.
1. determine the set of extensions
defined by the corresponding
metaclass (metaclass
inheritance)
2. determine the set of extensions
provided by the satisfied
criteria.
3. determine the set of extensions
defined by the corresponding
stereotype, if any
(stereotype inheritance)
4. merge the sets derived in
step 1 through 3 with each set
overriding the previous one.
TABLE 1 Steps for determining the set of
extensions that apply to a given model element.
FIGURE 4 Custom check.
Templates can be thought of as calculated attributes
used mainly for generation purposes but also
for defining criteria and name-code conversion
scripts. Templates are defined in GTL
(PowerDesigner’s Generation Template
Language).
FIGURE 5 GTL Template.
Generated Files define files to be generated as part
of the code generation process. Their template
content is specified in GTL.
FIGURE 7 Stereotype.
Criteria are a dynamic extension mechanism, in
contrast with the stereotyping mechanism that
may be considered as static, as the stereotype of a
model element is unlikely to change over time.
They are defined as arbitrarily complex conditions
based on attribute values and object relationships.
These conditions are expressed in GTL and may be
defined in terms of existing templates. One of the
most spectacular uses of criteria is coupled with
custom symbols as the symbol format is automatically
synchronized with the corresponding object,
depending on which criterion is satisfied. They are
also heavily used for generation purposes as in the
Java object language definition.
EXTENSION MECHANISM
The metamodel extension mechanism supports
inheritance both at the metaclass level and though
stereotype inheritance. If an extension defined in
CONCLUSION
The profiling capability introduced in
PowerDesigner v9.5 greatly enhances its customizability
and makes it the most flexible tool on the
market today in terms of pure modeling.
Although PowerDesigner doesn't support OCL at
this point, it does allows constraints to be defined
in terms of VBScript-based custom checks and
actually augments the set of extensions provided
by the UML profile with GTL templates and generated
files for defining model-to-code mappings.
As far as the actual extension mechanism is concerned,
PowerDesigner not only provides a UMLlike
stereotyping mechanism but introduces the
ability to define criteria that circumvent stereotype
limitations and offer an extremely powerful way of
inducing dynamic structure and behavior on
model elements.
5

Check IT
OUT
Because your TIME is more
LIMITED than ever, we have created
a series of technical VIDEO DEMOS
based on specific job functions.
Each video is a self-running
executable that runs from 5-20 minutes
and demonstrates some of the
key features of PowerDesigner based
on each job role.
VISIT
www.sybase.com/pdvideos
TODAY!
6