book

MDA Explained: The Model Driven Architecture™: Practice and Promise

by Anneke Kleppe, Jos Warmer, Wim Bast

April 2003

Intermediate to advanced

192 pages

4h 8m

English

Addison-Wesley Professional

Read now

Unlock full access

Who Should Read This BookHow This Book Should Be UsedTypeface ConventionsInformation on Related SubjectsBook Support and Example ImplementationAcknowledgments
1.1. Traditional Software Development1.1.1. The Productivity Problem1.1.2. The Portability Problem1.1.3. The Interoperability Problem1.1.4. The Maintenance and Documentation Problem1.2. The Model Driven Architecture1.2.1. The MDA Development Life CyclePlatform Independent ModelPlatform Specific ModelCodeRaising the Level of Abstraction1.2.2. Automation of the Transformation Steps1.3. MDA Benefits1.3.1. Productivity1.3.2. Portability1.3.3. Interoperability1.3.4. Maintenance and Documentation1.4. MDA Building Blocks1.5. Summary
2.1. What Is a Model?2.1.1. Relationships between Models2.2. Types of Models2.2.1. Business and Software Models2.2.2. Structural and Dynamic Models2.2.3. Platform Independent and Platform Specific Models2.2.4. The Target Platforms of a Model2.3. What is a Transformation?2.3.1. Transformations between Identical Languages2.4. The Basic MDA Framework2.5. Examples2.5.1. Public and Private Attributes2.5.2. Associations2.6. Summary
3.1. OMG Standards3.1.1. OMG Languages3.1.2. OMG Language and Transformation Definitions3.2. UML as PIM Language3.2.1. Plain UML3.2.2. Executable UML3.2.3. UML–OCL Combination3.3. Tools3.3.1. Support for TransformationsPIM to PSM Transformation ToolsPSM to Code Transformation ToolsPIM to Code Transformation ToolsTunable Transformation ToolsTransformation Definition Tools3.3.2. Categorizing ToolsSelecting Tools3.4. Development Processes3.4.1. Agile Software Development3.4.2. Extreme Programming3.4.3. Rational Unified Process (RUP)3.5. Summary
4.1. Rosa's Breakfast Service4.1.1. The Business4.1.2. The Software System4.2. Applying the MDA Framework4.2.1. The PIM and PSMs4.2.2. The PIM to PSM Transformations4.2.3. The PSM to Code Model Transformations4.2.4. Three Levels of Abstraction4.3. The PIM in Detail4.4. Summary

5.1. The PIM to Relational Transformation5.2. The PIM to EJB Transformation5.2.1. A Coarse Grained EJB Model5.2.2. The Transformation Rules5.3. The PIM to Web Transformation5.3.1. The Transformation Rules5.4. The Communication Bridges5.5. Summary
6.1. Relational Model to Code Transformation6.2. EJB Model to Code Transformation6.2.1. Some Remarks on EJB Code6.2.2. The Transformation Rules6.3. The Web Model to Code Transformation6.3.1. The Structure of the Web Code6.3.2. The Transformation Rules6.4. Summary
7.1. Desired Features of Transformations7.2. Controlling and Tuning Transformations7.2.1. Manual Control7.2.2. Conditions on Transformations7.2.3. Transformation Parameters7.2.4. Additional Information7.3. Traceability7.4. Incremental Consistency7.5. Bidirectionality7.6. Implications on Transformations7.6.1. Transformation Parameters7.6.2. Persistent Source-Target Relationship7.6.3. Transformation Rules as Objects7.7. Summary
8.1. Introduction to Metamodeling8.2. The Four Modeling Layers of the OMG8.2.1. Layer M0: The Instances8.2.2. Layer M1: The Model of the System8.2.3. Layer M2: The Model of the Model8.2.4. Layer M3: The Model of M28.2.5. Getting Rid of the Layers8.3. The Use of Metamodeling in the MDA8.3.1. The Extended MDA Framework8.4. Summary
9.1. Transformations Definitions Revisited9.2. The Transformation Definition Language9.2.1. Requirements for a Transformation Rule9.2.2. A Notation for Transformation Rules9.2.3. Transformation Definitions9.3. Example Transformation Definitions9.3.1. Public and Private Attributes9.3.2. Associations9.3.3. Classes9.3.4. Finishing the Transformation Definition9.4. The Complete MDA Framework9.5. Summary
10.1. The UML to Relational Mapping10.1.1. Transformation Rules for UML to Relational Model10.1.2. Completion of the Relational Model10.2. The UML to EJB Mapping10.2.1. Additional Operations10.3. The UML to Web Mapping10.4. Summary
11.1. Introduction11.2. The MOF11.2.1. yMOF ToolsThe MOF Repository InterfaceModel Interchange11.2.2. The Role of the MOF in MDA11.3. Query, Views, and Transformations11.4. UML11.4.1. The UML MetamodelRelationship between UML and the MOF11.4.2. The Role of UML in MDA11.5. OCL11.5.1. Using OCL with UML11.5.2. Using OCL with the MOF11.5.3. The Role of OCL in MDA11.6. The UML Action Semantics11.7. CWM11.8. UML Profiles11.8.1. The Role of Profiles in MDA11.9. Summary
12.1. The MDA Paradigm Shift12.1.1. A Historic Perspective12.1.2. A Shift of Focus12.1.3. Too Good to Be True?12.2. The Development Process12.3. The Tools12.4. The Modeling Languages12.5. Summary
Glossary
B.1. The SQL Code for Rosa's SystemB.2. The EJB Code for Rosa's SystemB.3. The JSP Code for Rosa's System

Content preview from MDA Explained: The Model Driven Architecture™: Practice and Promise

Foreword

“The sooner you start, the longer it takes.” This paradoxical slogan was coined by Fred Brooks in 1975 in his seminal software engineering text, The Mythical Man Month, to emphasize that in software projects preparation is never wasted. If you skimp on requirements capture, you'll waste effort designing things the customer doesn't want. If you skimp on design, you'll write a lot of pointless code that doesn't solve his problem . . . and so on.

Dr. Brooks' dictum reminds us that Good Design Matters. It's just as true now as it was twenty-five years ago, but much else has changed. His book was based on his experience with OS/360, at that time one of the largest software projects ever undertaken. Since then, software size and complexity have ...