ISBN-10:
032119442X
ISBN-13:
9780321194428
Pub. Date:
05/05/2003
Publisher:
Addison-Wesley
MDA Explained: The Model Driven Architecture': Practice and Promise / Edition 1

MDA Explained: The Model Driven Architecture': Practice and Promise / Edition 1

by Anneke Kleppe, Jos Warmer, Wim Bast
Current price is , Original price is $44.99. You

Temporarily Out of Stock Online

Please check back later for updated availability.

Product Details

ISBN-13: 9780321194428
Publisher: Addison-Wesley
Publication date: 05/05/2003
Series: Addison-Wesley Object Technology Series
Edition description: New Edition
Pages: 192
Product dimensions: 7.10(w) x 9.00(h) x 0.50(d)

About the Author

Anneke Kleppe is a consultant and adviser at Klasse Objecten, which she founded in 1995 to train and coach companies on the use of object technology, modeling, and MDA. She was intensively involved in the development of the Unified Modeling Language (UML) and the new UML 2.0 standard. The author of several books, Anneke started a knowledge center for object technology at KPN Research in Leidschendam, Netherlands. She is a member of the authoring team of the OCL 2 standard, where she has a special focus on the definition of the semantics of the OCL.

Jos Warmer is the primary author of the OCL standard. He is an active member of the Unified Modeling Language (UML) Revision Task Force, which defined the revisions in the UML 2.0 standard. Previously he was a member of the UML core team, where he was responsible for the development of the Object Constraint Language (OCL). The author of several books and numerous international articles, Jos is an advisor on the UML method and techniques at the De Nederlandsche Bank.

Wim Bast is Compuware’s OptimalJ MDA architect.

032119442XAB07222003

Read an Excerpt

For many years, the three of us have been developing software using object-oriented techniques. We started with object-oriented programming languages like C++, Small-talk, and Eiffel. Soon we felt the need to describe our software at a higher level of abstraction. Even before the first object-oriented analysis and design methods like Coad/Yourdon and Object Modeling Technique (OMT) were published, we used our own invented bubble and arrow diagrams. This naturally led to questions like, “What does this arrow mean?” and “What is the difference between this circle and that rectangle?” We therefore rapidly decided to use the newly emerging methods to design and describe our software.

Over the years we found that we were spending more time on designing our models than on writing code. The models helped us to cope with larger and more complex systems. Having a good model of the software available made the process of writing code easier, and in many cases, even straightforward.

In 1997 some of us got involved in defining the first standard for object-oriented modeling called Unified Modeling Language (UML). This was a major milestone that stimulated the use of modeling in the software industry. When the OMG launched its initiative on Model Driven Architecture (MDA), we felt that this was logically the next step to take. People try to get more and more value from their high-level models, and the MDA approach supports these efforts.

At that moment we realized that all these years we had been naturally walking the path toward model-driven development. Every bit of wisdom we acquired during our struggle with the systems we had to build fitted in with this new idea of how to build software. It caused a feeling similar to an AHA-experience: “Yes, this is it!”—the same feeling we had years before when we first encountered the object-oriented way of thinking, and again when we first read the GOF book on design patterns. We feel that MDA could very well be the next major step forward in the way software is being developed. MDA brings the focus of software development to a higher level of abstraction, thereby raising the level of maturity of the IT industry.

We are aware of the fact that the grand vision of MDA, which Richard Soley, the president of the OMG, presents so eloquently, is not yet a reality. However, some parts of MDA can already be used today, while others are under development. With this book we want to give you insight into what MDA means and what you can achieve, both today and in the future.

Anneke Kleppe Jos Warmer Wim Bast Soest, the Netherlands, March 2003


Table of Contents

Introduction.

Who Should Read This Book.

How This Book Should Be Used.

Typeface Conventions.

Information on Related Subjects.

Book Support and Example Implementation.

Acknowledgments.

1: The MDA Development Process.

Traditional Software Development.

The Productivity Problem.

The Portability Problem.

The Interoperability Problem.

The Maintenance and Documentation Problem.

The Model Driven Architecture.

The MDA Development Life Cycle.

Automation of the Transformation Steps.

MDA Benefits.

Productivity.

Portability.

Interoperability.

Maintenance and Documentation.

MDA Building Blocks.

Summary.

2: The MDA Framework.

What Is a Model?

Relationships between Models.

Types of Models.

Business and Software Model.

Structural and Dynamic Models.

Platform Independent and Platform Specific Models.

The Target Platforms of a Model.

What is a Transformation?

Transformations between Identical Languages.

The Basic MDA Framework.

Examples.

Public and Private Attributes.

Associations.

Summary.

3: MDA Today.

OMG Standards.

OMG Languages.

OMG Language and Transformation Definitions.

UML as PIM Language.

Plain UML.

Executable UML.

UML-OCL Combination.

Tools.

Support for Transformations.

Categorizing Tools.

Development Processes.

Agile Software Development.

Extreme Programming.

Rational Unified Process (RUP).

Summary.

4: Rosa's Application of MDA.

Rosa's Breakfast Service.

The Business.

The Software System.

Applying the MDA Framework.

The PIM and PSMs.

The PIM to PSM Transformations.

The PSM to Code Model Transformations.

Three Levels of Abstraction.

The PIM in Detail.

Summary.

5: Rosa's PIM to Three PSMs.

The PIM to Relational Transformation.

The PIM to EJB Transformation.

A Coarse Grained EJB Model.

The Transformation Rules.

The PIM to Web Transformation.

The Transformation Rules.

The Communication Bridges.

Summary.

6: Rosa's PSMs to Code.

Relational Model to Code Transformation.

EJB Model to Code Transformation.

