Patterns: Model-Driven Development Using IBM Rational Software Architect

Transcription

1 Front cover Patterns: Model-Driven Development Using IBM Rational Software Architect Learn how to automate pattern-driven development Build a model-driven development framework Follow a service-oriented architecture case study Peter Swithinbank Mandy Chessell Tracy Gardner Catherine Griffin Jessica Man Helen Wylie Larry Yusuf ibm.com/redbooks

2

3 International Technical Support Organization Patterns: Model-Driven Development Using IBM Rational Software Architect December 2005 SG

4 Note: Before using this information and the product it supports, read the information in Notices on page ix. First Edition (December 2005) This edition applies to Version of Rational Software Architect (product number 5724-I70). Copyright International Business Machines Corporation All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Notices ix Trademarks x Preface xi For solution architects xi For project planners or project managers xii For those working on a project that uses model-driven development xii How this book is organized xiii The team that wrote this redbook xiv Become a published author xv Comments welcome xvi Part 1. Approach Chapter 1. Overview and concepts of model-driven development Current business environment and drivers A model-driven approach to software development Models as sketches and blueprints Precise models enable automation The role of patterns in model-driven development Not just code Benefits of model-driven development Model-driven development with IBM Rational Software Architect Unified Modeling Language 2.0 editor UML profile support RSA patterns RSA transformations Summary Chapter 2. Scenario overview Enterprise architecture Suitability for model-driven development Contra-indications for model-driven development Integration architecture ESB structure Pattern definition Interaction behavior patterns Individual service patterns Suitability for model-driven development Copyright IBM Corp All rights reserved. iii

6 2.3.4 Contra-indications for model-driven development Automation Technical Organizational Managerial Summary Chapter 3. Model-driven development approach Abstraction Precise modeling Automation Architectural style The role of UML Expertise capture Logical architecture expertise Technical architecture expertise Patterns Quality and consistency Integration Platform independence Layered modeling Modeling of non-functional characteristics Summary Chapter 4. Model-driven development project planning The value and cost of model-driven development Understanding the tasks for a model-driven development project Descriptions of tasks The model-driven development tool chain Planning a model-driven development project Using an iterative approach to model-driven development Developing model-driven development skills Thinking about reuse Quality control for model-driven development tooling Tracking a model-driven development project At the end of the project Summary Chapter 5. Model-driven development solution life cycle Introduction to the solution life cycle Model-driven development life cycle Create the framework to generate the solution services Generate, customize, and test the solution services Model-driven development and versioning iv Patterns: Model-Driven Development Using IBM Rational Software Architect

7 5.3.1 Versioning and replacement policies Model-driven development and artifact management Reuse model artifacts Integrity management services Deployment support Model-driven development and problem determination Tooling versus instrumentation Information mining Testing Modeling for testing Applying test patterns Modeling using the UML testing profile Summary Chapter 6. Model-driven development in context OMG and Model-Driven Architecture MDA models IBM and MDA Software Factories and domain-specific languages UML and DSLs Asset-based development Pattern-driven development and IBM Patterns for e-business IBM Patterns for e-business Business-driven development Model-driven development and On Demand Business Model-driven development and middleware Visualization Executable UML Summary Part 2. Implementation Chapter 7. Designing patterns for the scenario Relationship to the project plan Overview of pattern design Architecture patterns Contracts of behavior Contract of behavior for synchronous updates General requirements for synchronous update Integration patterns Applying a pattern to create a high-level model The pattern The model Detailing the initial model with service patterns Contents v

8 7.7.1 Service patterns: Activity diagrams Integration services RSA transformation Implementing the integration facade Implementing the integration service Implementing the provider facade Use of the framework Presentation of model information to users Service creation Summary Chapter 8. Applying model-driven development with Rational Software Architect An overview of the Model-driven development process in RSA Framework development Application development RSA model-driven development framework for SOI Application development Installing the framework Creating a model and apply the profiles Applying patterns Applying transformations Testing the generated code Application development summary Framework development Developing the architectural style Creating a UML profile Implementing sample components Developing patterns and transformations Summary Chapter 9. Extending Rational Software Architect Introduction to implementing patterns and transformations to RSA Setup: Enabling Eclipse Developer Deploying UML profiles Defining a path map Releasing the profile Adding the profile to a plug-in Deploying the plug-in Implementing patterns Getting started Defining a pattern Pattern implementation vi Patterns: Model-Driven Development Using IBM Rational Software Architect

