190 likes | 379 Views
PowerDesigner 与对象建模. Why Using UML?. Visually define and communicate the structure and behavior of an application Represent systems using Object-Oriented concepts Link OO concepts to executable code. Brief Overview of UML. UML is defined by OMG. UML consists of 9 diagrams : Static
E N D
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
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
UML Support in PowerDesigner • PowerDesigner supports all nine UML diagrams • PowerDesigner supports UML 1.4 • Future version of PowerDesigner will support UML 2.0
Use Case Diagram • A Use Case Diagram describes the Actors, the Use Cases and the interaction between the Actors and the Use Cases.
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
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
Activity Diagram • An Activity Diagram describes the logic and the control flow of a Use Case, an Operation or another Activity.
Statechart Diagram • A Statechart Diagram is used to model the States and Transitions of a Class
Object Diagram • An Object Diagram shows the relationships between Object Instances
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.
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
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
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)
O/R Mapping Example Use O/R mapping to generate SQL Generate O/R mapping when generating a PDM from an OOM
Java Support • Provide wizards to automatically create EJBs, Servlets, JSPs, Web Services • Generate and reverse engineer Java code • Generate collection management accessor functions • Generate deployment descriptors • Generate O/R mapping descriptor for WebLogic, WebSphere, EAServer, JDO, JBoss (future) • Generate project files for JBuilder and Eclipse • Generate Ant script to compile, package and deploy J2EE application
Example of EJB EJB wizard EJB Classes and Interfaces EJB Component
.NET Support • Reverse engineer C# and Visual Basic .NET code • Reverse engineer .NET binary code in C# or VB .NET • Generate C# and VB .NET code • Generate collection management accessor functions • Generate Visual Studio .NET project files • Create Web Services for C# or VB .NET (.asmx files)
Code Generation • Templates and macros based code generator • Generate Java, C#, VB .NET, VB, C++, PowerBuilder, … • User could add their own code generation templates C# code preview