Some Remarks on EJB Code.

The Transformation Rules.

The Web Model to Code Transformation.

The Structure of the Web Code.

The Transformation Rules.

Summary.

7: More on Transformations.

Desired Features of Transformations.

Controlling and Tuning Transformations.

Manual Control.

Conditions on Transformations.

Transformation Parameters.

Additional Information.

Traceability.

Incremental Consistency.

Bidirectionality.

Implications on Transformations.

Transformation Parameters.

Persistent Source-Target Relationship.

Transformation Rules as Objects.

Summary.

8: Metamodeling.

Introduction to Metamodeling.

The Four Modeling Layers of the OMG.

Layer M0: The Instances.

Layer M1: The Model of the System.

Layer M2: The Model of the Model.

Layer M3: The Model of M2.

Getting Rid of the Layers.

The Use of Metamodeling in the MDA.

The Extended MDA Framework.

Summary.

9: Defining Your Own Transformations.

Transformations Definitions Revisited.

The Transformation Definition Language.

Requirements for a Transformation Rule.

A Notation for Transformation Rules.

Transformation Definitions.

Example Transformation Definitions.

Public and Private Attributes.

Associations.

Classes.

Finishing the Transformation Definition.

The Complete MDA Framework.

Summary.

10: Rosa's Transformation Definitions.

The UML to Relational Mapping.

Transformation Rules for UML to Relational Model.

Completion of the Relational Model.

The UML to EJB Mapping.

Additional Operations.

The UML to Web Mapping.

Summary.

11: OMG Standards and Additional Technologies.

Introduction.

The MOF.

yMOF Tools.

The Role of the MOF in MDA.

Query, Views, and Transformations.

UML.

The UML Metamodel.

The Role of UML in MDA.

OCL.

Using OCL with UML.

Using OCL with the MOF.

The Role of OCL in MDA.

The UML Action Semantics.

CWM.

UML Profiles.

The Role of Profiles in MDA.

Summary.

12: The MDA Promise.

The MDA Paradigm Shift.

A Historic Perspective.

A Shift of Focus.

Too Good to Be True?

The Development Process.

The Tools.

The Modeling Languages.

Summary.

Appendix A: Glossary.

Appendix B: The Code for Rosa's System.

The SQL Code for Rosa's System.

The EJB Code for Rosa's System.

The JSP Code for Rosa's System.

Bibliography.

Index. 032119442XT04072003

Preface

For many years, the three of us have been developing software using object-oriented techniques. We started with object-oriented programming languages like C++, Small-talk, and Eiffel. Soon we felt the need to describe our software at a higher level of abstraction. Even before the first object-oriented analysis and design methods like Coad/Yourdon and Object Modeling Technique (OMT) were published, we used our own invented bubble and arrow diagrams. This naturally led to questions like, “What does this arrow mean?” and “What is the difference between this circle and that rectangle?” We therefore rapidly decided to use the newly emerging methods to design and describe our software.

Over the years we found that we were spending more time on designing our models than on writing code. The models helped us to cope with larger and more complex systems. Having a good model of the software available made the process of writing code easier, and in many cases, even straightforward.

In 1997 some of us got involved in defining the first standard for object-oriented modeling called Unified Modeling Language (UML). This was a major milestone that stimulated the use of modeling in the software industry. When the OMG launched its initiative on Model Driven Architecture (MDA), we felt that this was logically the next step to take. People try to get more and more value from their high-level models, and the MDA approach supports these efforts.

At that moment we realized that all these years we had been naturally walking the path toward model-driven development. Every bit of wisdom we acquired during our struggle with the systems we had to build fitted in with this new idea of how to build software. It caused a feeling similar to an AHA-experience: “Yes, this is it!”—the same feeling we had years before when we first encountered the object-oriented way of thinking, and again when we first read the GOF book on design patterns. We feel that MDA could very well be the next major step forward in the way software is being developed. MDA brings the focus of software development to a higher level of abstraction, thereby raising the level of maturity of the IT industry.

We are aware of the fact that the grand vision of MDA, which Richard Soley, the president of the OMG, presents so eloquently, is not yet a reality. However, some parts of MDA can already be used today, while others are under development. With this book we want to give you insight into what MDA means and what you can achieve, both today and in the future.

Anneke Kleppe
Jos Warmer
Wim Bast
Soest, the Netherlands, March 2003

032119442XP04072003

Customer Reviews

Most Helpful Customer Reviews

See All Customer Reviews

MDA Explained: The Model Driven Architecture': Practice and Promise 5 out of 5 based on 0 ratings. 1 reviews.
Guest More than 1 year ago
There have been many talks about MDA, but none as 'complete' as this book. Granted that MDA is still under development and who knows what will actually happen to it when it is actually released, the authors of this book do an extraordinary job explaining what MDA is at its current stage and what areas might still change for the better before its final release. It is very difficult; as you may have had the pleasure of finding out the hard way, to actually implement true round trip engineering. It is a great concept on paper, but once you start the process of coding who has the time to go back and update the model? Update the use-cases and propagate the changes all the way down stream to the test cases? Specially if your project is under the gun and is already behind the schedule. The truth of the matter is that until today, modeling has been a great concept to kick things off, but many managers, project leads, etc... do not see the value of modeling and how it can improve their software. MDA is the answer to these questions... It's what we like to have if we had it all... It is a promise of something grand and it's being presented in this book as such. This book is the blue print of where things in the software development process will be 3-5 years from now. All and all, Anneke Kleppe, et. al. did an extraordinary job in putting this book together. MDA is a buzz word that we have been here for sometime now, and it is great to finally have a book such as MDA Explained that clarifies the concepts and sheds some light on what's coming and what to expect.