9 9.4.4 Testing the pattern Publishing patterns Implementing a transformation Creating a new plug-in with a transformation Transformation API Implementing the root transformation Implementing the transformation rules Creating and modifying files in the RSA workspace Testing the transformation Launching a Run-time Workbench Deploying plug-ins Using a RAS repository Summary Chapter 10. Conclusion Appendix A. Additional material Locating the Web material Using the Web material System requirements for downloading the Web material How to use the Web material Abbreviations and acronyms Related publications IBM Redbooks Other publications Online resources How to get IBM Redbooks Help from IBM Index Contents vii

10 viii Patterns: Model-Driven Development Using IBM Rational Software Architect

11 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. Copyright IBM Corp All rights reserved. ix

12 Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: CICS developerworks Eserver Eserver IBM Rational Unified Process Rational Redbooks (logo) RUP SoDA WebSphere The following terms are trademarks of other companies: EJB, Java, Javadoc, JVM, J2EE, RSM, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. x Patterns: Model-Driven Development Using IBM Rational Software Architect

13 Preface The convergence of patterns, models and tooling sets the scene for major increases in application development productivity by Now is a good time to get on board. Jonathan Adams, Distinguished Engineer, IBM Academy of Technology You may read this IBM Redbook for a number of reasons. Perhaps you are already familiar with the ideas behind model-driven development (MDD), and you want to learn about how to put those ideas into practice and how to convince others in your organization to adopt the approach. Maybe you heard something about the benefits of MDD but want to learn more about it before you are convinced that it is suitable for your project. Or you recently joined an MDD project and need to understand what it is all about. This IBM Redbook is written for technical practitioners and project managers who want to learn more about MDD in practice. It will help you understand how to put the ideas of MDD into practice using Unified Modeling Language (UML). You will learn how to articulate the advantages of MDD to both project managers and technical colleagues. You will see how the MDD software life cycle differs from other approaches and how you can effectively plan and manage an MDD project. If you are already working on an MDD project, you will learn how to use Rational Software Architect to carry out your work. For solution architects Solution architects can expect to learn about the benefits of a model-driven approach to software development and how to determine whether it is a suitable approach for your project. You will learn how to put the ideas of MDD into practice using Rational Software Architect (RSA). You will also learn how to articulate the advantages of MDD to both project managers and technical colleagues. Copyright IBM Corp All rights reserved. xi

14 For project planners or project managers If you are a project planner or a project manager, you will learn about the benefits of a model-driven approach to software development and how to determine whether it is a suitable approach for your project. You will also learn how the MDD software life cycle differs from other approaches and how you can effectively plan and manage an MDD project. For those working on a project that uses model-driven development If you are reading this book because you are working on a project that has adopted MDD, then you will learn about the MDD approach: how an overall MDD project works and what your role is. You will also learn how to use RSA to carry out your work. The following chapters are recommended based on particular roles: If you are a solution architect or developer responsible for developing an application using an existing MDD framework, read all chapters, but in particular read: Chapter 1, Overview and concepts of model-driven development on page 3 Chapter 2, Scenario overview on page 17 Chapter 3, Model-driven development approach on page 29 Chapter 7, Designing patterns for the scenario on page 93 Chapter 8, Applying model-driven development with Rational Software Architect on page 129 If you are a solution architect responsible for developing an MDD framework, read all chapters, but in particular read: Chapter 1, Overview and concepts of model-driven development on page 3 Chapter 2, Scenario overview on page 17 Chapter 3, Model-driven development approach on page 29 Chapter 6, Model-driven development in context on page 73 Chapter 7, Designing patterns for the scenario on page 93 Chapter 9, Extending Rational Software Architect on page 161 xii Patterns: Model-Driven Development Using IBM Rational Software Architect

15 If you are a project manager, the following chapters may interest you the most: Chapter 1, Overview and concepts of model-driven development on page 3 Chapter 3, Model-driven development approach on page 29 Chapter 4, Model-driven development project planning on page 45 Chapter 5, Model-driven development solution life cycle on page 59 Chapter 10, Conclusion on page 219 If you are a pattern/transformation developer, the following chapters may interest you the most: Chapter 1, Overview and concepts of model-driven development on page 3 Chapter 3, Model-driven development approach on page 29 Chapter 8, Applying model-driven development with Rational Software Architect on page 129 Chapter 9, Extending Rational Software Architect on page 161 How this book is organized In this book, we present MDD as an approach to improving on the mainstream software development practice. MDD treats UML models as primary software artifacts from which consistent implementation artifacts can be generated. In Part 1, Approach on page 1, we describe the ideas behind MDD. We also explain how to apply MDD in practice using Rational Software Architect by introducing a scenario generalized from a number of real-world projects in which the authors participated. The scenario involves the development of integration services within a service-oriented architecture (SOA). In Part 2, Implementation on page 91, we explain how to apply MDD to the scenario. The information you need to reproduce the examples is included in the additional materials provided with this redbook. Preface xiii

