MDA vs MDD

By Tim Ackroyd on

This post kicks of a new series on UML Operator Channel UML Operator Channel around systems and software delivery, titled "Model-Driven Anything". Subscribe, turn on notifications, follow, and most importantly...Contribute 😎

IMPORTANT NOTE: Never start a software development effort without Requirements!!! or Scope!!! However, sometimes software starts out as a means of developing scope and requirements!

So what are we talking about?

Model-Driven Architecture (MDA) and Model-Driven Development (MDD) are both approaches within the realm of software development that emphasize the use of models as primary artifacts in the software engineering process. However, they have distinct focuses and methodologies. Here are the key differences between the two:

Model-Driven Architecture (MDA)

Origin and Standardization:

  • Origin: MDA is a software design approach proposed by the Object Management Group (OMG).
  • Standardization: It is a well-defined framework with standardized guidelines and specifications.

Core Concept:

  • MDA is based on the separation of concerns, using models to describe different aspects of a system at varying levels of abstraction.

Abstraction Levels:

  • Computation Independent Model (CIM): Describes the system's business context without considering system details.
  • Platform Independent Model (PIM): Focuses on the system's functionality and behavior without considering platform specifics.
  • Platform Specific Model (PSM): Tailors the PIM to specific platforms, adding details needed for the implementation on a particular technology.

Transformation:

  • Emphasizes model transformations between different levels of abstraction (e.g., from PIM to PSM).

Standards and Tools:

  • Utilizes standards such as UML (Unified Modeling Language), XMI (XML Metadata Interchange), and MOF (Meta-Object Facility).
  • Often supported by specific tools that adhere to OMG's standards.

Model-Driven Development (MDD)

Origin and Flexibility:

  • Origin: MDD is a broader and more general approach that encompasses any development methodology that relies heavily on models.
  • Flexibility: It is not tied to a specific set of standards or frameworks and can be adapted to various contexts.

Core Concept:

  • MDD focuses on using models as primary artifacts throughout the software development lifecycle, from requirements to design, implementation, and testing.

Approach:

  • Models are used to generate executable code, documentation, and other development artifacts.
  • The approach can vary greatly, with some methodologies using specific types of models or tools.

Transformation:

  • While transformations are part of MDD, they are not as strictly defined as in MDA. The emphasis is more on the practical use of models to directly support development tasks.

Tools and Techniques:

  • Uses a variety of modeling languages (not just UML), domain-specific languages (DSLs), and other tools tailored to specific development needs.
  • More adaptable to incorporating new modeling techniques and tools.

Summary

  • MDA is a standardized, framework-based approach proposed by OMG, focusing on model transformations across different levels of abstraction using specific standards and tools.
  • MDD is a broader, more flexible approach that emphasizes the use of models throughout the development process, without being tied to specific standards or frameworks.

By understanding these differences, organizations can better choose the approach that aligns with their project requirements, goals, and existing workflows.

Conclusion

What we will expose, in this video series, are the core concepts in Enterprise, Solution, and Application Architecture to most effectively deliver Systems and Software. If you are new to software delivery, this will give you an idea of what is necessary to deliver this architecture based on my 30+ years in this business. If you are an experienced Systems/Software Architect, at any level, you should be able to relate and contribute.

Things you will Learn

  1. What is MDD/MDA and how to get started
  2. The benefits of MDD and MDA
  3. How to apply these concepts in Sparx Enterprise Architect (EA)
  4. Integration between your "modeling environment" and your Integrated Development Environment (IDE)
  5. Demonstrate these concepts in a real project, from Requirements to Release
    And more....
Visit and join UML OperatorUML Operator to get started.

Comments

Post a Comment

Popular posts from this blog

Sparx EA and Open Collaboration

By Tim Ackroyd on
I get asked, quite often, "Is there a way to integrate Sparx Enterprise Architect (EA) with other tooling?" My answer is always, "Yes". There are multiple approaches, from very simple to more advanced. I have helped several shops do this over the years, and may do videos on this in the future. Integrating Sparx with Azure DevOps and other Cloud platforms, as well as other Tooling, is very possible and beneficial for managing delivery, such as requirements, problem solving, design, and development... all in a unified way.  The integration can allow companies/shops to seamlessly synchronize between Sparx EA's modeling environment and platforms, such as Azure DevOps'. Remember that one of the biggest benefits of Sparx EA over other modeling platforms, is that Sparx is based on Data-First implementation and supports open integration. Years ago, something call Open Services for Lifecycle Collaboration (OSLC) came out and Sparx was one of the first to embrace it. ...
Read more

BPMN Diagram versus Sequence Diagram

By Tim Ackroyd on
I am getting some great questions in our  UML Operator Channel , as we are publishing  a series on Business Process Modeling Notation (BPMN) . Modelers see the term "Sequence" in BPMN and get a little confused...probably my fault 😏. When using BPMN, just understand the difference between Unified Modeling Language (UML) and BPMN (an extension of UML) and things should fall into place. So now let's talk about BPMN vs UML Sequence Diagrams... BPMN Diagram versus Sequence Diagram BPMN diagrams and sequence diagrams are both types of visual representations used in the field of business process modeling and software engineering, respectively. While they share some similarities, they serve different purposes and focus on different aspects of a system or process. BPMN Diagram: Purpose: BPMN (Business Process Model and Notation) is used for modeling and documenting business processes. It provides a standardized way to r...
Read more