The Unwired Enterprise is an information management strategy. In this session, we’ll be discussing this (POINT OUT YOUR PRODUCT OR SOLUTION AREA) section of Sybase’s Unwired Enterprise solution.
Sybase® Workspace framework and tools. To build an Unwired Enterprise, you need to do three things: End-to-end development Leverage and work with other open source components in Eclipse Integrate with full PowerDesigner release in Eclipse (Enterprise Modeling piece) Here is where we should talk about the overall architecture, how Workspace ties all of this functionality together into a single unified environment. Also, using Eclipse allows us to leverage open source components as well, for lower total cost of ownership.
To best understand what PowerDesigner offers, we use an analogy to Architecture. The question we ask is “Would you build a house withut a blueprint?” – the answer is obviously no. Looking at the pictures below, we also recognize that the design of an office space, a house, an addition to a home, whatever we are building, has multiple views. This example shows office space in both a “Business”-centric 3-Dimensional representation that everyone can understand, and the more technical definition that the contractors, plumbers, electricians, and so forth can understand. What gets interesting is – what if the contractor notices that by narrowing a 13-foot span to a 12-foot span, we can use a standard length beam in the project, and save $12,000 on the total cost of construction. What is the right BUSINESS decision to make here? Maybe I need the extra space and the smaller room will not fit my equipment properly – but on the other hand, if we can spare the space, the cost savings is significant. To make the correct business decision, I need to re-create the 3-Dimensional image so that we can validate the change is still consistent with our overall goals, and then make the decision – invest $12,000 because we need the space, or save $12,000 – the space is not critical and savings are more important.
To illustrate the effects of Iterative Analysis, Design and Development, we have built this chart that compares the typical cost of making a change throughout the development lifecycle with the cost associated with a highly iterative analysis and design cycle. If we follow the top line, representing the Traditional methods, we see that a change introduced at the Analysis level is relatively inexpensive to make, but as we move along through Design, Development, Testing and finally Deployment, we see the costs starting to exponentially rise. The lower line represents PowerDesigner’s ability to easily communicate changes made in any mode as change requests to any other model from any other user. With this, we can streamline the impact of change in such a way that changes discovered throughout the design, development and testing phases are relatively equal in cost, and much lower than traditional methods. Having a highly iterative cycle incorporating multiple small changes keeps projects relevant to a constantly changing set of user requirements.
So, nowadays, we see three different segments in the modeling (or design) market space: Data Modeling : this is where it all started, with modeling techniques like Entity/Relationship (this explains E/R) created by James Martin, famous for a methodology called James Martin Information Engineering UML modeling : James Martin Information Engineering was and still is very effective for database modeling, but was weak for application logic modeling. UML – Unified Modeling Language – although a generic notation, has proven its capabilities in recent years especially in the area of application/business logic modeling, especially because, if properly implemented, it allows automatic code skeleton generation and roundtrip engineering Business Process Modeling : BP Mo d eling has been around for a while, especially within Business Process Re-engineering companies. We have seen growing interest in BP modeling during recent years, mostly because of the new opportunities that the Internet brings to businesses. The Internet basically empowers enterprise to integrate – at information system level – with their customers and partners. In order to leverage these new opportunities, you do need 1) to understand your business process, 2) understand your customers / partners business processes and 3) design the interaction. BP modeling is a great tool for this.
Now, let’s look into what PowerDesigner offers. First, this is the history of PowerDesigner. We started in 1989, so we have been in the design tools business for a number of year, and we do believe we have accumulated a lot of knowledge in order to be capable of delivering the best solutions. The second interesting point in this slide is that we have been following standards adoption, E/R, UML, datawarehouse, and recently new emerging technologies for BP modeling. Lastly, please note that in 1996, we realized we had a 9 years old product. At the same time, new modeling techniques like UML where emerging and the need for enterprise repository was becoming more clear. We decided to re-architecture the product and came out in 1999 with version 7.0, a complete new rewrite of the code. We have added more and more features since, but, although we are at version 9.5, we still have a pretty young code line.
PDR608: Best Practices for Integrated Modeling with PowerDesigne r Xiao-Yun WANG PowerDesigner Chief Architect [email_address] August 15-19, 2004
The Enterprise. Unwired. Unwire People Unwire Information Manage Information Sybase Workspace Industry and Cross Platform Solutions
Adaptive Server Enterprise*
Adaptive Server Anywhere
Industry Warehouse Studio
Real Time Data Services*
SQL Anywhere Studio*
Pylon Family (Mobile Email)
XcelleNet Frontline Solutions
* = Products supported by PowerDesigner
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
Modeling in Application Development Lifecycle Modeling Tool Can Help in Each Phase Business Requirements Analysis Design Develop- ment Test Deployment Maintenance Business users IT users, analysts, designers Developers, DBAs, Administrators, etc Team work, Change management, Methodology, Documentation, Reuse Roles Control points
Use models to understand how the application was designed and developed
Repository; version control
Major Modeling 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
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 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. … »
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 Powersoft Sybase 2004 v11.0 Requirements Impact analysis Liquidity
PowerDesigner is the No. 1 Data Modeling Tool Data Modeling Magic Quadrant PowerDesigner Market share in 2002 was 39% (Document Gartner August 2003) Note : Quest Software resells an OEM version of PowerDesigner under the name ‘QDesigner’.
OOAD & BPA Market Overview Business Process Analysis MQ at version 9.5 Object Modeling MQ at version 9.5 Challenger Visionary
PowerDesigner V11 Structure O/R Mapping Data Model (E/R) Object Model (UML) Business Process (Targets: ebXML, BPEL4WS, Sybase U O) Business Process Model Repository Databases Persistence Management Application Servers Integration Servers - Metadata - Profiles - Model-to-Model Generation - MDA - Report - XMI …
Free Model - XML Model
Information Liquidity Model
Code Generation IDE
PowerDesigner V11 Modules 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 Database SQL Script (DDL) O/R Mapping Conceptual Data Model Physical Data Model Object Model (UML) XML Model Requirements Model Information Liquidity Model
PowerDesigner for Integrated 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
Best Practices of Integrated Modeling with PowerDesigner