- 1. PDR608:Best Practices for Integrated Modeling with
PowerDesigne r Xiao-Yun WANG PowerDesigner Chief Architect
[email_address] August 15-19, 2004
2. The Enterprise. Unwired. 3. The Enterprise. Unwired. Unwire
People Unwire Information Manage Information Sybase Workspace
Industry and Cross Platform Solutions
- Adaptive Server Enterprise*
- Industry Warehouse Studio
- Pylon Family (Mobile Email)
- XcelleNet Frontline Solutions
* = Products supported by PowerDesigner 4. Sybase Workspace
Integrated Development to build the Unwired Enterprise Web App,
Mobile, Portal, Data Management,Integration/Web Services,
Enterprise Modeling Sybase Infrastructure Products Common
Frameworks Eclipse 5. Summary
- Integrated Modeling Overview
- Best Practices ofIntegrated Modeling with PowerDesigner
6. Integrated Modeling Overview
- Modeling in Application Development Lifecycle
7. Why Modeling - Would You Build a House Without a
Blueprint?
- 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
8. Problem Statements
- How to improve application quality, reduce development time and
ease maintenance?
- How to design applications in such way that they are easy to
adapt for business requirements changes?
- 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
9. Modeling Toolforthe Rescue
- To improve application quality, reduce development time and
ease maintenance
-
- Use Modeling tool to analyze and design the applications
-
- Use code generators to generate the database, the application
code (MDA)
- To design applications in such way that they are easy to adapt
for business requirements changes
-
- Adopt Service-Oriented Architecture (SOA)
-
- Use Business Process Modeling, UML Modeling and Data Modeling
together
- To improve collaboration and team work
-
- Use an Integrated Modeling tool that supports requirements
management, impact analysis, change management
-
- Use a repository to store models and manage versions
10. Typical Application Development Cycle
Business Requirements Analysis Design Develop- ment Testing
Deployment Maintenance 11. Sybase PowerDesignerOur Vision 12.
Modeling inApplicationDevelopment Lifecycle Modeling Tool Can Help
in Each Phase Business Requirements Analysis Design Develop- ment
Test Deployment Maintenance Businessusers IT users,analysts,
designers Developers,DBAs, Administrators, etc Team work, Change
management, Methodology, Documentation, Reuse Roles Control points
13. Modeling in Application Development Lifecycle
-
- Requirements management; change management; traceability
-
- Define high-level abstraction models
-
- Synchronize code with models
-
- Generate test design documents and test cases
-
- Specify deploy topology and contents
-
- Use models to understand how the application was designed and
developed
-
- Repository; version control
14. MajorModeling Techniques Data Modeling ( E/R ) Object
Modeling (UML) Business Process Modeling (emerging standards) IT
users Analysts, Designers DBAs IT users Analysts, Designers
Developers Business users CIOs Integrated Modeling = PowerDesigner
Three modeling markets converging 15. Methodological Approaches
Source: Gartner
- Business Process Oriented (BPA)
16. Gartner says: The Modeling Techniques are Converging
- Gartner research note December 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 asSybase (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 17. Integrated Modeling Techniques(1/2)
- Business Process Modeling
-
- Allow business users to describe the business requirements
-
- Business process simulation and optimization
-
- Allow IT users, analysts, designers and developers to analyze
and design applications
-
- Define user interface, business logic, persistence and O/R
mapping
-
- Generate database structure and application code
-
- Conceptual, logical and physical data models
-
- Optimize database structure
-
- Create and reverse engineer the database
- Information Liquidity Modeling
-
- Support replication (Replication Server, ), synchronization
(MobiLink, ), data movement, ETL, XML/Relational mapping, virtual
data source,
-
- Design XML Schema, DTD, XDR, used for Web Services, databases,
Java, .NET
18. Integrated Modeling Techniques(2/2)
-
- Methodological approach for analysis, design and
development
- Model-Driven Architecture (MDA)
-
- Separate Platform Independent Models (PIM) with Platform
Specific Models (PSM)
-
- Model transformation, template or Design Pattern based code
generation
-
- Apply a generic solution for similar problems
-
- Model transformation or code generation
- Service-Oriented Architecture (SOA)
-
- Create or expose reusable services as Web Services
-
- Assemble Web Services using Business Process
- Collaboration and Team Work
-
- Central repository for storing models and specifications
-
- Manage model versions and security
-
- Impact analysis, change management
19. PowerDesigner Overview
20. PowerDesigner History 1989 (v1) 1990 French,CDM only 1991 V3
English CDM & PDM 1992 v4 Enterprise edition 1994 v5 Modules
ProcessAnalyst 1996 v6 Maturity release DataWarehouse Old Releases,
focus on E/R modeling and extensions New generation, UML and new
techniques 1999 v7 first UML diagram (Class) 2000 v7.5 added new
repository 2001 v8.0 More UML (Use Case, Sequence) v9.0 More UML
(Activity, Component) Data Warehouse EJB Business Process modeling
2002 v9.5 All UML diagrams UML profiles BP Modeling extensions 2003
v10.0 SOA .NET MDA PowersoftSybase2004 v11.0 Requirements Impact
analysis Liquidity 21. PowerDesigner is the No. 1 Data Modeling
Tool Data Modeling Magic Quadrant PowerDesigner Market share in
2002was39% (Document Gartner August 2003) Note : Quest Software
resells an OEM version of PowerDesigner under the name QDesigner.
22. OOAD & BPA Market Overview Business Process Analysis MQ at
version 9.5 Object Modeling MQ at version 9.5 Challenger Visionary
23. PowerDesignerV11 Structure O/R Mapping Data Model (E/R) Object
Model (UML) Business Process (Targets: ebXML, BPEL4WS,SybaseU O)
Business Process Model Repository Databases Persistence Management
Application Servers Integration Servers - Metadata - Profiles -
Model-to-Model Generation - MDA - Report - XMI
- Information Liquidity Model
Code Generation IDE 24. PowerDesignerV11Modules Java, J2EE,C#,
VB.Net, Web Services,PowerBuilder, XML, WSDL Forward Engineering
Reverse Engineering R ound-trip Engineering Import/Export ODBC
Corba, C++, etc... Business Process Model BPEL4WS IO, ebXML
DatabaseSQL Script (DDL) O/R Mapping Conceptual Data Model Physical
Data Model Object Model (UML) XML Model Requirements Model
Information Liquidity Model 25. PowerDesignerforIntegrated Modeling
Very Good Collaboration and Team Work Very Good Service-Oriented
Architecture (SOA) Some Design Patterns Very Good Model-Driven
Architecture (MDA) No Methodology Very Good XML Modeling Good
Information Liquidity Modeling Very Good Data Modeling Very Good
Object Modeling (UML) Good Business Process Modeling 26. Best
Practices ofIntegrated Modeling with PowerDesigner
- Types of application development
- Software engineering process
- Application development phases
- Best practices with PowerDesigner
27. Types of Application Development
- There are many types of application development
-
- Create a new web application
-
- Create a newclient/ server application
-
- Improve an existing application to fit business
requirements
-
- Modify existing application and create new application to
support SOA
- Each type of application development may use different
development process
28. Software Engineering Processes
- A software engineering process defines:
-
- The software development workflow
-
- The models and documents to produce in each step
-
- Models and documents templates and how to define the models and
documents
- PowerDesigner does not provide a process like Rational Unified
Process (RUP)
- Each customer could adopt a particular process or best practice
for his own needs
29. Typical Application Development Phases
- Requirements: Requirement Model
- Architecture: Business Process Model or Free Model
- High-level Business Process Model and UML Model
- Simulation:Business Process Model
- Business logic: detailed BPM and OOM
- Persistence: Data Model, O/R mapping
- Code generation: OOM, BPM
- Integration with IDE: Eclipse or PowerBuilder plugin
- Generate test plan and test design document from Requirement
Model
- Analysis and design models
30. High-LevelDesignand DevelopmentBest Practices
- Define user and software requirements
- Use high-level Business Process Model to define business
requirements
- Use UML to analyze and design the application
- Generate Data Model from UML Model
- Use Data Model to design and optimize the database
- Use Object/Relational mapping to generate persistence
management code
- Develop components, services and user-interfaces
31. Object-OrientedDesignand Development Best Practices
- Identify classes and operations
- Create detailed Class Diagram (business logic and
persistence)
- Generate PDM to optimize and create database and define O/R
mapping
- Use an IDE to develop the business logic
- Reverse engineer the code to update the models
32. Service-Oriented Architecture (SOA) 33. Service-Oriented
Development Best Practices
- Define requirements using Requirement Model
- Use BPM to simulate and optimize new or existing
operations
- Analyze and design new systems using UML
- Expose existing systems as Web Services
- Create databases using PDM
- Define replication and synchronization using Information
Liquidity Model
- Define XML Schemas using XML Model
- Define Web Services using UML Model
- Generate the code from models
- Assemble Web Services using Business Process Model
- Generate Web Services assembling languages (BPEL4WS, Sybase
Integration Orchestrator, )
34. RequirementsManagement
- Define business and user requirements
- Define software requirements
- Link software requirements to business and user
requirements
- Link use cases to software requirements
- Generate documents from requirements
35. RequirementsManagement in PowerDesigner (new) 36.
Requirements Traceability Matrix View 37. Editing Requirements in
WORD 38. Impact Analysis
- Deleting Customer class impact:
39. Business Process Modeling
- Define high-level Business Process Model to capture business
requirements
- Define detailed Business Process Model
- Simulate Business Process Model to optimize cost and delay
- Implement application artifacts (components,Web Services)
- Assemble Web Services using Business Process Model (BPEL4WS,
Sybase Unwired Orchestrator, )
- Use Business Process Model to generate other languages (ebXML,
Workflow, )
40. Example of High-Level Business Process Model
- Business users explain how a new or existing Business Process
should work
41. Example of More Detailed Business Process Model
- Once the business requirements are well defined, analysts and
designers create details Business Process Model that fits the
business needs
42. Process Hierarchy Diagram (new)
- Special diagram that allows users to view, create and modify
processes hierarchy
43. Example of an Order Processing Business ProcessModel for
Simulation 44. Example of a Business Process Model Simulation 45.
Example of an Executable Business Process Modelfor
SybaseUnwiredOrchestrator 46. Object Modeling (UML)
- Round-trip engineering for Java, C#, VB .NET, PowerBuilder and
Web Services
- Generate and reverse engineer PDM
- O/R mapping for EJB & JDO
- Integration with PowerBuilder 10 and Eclipse IDEs
47. Integration with PowerBuilder 10 48. Integration with
Eclipse3.0 49. Data Modeling
- PowerDesigner has complete data modeling support
- Conceptual Data Model and Physical Data Model
- Support all major databases
-
- XML in database (SQLX queries, annotated schema, )
50. Information Liquidity Modeling
- Support replication (Sybase Replication Server 12.5 &
12.6)
- Support ASE real-time messaging (RepConnector)
- Support synchronization (iAnywhere MobiLink 9)
- Could support data movement, ETL, virtual data source, in the
future
51. XML Modeling
- Design, generate and reverse engineer XML Schema, DTD, XDR
- Validate XML document(new)
- Generate XML document template(new)
- Generate XML Model from PDM
- Generate SQLX queries(new)
52. ExampleofXML Model Diagram 53. Model-Driven
Architecture(MDA)
-
- Platform Independent Models (PIM) and Platform Specific Models
(PSM)
-
- Transform PIM to PIM or PSM
-
- Generate default application code
- PowerDesigner has complete MDA support
- User-defined transformation functions
- User-defined template based code generator
- Use UML profile to extend metamodel (stereotype, code template,
custom command, transformation, )
54. Design Patterns
-
- Generic solution for solving similar problems
- Design Patterns could be implemented in PowerDesigner today
using:
-
- Use custom command defined in a Profile (Extended Model
Definition)
-
- Use transformation defined in a Profile
- Better support will be offered in future release
55. Service-Oriented Architecture (SOA)
- PowerDesigner has complete support for SOA
- High-level Business Process Model for analysis and design
- Create implementation artifacts for Java, .NET or
PowerBuilder
- Create Web Services for Java, .NET and databases
- Assemble Web Services using Business Process Model for BPEL4WS
and Sybase Unwired Orchestrator
56. Collaboration and Team Work
- Design business and software requirements
- Link requirements to design objects (Use Cases, )
- Generate documents from requirements (specification document,
test design document, documentation plan, project file, )
- Enterprise repository for models sharing and versioning
57. PowerDesigner Roadmap
- PowerDesigner 11.0 (Minerva)
58. PowerDesigner 11.0 Key Features
- Process hierarchy diagram
- Information Liquidity Model (Replication Server, RepConnector,
MobiLink)
- Floating license management
59. Beyond Minerva
- Advanced team work capabilities
- Enhanced requirements management
- Support for methodology frameworks
- Improved mapping management (replication, DW, O/R, XML/R)
- Visual Studio .NET plugin
60. More Information
-
- http://www. sybase .com/ powerdesigner
-
- http:// powerdesigner . codexchange . sybase .com
-
-
news://forums.sybase.com/sybase.public.powerdesigner.general
- PowerDesigner Advanced Documentation
-
- Accessible from PowerDesigner help menu
- PowerDesigner VBScript online help
-
- Accessible from PowerDesigner help menu
- Microsoft Windows Script online help
-
- Can be downloaded fromhttp:// msdn . microsoft .com
61. PowerDesigner The Leader in Enterprise Modeling Xiao-Yun
WANG PowerDesigner Chief Architect [email_address] August 15-19,
2004