1. The Power of PowerDesigner Frank Irnich Sybase GmbH Frank.Irnich@sybase.com

2. Agenda  PowerDesigner Overview  PowerDesigner for PowerBuilder Features Summary  Applying PowerDesigner extensibility features to extend its traditional usage  Version 10: PowerDesigner and PowerBuilder together  PowerDesigner 10

3. PowerDesigner Overview  Why Modeling?  PowerDesigner History  PowerDesigner Features Summary

4. Why Modeling? – An analogy The Architect validates the concept with the client From these drawings, a technical diagram will be derived The Contractors will take this blueprint and optimise it based on technical considerations – linked to the Architectural View Would you build a house without a blueprint ?

5. The Application Development Process  Starts with Understanding Business Needs  IT Manager then:  Matches business needs with Technological Requirements  Manages the IT development team – a multi-discipline team  Most IT shops separate DB development from Application development  Specific tools needed for each population/role A Business Process Model describing the Software Development Lifecycle

6. Traditional E/R Data Modeling (James Martin) Object-oriented Modeling (UML techniques) Business Process Modeling (emerging standards) Designers/Analysts, DBAs, Database Developers Design Tools Market Landscape Designers/Analysts, Developers, Programmers Business Analysts LOBs CIOs Three markets converging

7. Target Audience Business-centricIT-centric RDBMS - Designers - Developers -… CxOs LOBs Business Analysts Application - Designers - Developers -… IT Directors and Managers Senior Analysts & Designers

8. PowerDesigner’s Rich History 1989 v1 1990 v2 French Only 1991 v3 Multiple Models 1992 v4 Enterprise Edition 1994 v5 DFD Process Modeling 1996 v6 Warehouse Modeling Old Generation – Completed commitment to Traditional E/R New generation - Reinvented and Refined - UML, Business Modeling 1999 v7 First UML 2000 v7.5 Enterprise Repository 2001 v8.0 Enhanced UML v9.0 J2EE in UML New Warehouse & Business Process Modeling Q4/2002 v9.5 All UML diagrams.NET in UML Integration Q1/2002

9. Source Sybase Repository Business centric IT centric PowerDesigner 9.5 Development Analysis & Design Business Analysis Business-centric Control Flow diagram Entity/ Relationship modeling (and DW extensions) UML modeling (all diagrams) RDBMS structures Object Relational mapping Java,.Net, XML, PB... support IDEs & App Server support Templates, Generic Generators, UML profiles, model-to-model generation… Integrated Enterprise Modeling Tool

10. Link and Synchronize All Models PowerBuilder, Java, J2EE XML, WSDL Forward Engineering Reverse Engineering Round-trip Engineering Import/Export ODBC C++, C#, VB.Net, Web Services, etc... Business Process Model (BPM) ebXML, Message Broker, Ohio Database SQL Script (DDL) O/R Mapping Conceptual Data Model (CDM) Physical Data Model (PDM) Object-Oriented Model (OOM) Free Model (FEM)

11. PowerDesigner 9.5.2 Features Summary  PowerDesigner is a good enterprise modeling tool  Leading Data Modeling tool  Complete UML support (9 UML diagrams)  Business Process Modeling features  Good Repository  Integration with Integration Orchestrator, Message Broker, ebXML  Design and generate code for PowerBuilder, Web Services, J2EE (EJB, O/R mapping),.NET, etc.  Support all major databases (more than 30)  Support major application servers (EAServer, WebLogic, WebSphere)  Integration with IDEs (Eclipse, JBuilder 8, Ant)  Supports Model Driven Architecture (MDA)  Extensibility (Profile, Code generator, VBScript, OLE automation)

12. PowerDesigner 9.5.2 for PowerBuilder  PowerDesigner for PowerBuilder Features Summary  PowerBuilder Applications Design and Development  Reverse Engineering PowerBuilder Applications  Designing PowerBuilder Applications  Generating PowerBuilder Applications  Extending PowerDesigner Features  Future Direction

13. PowerDesigner for PowerBuilder Features Summary  PowerDesigner 9.5.2 introduces complete support for all PowerBuilder objects reverse engineering and generation  Support libraries (.pbl) and source files (.sr*)  Support PowerBuilder 6, 7, 8 and 9  PowerBuilder tool palette for creating new objects  Model verification  Generate & reverse PowerBuilder extended attributes in PDM