16 The team that wrote this redbook A team of specialists from around the world working at the International Technical Support Organization (ITSO), Hursley Center, produced this redbook. Peter Swithinbank is a project leader at the ITSO, Hursley Center. He writes IBM Redbooks and teaches IBM classes worldwide building business integration solutions. Peter has worked for IBM for 27 years and has been with the ITSO for one year. He has a diploma in software engineering from Oxford University and an MA in Geography from the University of Cambridge. Mandy Chessell is a Senior Technical Staff Member (STSM) in the U.K. She has 18 years of experience in the middleware field. She holds a master degree in software engineering from the University of Brighton, U.K. Her areas of expertise include distributed transaction processing, object-oriented design, usability, and UML modeling. Dr. Tracy Gardner is a solution architect in the IBM Software Group Services in the U.K. She has over five years of industrial experience in model-driven development. She has written and presented extensively on model-driven development. She holds a Ph.D. in software engineering from the University of Bath. Catherine Griffin is a software engineer at IBM Hursley in the U.K. She has 10 years of experience in software development. Her areas of expertise include Eclipse and the Eclipse Modeling Framework. She holds a degree in mathematics from Nottingham University, U.K. Jessica Man is an IT specialist in the U.K. She has five years of experience in software development. Her areas of expertise include the JVM and tooling for Java and J2EE application development, deployment, runtime problem determination, and performance measurement. She holds a master degree in advanced computer science from the University of Manchester. Helen Wylie is a certified consultant IT architect in Hursley Architectural Services in the U.K. She has many years of experience in the IT industry and has focussed primarily on integration architectures in the last decade. Her areas of expertise are SOA and integration, and most recently the combination of patterns and models to support automated generation of services and deployment artifacts for deployment to an enterprise service bus (ESB). She holds a mathematics degree from the Open University and a post graduate diploma in computer science from Cambridge University. xiv Patterns: Model-Driven Development Using IBM Rational Software Architect

17 Larry Yusuf is a solution designer with Software Group Strategy and Technology based at the Hursley Labs in the U.K. He has four years of experience in Business Integration and modeling, with a particular focus on Business Process Management, Event and Solution Management, and Integration patterns. He has written and presented extensively on these topics. Credits and acknowledgements Without the sponsorship of Jonathan Adams, this book would not exist. We are all indebted to Jonathan for championing the adoption of pattern-based techniques in software architecture. He also was an assiduous reviewer. We also thank Ian Scott who worked with members of the team in applying these techniques to a large IT project. As well, we thank Charles Rivet, Lee Ackerman, Lisa Noon and David Kelsey for reading and commenting on the first draft for us. We also want to acknowledge the help of our many IBM colleagues, many formerly of Rational, who are working with us to apply modeling techniques to SOA and integration. Become a published author Join us for a two-to-six week residency program! Help write an IBM redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You will team with IBM technical professionals, Business Partners, or customers. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you will develop a network of contacts in IBM development labs, and increase your productivity and marketability. Find out more about the residency program, browse the residency index, and apply online at the following Web site: ibm.com/redbooks/residencies.html Preface xv

18 Comments welcome Your comments are important to us! We want our redbooks to be as helpful as possible. Send us your comments about this or other redbooks in one of the following ways: Use the online Contact us review redbook form found at: ibm.com/redbooks Send your comments in an to: Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HZ8 Building 662 P.O. Box Research Triangle Park, NC xvi Patterns: Model-Driven Development Using IBM Rational Software Architect

19 Part 1 Part 1 Approach This part describes model-driven development (MDD) as an approach to software development. We explain how to organize a software development project to use the MDD approach. Part 2, Implementation on page 91, takes you through the application of MDD to a hypothetical scenario that draws upon the experience of the team in real engagements. Chapter 1, Overview and concepts of model-driven development on page 3, provides a brief overview of what MDD is and describes some of its benefits. Chapter 2, Scenario overview on page 17, describes the scenario we selected to use throughout the book. MDD is not applicable to every scenario. We discuss the indications that suggest MDD is effective for the scenario we chose. In Chapter 3, Model-driven development approach on page 29, we step lightly into the waters of MDD and explain the key ideas behind model-driven development that we apply in the second part of the book. We wrote Chapter 4, Model-driven development project planning on page 45, with the project planner in mind, and we discuss how to introduce and manage an MDD project. Copyright IBM Corp All rights reserved. 1

20 Chapter 5, Model-driven development solution life cycle on page 59, continues in the planning vein and looks at the way MDD affects aspects of the solution life cycle that are not discussed elsewhere in the book. MDD is a rapidly advancing field, and in Chapter 6, Model-driven development in context on page 73, we discuss some of the currents in MDD and how they relate to some other aspects of software development. 2 Patterns: Model-Driven Development Using IBM Rational Software Architect