Model Driven Architecture in the EnterpriseSlide 2Project GoalsMDA BenefitsMDA Development LifecycleCriteria ExplanationCriteria Explanation Cont’dSlide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Together Architect 2006 for EclipseSlide 23Slide 24Slide 25Slide 26Slide 27Slide 28Slide 29Slide 30I-Logix RhapsodySlide 32Criteria Explanation [1]Slide 34Slide 35Slide 36Slide 37Slide 38Slide 39Slide 40Slide 41Slide 42Slide 43Slide 44Slide 45Slide 46Slide 47Slide 48OptimalJ by CompuwareOptimalJDomain Model (PIM)Application Model (PSM)Database Model (DBMS) ScreenshotCode ModelOptimalJ’s CycleApplication Server ExampleOptimalJ evaluationOptimalJ evaluation cont’dSlide 59Slide 60MagicDraw UML 10.0Features of MagicDrawSlide 63Slide 64Slide 65Slide 66Slide 67Slide 68Slide 69Comparison ChartResultsFuture OutlookQuestions?Model Driven Architecture in the Enterprise•Project Goal•Brief MDA Overview and Refresher•Evaluation Criteria•Evaluation of MDA Supported Tools–Borland Together Architect 2006 for Eclipse–Logix Rhapsody Developer Edition–OptimalJ Developer Edition by IntelliJ 4.0.00–MagicDraw UML 10.0•Modeling Tools Supporting MDA•Project Current StatusAmit, Keyur, Sabhay and SalehModel Driven Architecture in the EnterpriseProject Goals•MDA Conception and Background•Develop Criteria for MDA-Tools Evaluation•Evaluation of Tools and Techniques–Try selected MDA-tools•Final Report with conclusions and future outlookMDA Benefits•Productivity:–Work is done mainly at the PIM level–PIM-to-code transformation is automated–Caveat: need to define transformations, but they can be reused (hopefully)•Portability:–PIMs are implementation-independent–Incorporate new technologies by defining new (reusable) transformations•Interoperability:–MDA tools should generate bridges•Maintenance/Documentation:–Changes to the PIM can be filtered down to PSM/code by re-applying transformationsMDA Development Lifecycle•MDA lifecycle similar to traditional lifecycle, but:–Emphasis on creation of formal models (i.e., models that can be understood by computer)•2 types of models:–Platform-independent model–Platform-specific model•3 types of transformations:–PIM-to-PIM–PIM-to-PSM–PSM-to-code•Importance of transformation automationrequirementsanalysisdesigncodingtestingdeploymentPIMPSMCodeCodeMostly textMDAProcessCriteria ExplanationMDA01 -Support for PIMa. Support of at least one PIM (Generic UML and domain-tagged UML profiles can be considered PIM)b. Support Multiple Viewpoint PIMc. PIM extensibility (custom Metamodels)d. PIM Metamodel editing facilityCriteria Explanation Cont’dMDA02 -Support of PSMa. Support at least one PSM (platform in the sense of middleware)b. Platform-tagged UML profiles count as PSM(PIM to PSM is a critical requirement of MDA)Criteria Explanation Cont’dMDA03 -Can Target Multiple PSMa. Target more than one PSM, e.g. J2EE and .NETb. PSM extensibilityc. PSM Metamodel editing facilityCriteria Explanation Cont’dMDA04 -Model Integrationa. Multiple diagrams of the same typeb. Multiple diagram typesc. Multiple viewpoints feed the same transformationCriteria Explanation Cont’dMDA05 -System Evolutiona. Source code managementb. Forward propagation of changesc. Efficient-forward propagation of changes (updates only)Criteria Explanation Cont’dMDA06 -Model Interoperabilitya. Import models from other legacy toolsb. Import XMIc. Export XMICriteria Explanation Cont’dMDA07 -Mappings are modeleda. Legacy-customizable Model-to-Code mappingsb. Quasi-standard QVT Model-to-Code mappingsCriteria Explanation Cont’dMDA08 -Support for Managing Model Complexitya. Locating modeling elements in modelsb. Zooming in and outCriteria Explanation Cont’dMDA09 –Correctnessa. Modeling tool checks static models based on the corresponding metamodelsb. Allow more rules to be defined and checkedCriteria Explanation Cont’dMDA10 –Expressivitya. language "can" express any instance of the domain it is modelingb. support expressive higher levels of abstraction (PIM)Criteria Explanation Cont’dMDA11 -Patterns and Genericitya. Use of ready-made patterns in code generationb. Use of ready-made patterns in transformationsc. User-defined patternsCriteria Explanation Cont’dMDA12 -Support for Refactoringa. Generate Model given Codeb. Propagate code changes to model (roundtrip)Criteria Explanation Cont’dMDA13 -Intra-Model Mappingsa. Built-in Model-to-Model Mappings (transformations)b. Immediate propagation of changes between models related by transformationsc. Legacy-customizable transformationsd. QVT Model-to-Model mappingsCriteria Explanation Cont’dMDA14 -Traceabilitya. PSM elements reference PIM elements where they originateb. Reverse propagation of changes in PSMCriteria Explanation Cont’dMDA15 -Life Cyclea. Analysis, b. Design, c. Implementation, d. TestingCriteria Explanation Cont’dMDA16 -Standardizationa. UMLb. MOFc. XMId. QVTTogether Architect 2006 for Eclipse•Borland Together Architect 2006 for Eclipse is a comprehensive modeling solution for software architects.•Uses an Eclipse environment with built modeling support by Together Architect.•Enables architects to design, develop, and communicate enterprise application architectures. •Designers can create UML and business process models.Together Architect 2006 for Eclipse•Support for Model Driven Architecture (MDA) –Meta-models:•Tool has a large library of meta-model definitions for technology mapping•These meta-models can be viewed in meta-model browser view.•There is no support for editing existing meta-model or creating own meta-model•Meta-models are used for transforming models into models and code.Metamodel browser screenshotTogether Architect 2006 for Eclipse•Support for Model Driven Architecture (MDA) –Model to Model Transformations:•Open new MDA transformation project•Uses OMG’s Query View Transformation (QVT) in model-to model transformations•Specify input and output meta-models to import in QVT script•Transforms and instance of one Together or EMF model to an instance of another Together or EMF model•QVT Editor and Eclipse QVT Debugger enable code sensitive editing and step by step trace of the execution.Example of the QVT transformation script fileTogether Architect 2006 for Eclipse•Support for Model Driven Architecture (MDA) –Model to Text (Code) Transformations:•Open new MDA
View Full Document
Unlocking...