14. Problem Statement  Most of PowerBuilder developers don’t do design.  Many PowerBuilder applications don’t have a good architecture and there is no documentation.  It is difficult to maintain and evolve when the developers are gone.

15. PowerDesigner Value Proposition  Help users to understand how the application was developed.  Help users to visually see the relationship between objects.  Help users to improve existing code, refactor the code.  Regenerate PowerBuilder application.  Generate documentation (report) in HTML and RTF format.

16. Reverse Engineering PowerBuilder Applications  Application, User Object, Structure, Function, Window, Proxy are represented by class structure  For the other objects (DataWindow, Query, Pipeline, …), the source code is preserved and can be regenerated  Both libraries (.pbl) and source files (.sr*) can be reverse engineered

17. Reverse Engineering PowerBuilder Applications  You could select reverse engineering options.  You could use PowerBuilder System Classes and PFC library models to represent parent classes that give you the complete definition of the System Classes.

18. Displaying PowerBuilder Objects in Class Diagram  A class diagram shows packages, inheritances, associations, dependencies, attributes, operations.  Each library is represented by a package.  A stereotype and a mini icon shows the type of object.  The dependencies show which menu or data window is used by which window.  Window, user object, application, structure, function and proxy are represented as classes and the code is regenerated from the class definition.  Other objects are represented as classes by the source code is kept and are not regenerated from the class definition.  Controls are represented by inner classes.

19. Example of a Class Diagram

20. Designing PowerBuilder Applications  You can create, modify or delete objects or links.  You can use the PowerBuilder tool palette to create objects.  You could define interfaces and implement interfaces but the interfaces will not be generated.  You can preview the PowerBuilder code.  You can modify the PowerBuilder code in the code preview window.  You can write specification in RTF format. You could use Word to edit the description or annotation.  You can generate reports in HTML or RTF formats for documentation.

21. Defining Inheritances  A parent class could be a shortcut representing a class defined in another model for example for system classes.

22. Defining Events  Events are represented as operations.  An Event could be an operation with the «event» stereotype, with a language event or with an extended attribute EventID (pbm_*).

23. Overriding Properties  In the Attributes tab of the class property sheet, the Inherited button allows you to select the properties to override.

24. Previewing PowerBuilder Code  Open the properties of an object. Select the Preview tab.  For Window, User Object, Application, Structure, Function and Proxy, the code is generated from the class definition. You could change the code in the Preview window (add attributes, modify operations, …), the model will be updated to reflect the changes.  For DataWindow, Menu, Query, …, you could change the code in the Script tab

25. Verifying the Model  You could use the Check Model function to verify if the model is well defined.  There are PowerBuilder specific checks.

26. Generating PowerBuilder Applications  You can generate PowerBuilder objects into libraries or source files.  You can select the objects you want to generate.

27. Extending PowerDesigner Features  You could use various extensibility features of PowerDesigner to extend PowerDesigner’s PowerBuilder generation and reverse engineering capabilities:  Profile  GTL (template based code generator)  VBScript, OLE automation (PowerBuilder,.NET, Java, C++, …)  Plugins

28. The profile concept  PowerDesigner uses the profile concept to extend/cutomize the definition of its metamodel  Profiles are used for  Creating categories of objects (stereotypes and criteria)  Customizing the graphics of objects  Adding additional metadata to objects (extended attributes)  Defining new or modified generation capabilities (templates)  Defining custom checks, menue-items, events, etc..  Profiles appear in all DBMS, object languages and extended model definitions

29. The profile concept  Profiles appear in all DBMS, object languages and extended model definitions PowerDesginer Public MetaModel Object Language / DBMS Extended Model Definition(s) Target Model (OOM, PDM, etc...) } Profile Concept BPM/FRM

30. GTL – Generation Template Language  Easy to use template language  Mixes generated text with object properties enclosed in % characters  Provides macros for  Specifying conditional logic  Iterating on object collections  Manipulating text  VB Scripts may be embedded in GTL templates for complex logic  Supports inheritance and polymorphism

31. GTL – Generation Template Language  Sample:  Class %code% { %attributes% } .foreach_item(Attributes).if (%visibility% == +) public %DataType% %Code%;.elseif (%visibility% == -).//....endif.next(\n) Macro Collection Variable

