MDA
Download as PPT, PDF1 like998 views
Model Driven Architecture (MDA) is an approach proposed by the Object Management Group to address challenges of business and technology change by separating business logic and system specifications from implementation details using model-driven engineering. MDA uses standards like UML, MOF, and XMI to transform platform-independent models into specific platforms through automated transformations. Adopting MDA promises benefits like increased portability, interoperability, and adaptability of systems while reducing costs and shortening development times.
MDA
- 1. Model Driven Architecture “The Architecture of choice for a changing world” Preetam Palwe Aftek Limited
- 2. Roadmap Need for MDA What is MDA How MDA works Tools and Specifications Advantages Concerns Road ahead
- 3. Satisfaction with IT projects remains low? New apps or changes to existing apps are delivered in time frame needed? New apps or changes to existing apps are delivered at expected quality levels? What say you ? Strongly agree Disagree Somewhat disagree Somewhat agree Agree Strongly agree
- 4. Are we on same pitch?
- 5. Requirements gathering is a root cause 40%-55% errors found in QA are actually requirements issues Up to 70% of rework is caused by bad requirements
- 6. Limitations of traditional solutions Requirements management tools: Describe “what” not “how” — requirements are not specifications Useful for managing and tracing requirements, not gathering them UML models: Too abstract for business users Can create a false sense of agreement Mockups — Visio/PPT: Can be high fidelity, but don’t allow users to interact Coded prototypes: Expensive and time-consuming to build Require high technical skills Risk preempting technology decisions
- 7. Understanding requirements is hard!
- 8. Can MDA help? What is MDA? Specification by Object Management Group (OMG) Open and vendor neutral software design approach to challenge of business and technology change Based on various standards like UML, MOF, XMI, CWM Enforce portability, interoperability and adaptively of systems Automatic transformations using tools
- 9. How it works? Forward engineering approach
- 10. How it works? (cont.)
- 11. Are there any tools for this? QVT standard (Queries/Views/Transformations ) Model to Model transformation No Model to Text and Text to Model transformation Types of tools Creational Analysis Transformation Composition Test Simulation Metadata management Reverse engineering Implementations IBM-Rational RAD Eclipse EMF Microsoft DSL tools (?)
- 12. Key requirements Portable PIM independent of business and technology specifications Interoperable Defining, managing, publishing and sharing metadata Adaptive Adaptive Object Model (AOM) Runtime interpretation of model
- 13. Different standards satisfying requirements UML (Unified Modeling Language) Based on MOF, provides visual artifacts to model systems UML compliance not required MOF (Meta-Object Facility) Common, abstract language for modeling models MetaModel for compliance and transformations Define rules for mapping MOF MetaModel to platform independent interfaces XMI (XML Metadata Interchange) Translate MOF MetaModel to XML representation CWM (Common Warehouse MetaModel) Model data space (data mining across databases) and not application space like UML
- 14. Advantages Platform independence by modeling specifications independent of technology Cost reduction throughout application life cycle by virtually eliminating re-work Reduced development time for new applications Rapid inclusion of emerging technology benefits into existing systems Software prototyping (e.g. AppWeaver)
- 15. Concerns? Incomplete standards E.g. xtUML, QVT Vendor lock in Idealistic OMG track record E.g. CORBA J2EE specific E.g. UML class and C# properties Document incompatibility E.g. XMI and MOF version incompatibility questions its model serialization approach Does not support software product lines
- 16. Solution Domain Specific Languages Approach by Microsoft Called as Domain Specific Development because modeling language can only clearly define the problem domain UML as a diagramming tool with domain specific extensions if needed Domain specific schemas to represent model Models are essentially creating configuration code for the framework, patterns One of the pillars of software factory approach by Microsoft
- 17. What's in store for us? Visual studio DSL for defining / modeling DSL for attendance domain. Model driven rule engine for CARS? Config Utility of DHG2.0. Is this a DSL for Home Automation? Metadata sharing by various DVGs / Devices. Adaptive Object Modeling? uPnP?
- 18. Thank You ! Note: This presentation was made purely for educational purpose and the data used to prepare this is taken from various resources available on internet.