1 / 94

UML China 讲座 All-in-One Design Tool PowerDesigner10.0 与模型驱动开发

王晓昀 PowerDesigner 首席架构师 xwang@sybase.com 2004 年3月25日. UML China 讲座 All-in-One Design Tool PowerDesigner10.0 与模型驱动开发. 议程. 我的简介 为什么要使用模型 驱动开发 工具 PowerDesigner 简介 PowerDesigner 与业务流程建模 PowerDesigner 与对象建模 PowerDesigner 与数据建模 PowerDesigner 与 XML 建模 PowerDesigner 的 共同 功能

derora
Télécharger la présentation

UML China 讲座 All-in-One Design Tool PowerDesigner10.0 与模型驱动开发

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 王晓昀PowerDesigner 首席架构师 xwang@sybase.com 2004年3月25日 UML China 讲座All-in-One Design ToolPowerDesigner10.0与模型驱动开发

  2. 议程 • 我的简介 • 为什么要使用模型驱动开发工具 • PowerDesigner简介 • PowerDesigner与业务流程建模 • PowerDesigner与对象建模 • PowerDesigner与数据建模 • PowerDesigner与XML建模 • PowerDesigner的共同功能 • PowerDesigner 10.0 的新功能介紹 • PowerDesigner与模型驱动开发 • PowerDesigner 的路线图

  3. 我的简介 • 我的名字是王晓昀 (WANG Xiao Yun) • 我于1978年上北京大学.只上了三个月. • 我于1979年去法国上学 • 1986年大学毕业后在巴黎的SDP软件公司工作 • 1988年开始开发PowerDesigner • 1989年开发在法国出卖AMC*Designor • 1991年开始在美国出卖S-Designor • 1995年Powersoft买下了我们的SDP公司 • 1995年Sybase又买下了Powersoft • S-Designor和AMC*Designor的名字改为PowerDesigner和PowerAMC • 从1995年到现在我一直负责PowerDesigner的设计和开发 • 我在法国生活了25年.我现在还是中国人

  4. 为什么要使用模型驱动开发工具

  5. 为什么要使用模型驱动开发工具? Would You Build a House Without aBlueprint? • The Architect will do the first high level drawings to validate the concept with its client He will then make a detailed plan for the Builders • The Builders will take this blueprint and optimize it based on technical constraints

  6. 开发软件的问题 • How to improve application quality, reduce development time and ease maintenance? • How to model business-driven application? • How to design applications in such way that they are easy to change? • Different techniques (E/R, UML, BP Modeling) have forced corporations to buy different tools, raising communication and co-ordination issues • Lack of central place to store and manage models

  7. 模型驱动开发工具 • To improve application quality, reduce development time and ease maintenance • Use Modeling tool to analyze and design the applications • Use Modeling tool to generate the specification • Use code generators to generate the database, the application code • Use repository to store models and manage versions • To model business-driven application and allow applications to be easilly changed • Use Business Process Model, UML and Data Model together

  8. PowerDesigner 简介

  9. PowerDesigner的历史 Old Releases, focus on E/R modeling and extensions Powersoft Sybase 1996 1989 1990 1991 1992 1994 v5ModulesProcessAnalyst v4Enterpriseedition v6Maturity releaseDataWarehouse (v1) French, CDM only V3 EnglishCDM & PDM New generation, UML and new techniques 2003 1999 2000 2001 2002 v7first UMLdiagram (Class) v7.5added newrepository v8.0More UML(Use Case, Sequence) v9.0More UML(Activity,Component) Datawarehouse EJB Business Process modeling v9.5All UML diagramsUML profilesBP Modelingextensions… v10.0 SOA .NET MDA

  10. Gartner说 PowerDesigner在数据建模上占世界第一位 PowerDesignerMarket share in 2002 was39%(Document Gartner August 2003)

  11. Gartner说PowerDesigner在数据建模上占世界第一位 PowerDesignerMarket share in 2002 was 39%(Document Gartner August 2003) Data Modeling ‘Magic Quadrant’ 2004 Note: Quest Software resell an OEM version of PowerDesigner under the name ‘QDesigner’.

  12. OOAD & BPA Market OverviewGartner modeling quadrants BP Modelingat version 10 2004 quadrant Object Modelingat version 9.5.22003 quadrant Visionnary Challenger

  13. 不同的建模技术 • 数据建模(E/R, DFD) • 面向对象建模(UML) • 商业流程建模(BPA) Source: Gartner

  14. Gartner说三个建模技术要连结在一起 • Gartner research note decembre 2003 • Strategic Planning, SPA-21-5951 - M. Blechar • Predicts 2004: BPA, UML and Data Modeling Converge« Techniques such as business process analysis are converging to provide technical architects, business modelers, developers and database designers consistency, productivity and quality via reuse and code automation. » • « …Vendors such as Sybase (PowerDesigner) and … offer single products that span all three markets. Most UML modeling tool vendors already have some BPA and database design support in their tools, and vice versa. … » Source: Gartner

  15. PowerDesigner Key Features • Good Business Process Modeling support • Full UML Modeling support • Complet Data Modeling support • XML Modeling • Integrated BP, UML & Data Modeling • O/R Mapping • Repository • Report generator • Customizable code generator (Java, EJB, Web Service, C#, VB .NET, PowerBuilder, XML, BPEL4WS, …) • VBScript and OLE automation support

  16. 最好的建模技术是整合式建模 三个建模技术要连结在一起 商业流程建模 (emerging standards) 商业用户CIOs 数据建模(E/R) 面向对象建模 (UML) IT用户 分析员设计师DBAs IT用户 分析员设计师 开发人员 整合式建模 = PowerDesigner

  17. PowerDesigner的体系结构Maximum coverage 资料库(optionnel) 商业流程模型 - Free Model- XML Model 商业流程模型(Targets: ebXML, BPEL4WS, Sybase IO) - Metadata - Profiles- Model-to-Model Generation - MDA - Report - XMI … 数据模型 (E/R) 面向对象模型(UML) O/R Mapping 编码生成 IDE Persistence Management Application Servers Integration Servers 数据库

  18. O/R Mapping Generation Reverseengineering Import/Export Synchronization PowerDesigner的模型 Java, C#, VB.Net, PowerBuilder, WSDL, … 商业流程模型 面向对象模型 ebXML BPEL4WS IO XML DTD XML Schema 概念性数据模型 XML模型 物理数据模型 Script DDL SQL 数据库 ODBC

  19. Modeling in Development Cycle Business Requirements 分析 设计 测试 Deployment Maintenance 开发 Roles IT用户 分析员设计师 开发人员, DBAs, Administrators, etc 商业用户 Team work, Change management, Methodology,Documentation, Reuse PowerDesigner coverage 明天 PowerDesigner coverage 今天 Control points

  20. Exemple of PowerDesigner Object-Oriented Model (UML)

  21. Industry Endorsement – Customer Adoption • PowerDesigner is already used by many public and private organizations worldwide • Total today over 50,000 users at 30,000 sites worldwide – we are doing something right! • Examples of strengths in specific areas: • Financial Community embraces PowerDesigner • France • Germany • UK • USA • French market – 80% market share – and they know about design!

  22. Hurwitz on PowerDesigner 9.0 Benchmark Rating – Overall Rating 8.0 • Comprehensiveness: ‘… a rich all in one modeling environment…’ • Deployment flexibility: variety of languages and target platforms • Developer resources: Sybase Developer Network • Life-cycle management: integration with IDE • Developer productivity: ‘… a solid set of wizards and tools to speed development tasks such as EJB creation, object/relational mapping (O/R map), report generation, and a customizable user interface’ Ease-of-use Comprehensiveness Deployment Flexibility Developer Resources Life-Cycle Management Developer Productivity Aids/Wizards Adherence to Standards 0 2 4 6 8 10

  23. – – – UML only, IT style Sterling, BPwinproducts No No Erwinis a decliningleader E/R Studio technical limitations – – + limited &complex + limited Leaderfor developers two overlappingproducts(Platinum/Sterling) Describe limited awareness UMLvisionary - – + + integration issue due to multiple products integration issue due to multiple products – – – usabilityissues – limited Competitive Differentiation – PowerDesigner 10.0 IBM RationalRose • Competitive DifferentiationPowerDesigner 9.5 ComputerAssociates Borland Together Embarcadero Business Process Modeling Data Modeling Object Modeling Repository

  24. Competitive Differentiation – PowerDesigner 10.0 • Competitive DifferentiationPowerDesigner 9.5 Sybase PowerDesigner Challenger with specific offering Business Process Modeling Leader mature technology proven over years of success Data Modeling Complete offering with version 10.0 showing growth in market and technology Object Modeling Most complete and integrated design-time enterprise repository in the industry Repository

  25. Competitive Differentiation – PowerDesigner 10.0 • Best integrated BP, UML, Data modeling tool • No.1 Data Modeling tool, better than ERwin • Very good UML modeling, better than Rose • Best O/R mapping support • Best Repository • Very good report generator • Extensible (code generator, profile, VBScript, …) Repository

  26. PowerDesigner 与业务流程建模

  27. Why Using Business Process Modeling? • It is not technical; it is easy to use. • Business users can use it to: • Describe the current business processes • Define the future business processes • Optimize business processes • Improve ROI • BPM can be used to design and generate BPM and workflow standards (ebXML, BPML, XPDL, …) • BPM can be used to design and generate Web Services orchestration standards (BPEL4WS, …)

  28. Why We Use BPM instead of UML? • BPM tool is essentially for business users. It should be very easy to use. • UML is more technical and more complex. It is good for designing applications but not for describing business processes. • We offer well adapted tools for different usages instead of forcing all users to use UML.

  29. Business Process Model Concepts • Predefined Symbols • Start • End • Process • Flow • Decision • Synchronization • Organization Unit • Resource • Service provider, interface, operation • Data

  30. Example of a High-Level BPM • Describe system architecture

  31. Example of a Detailed BPM Swimlane

  32. PowerDesigner 10.0 BPM Features • Simple user-interface • Custom symbols, predefined symbols tool palette • Support Simulation (use Simul8) • Support Service-Oriented Architecture (SOA) • Generate/reverse engineer BPEL4WS • Generate Sybase Integration Orchestrator model • Generate/reverse engineer ebXML • Import/export data from/to OOM and CDM • Export UML Activity diagram using VBScript • Swimlane • CRUD matrix (Create, Read, Update, Delete)

  33. Support Simuation (new in V10) • Use simulation to optimize business processes (costs, delay, resources) • Define Simul8 specific properties • Generate Simul8 models • Reverse engineer Simul8 properties

  34. Support Service-Oriented Architecture (SOA) • Support Service provider, Service interface and operation • Import WSDL, UDDI browser • Assign service operation to process • Web Services assembling • Design, generate, reverse engineer BPEL4WS

  35. Generate Sybase Integration Orchestrator Model • Define IO specific Business Process Model in PowerDesigner • Generate IO model • Refine IO model

  36. Support ebXML BPSS • Design, generate and reverse engineer ebXML Business Process Specification Schema (BPSS) • Generate Private Process Options for Process Server • Process Server can import the generated ebXML BPSS.

  37. PowerDesigner 与对象建模

  38. Why UsingUML? • Visually define and communicate the structure and behavior of an application • Represent systems using Object-Oriented concepts • Link OO concepts to executable code

  39. Brief Overview of UML • UML is defined by OMG. • UML consists of 9 diagrams: • Static • Class diagram • Object diagram • Dynamic • Use Case diagram • Sequence diagram • Statechart diagram • Collaboration diagram • Activity diagram • Implementation • Component diagram • Deployment diagram

  40. UML Support in PowerDesigner • PowerDesigner supports all nine UML diagrams • PowerDesigner supports UML 1.4 • Future version of PowerDesigner will support UML 2.0

  41. Use Case Diagram • A Use Case Diagram describes the Actors, the Use Cases and the interaction between the Actors and the Use Cases.

  42. Collaboration Diagram • A Collaboration Diagram describes the interaction between objects (instance of classes) by exchanging messages. • Collaboration Diagram can be used to identify classes and operations

  43. Sequence Diagram • A Sequence Diagram describes the interaction between objects and how the messages are exchanged over time. • Sequence Diagram is used to identify classes and operations

  44. Activity Diagram • An Activity Diagram describes the logic and the control flow of a Use Case, an Operation or another Activity.

  45. Statechart Diagram • A Statechart Diagram is used to model the States and Transitions of a Class

  46. Object Diagram • An Object Diagram shows the relationships between Object Instances

  47. Class Diagram • A Class Diagram defines the Classes, Interfaces, Attributes, Operations, Relationships, Inheritances, … • A Class Diagram can be used to define persistent objects, control objects and user-interface objects. • A Class Diagram can be used to generate the Physical Data Model and the application implementation code.

  48. Component Diagram • A Component Diagram can be used to define the components you need to create for an application • A Component can use Classes, Interfaces • PowerDesigner uses Components to representEJBs, Servlets, JSPs, ASPs and Web Services

  49. Deployment Diagram • A Deployment Diagram is used to define the deployment architecture • Deployment Diagram shows the Nodes (machines, servers), the Component Instances deployed in a Node and the Links between Nodes

  50. Object/Relational (O/R) Mapping • Generate a Class Diagram from a Physical Data Model with O/R mapping • Generate a Physical Data Model from a Class Diagram with O/R mapping • Manually define complex O/R mapping • Generate select, insert, update, delete SQL statements • Use O/R mapping to generate EJB CMP (WebLogic, WebSphere, EAServer), JDO, Cocobase, .NET (future)

More Related