32. VBScript  Manipulate PowerDesigner objects in memory and perform any action on them  Browse object collections from the model down to any object using PowerDesigner`s metamodel  You can  Load and save models  Gain access to object definitions  Perform checks  Change object property values  Create or delete objects with the wanted characteristics

33. OLE automation  VBScript allows you to write a VBScript and execute it inside PowerDesigner to manipulate PowerDesigner objects  OLE automation allows you to write a program to manipulate PowerDesigner objects from outside  You can use any programming language that supports COM to access PowerDesigner objects, create user-interfaces, integrate PowerDesigner functions in your program, etc...

34. Future Direction  PowerDesigner 10.0 will support tight integration with PowerBuilder 10  PowerBuilder 10 will be able to embed PowerDesigner views inside PowerBuilder  PowerBuilder will be able to control PowerDesigner  PowerDesigner will generate complete PowerBuilder application code (post 10.0)

35. PowerDesigner Roadmap  PowerDesigner Athena (V10, December 2003)  Integration with PowerBuilder  Integration with Eclipse (Q1 2004)  Major BPM improvements  XML model  Fully support MDA  PowerDesigner Minerva (end of 2004)  Enterprise features (requirements, impact analysis, …)  XML and Web Services in database  UML 2.0  Design patterns

36. Business Process Modeling Improvements  Add targets (Analysis, BPEL4WS, ebXML, Integration Orchestrator, MessageBroker, …)  Support simulation (use Simul8 engine)  Support Service-Oriented modeling  Model, generate & reverse BPEL4WS  Better integration with Integration Orchestrator (round-trip)  Better support ebXML BPSS

37. XML Model  Design, reverse engineer and generate XML Schema and DTD  Define mapping between XML Schema and database schema  Define mapping between XML Schema and objects  Support databases XML features

38. Other Athena Features  Support C# and VB.NET reverse engineering  Improve Web Services support (support Apache Axis, …)

39. PowerDesigner and PowerBuilder Together  PowerDesigner: A Plugin Component in PowerBuilder 10  Reverse Engineer From PowerBuilder  Design and Generate PowerBuilder Code Using PowerDesigner  Navigation Between PowerDesigner and PowerBuilder Summary

40. PowerDesigner and PowerBuilder Together  PowerBuilder Plugin Manager Manages Plugin Components  A plugin component can enable or disable by Plugin Manager  PowerDesigner Feature Will Be Available Only When It Is Turned On PowerDesigner: A Plugin Component in PowerBuilder 10

41. PowerDesigner and PowerBuilder Together PowerDesigner: A Plugin Component in PowerBuilder 10

42. PowerDesigner and PowerBuilder Together  Select “Reverse Engineer” From PowerBuilder Target Context Menu  Select PBLs and Objects to Reverse Engineer Reverse Engineer From PowerBuilder

43. PowerDesigner and PowerBuilder Together  Create a New PowerBuilder OOM (Object Oriented Model)  OOM name maps to PowerBuilder target name  Package name maps to PowerBuilder pbl name Design and Generate PowerBuilder Code Using PowerDesigner

44. PowerDesigner and PowerBuilder Together  Add Classes and Do Design  Although PowerBuilder doesn’t support interface yet, user can define interface in PowerDesigner, then implement interface in a PowerBuilder user object. Design and Generate PowerBuilder Code Using PowerDesigner

45. PowerDesigner and PowerBuilder Together  Check Model  Check model is customized for PowerBuilder, for example, it will check whether a object name is valid PowerBuilder name, a pbl can only have one application object  Check model results are printed in output window Design and Generate PowerBuilder Code Using PowerDesigner

46. PowerDesigner and PowerBuilder Together  Generate PowerBuilder Code  Select packages and classes from OOM to generate PowerBuilder code  If it is the first time to generate PowerBuilder code, a new PowerBuilder target will be created Design and Generate PowerBuilder Code Using PowerDesigner

47. PowerDesigner and PowerBuilder Together  From PowerBuilder to PowerDesigner  Select “Open Class Diagram” from pbl context menu to open class diagram for this pbl  Select “Find in Class Diagram” from PB object context menu to find the corresponding class in class diagram  From PowerDesigner to PowerBuilder  Double click a class in class diagram to launch PowerBuilder painter to open corresponding PB object  Select “Find in PowerBuilder Workspace” from class context menu to find the corresponding PowerBuilder object in PowerBuilder workspace Navigation Between PowerDesigner and PowerBuilder

48. Question & Answer...

49. The Power of PowerDesigner Frank Irnich Sybase GmbH Frank.Irnich@sybase.com