Model-Driven Architecture (MDA) Process

Model-Driven Architecture (MDA) is a software development approach that uses models to separate business logic from technology, enhancing flexibility and adaptability across platforms. The MDA process consists of four phases: Computation Independent Model (CIM), Platform Independent Model (PIM), Platform Specific Model (PSM), and Code Generation, each focusing on different levels of abstraction. MDA is particularly beneficial in industries like banking and finance, allowing for technology agnosticism, regulatory compliance, and scalability.

Uploaded by

jhegs tindugan

Available Formats

Download as PPTX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

8 views

Model-Driven Architecture (MDA) Process

Uploaded by

jhegs tindugan

Available Formats

Download as PPTX, PDF, TXT or read online on Scribd

You are on page 1/ 16

Model-Driven Architecture (MDA) Process

Model-Driven Architecture (MDA) is a software development approach defined

by the Object Management Group (OMG). It emphasizes the use of models to
drive the design, development, and deployment of software systems. Instead of
writing platform-specific code from the start, MDA focuses on abstract modeling
and then transforms these models into implementation-specific details.
Introduction to MDA
MDA separates business logic from technology to improve
flexibility.

Example: A banking system can migrate easily from one platform

to another.
Core Concepts & Benefits
- PIM, PSM, Code Generation
- Increased Flexibility

Example: A retail e-commerce system can quickly adapt to

different platforms.
Phases of MDA Process
MDA consists of four major phases, each representing different levels of abstraction:
1.Computation Independent Model (CIM)
1. Also called the Business Model.
2. Focuses on business processes and requirements without worrying about
technology.
3. Example: A company defines an online booking system process without discussing
databases or programming languages.
2.Platform Independent Model (PIM)
1. Describes the system’s functionality and structure without specifying the
technology or platform.
2. Example: A UML (Unified Modeling Language) diagram showing how different
components of a system interact.
3.Platform Specific Model (PSM)
1. Converts the PIM into a model tailored to a specific platform like Java, .NET, or
Python.
2. Example: If the PIM was technology-neutral, a PSM would define how the system
will be implemented in Spring Boot for Java or Django for Python.
4.Code Generation
1. The PSM is transformed into actual executable code using MDA tools.
2. Example: An MDA tool like Eclipse Modeling Framework (EMF) generates Java
code from the designed models.
Computation Independent Model (CIM)
Defines
business
needs
without
technical
details.

Example: An
online
booking
system
describes its
user flows.
Platform Independent Model (PIM)
Models the system
without platform
specifics.

Example: A hospital
management system
defines data flows
without tech
constraints.
A hospital manageme
nt system.pdf
Platform Specific Model (PSM)
Adapts the model to a specific technology.

Example: Transforming a PIM into a Java-based web application.

Code Generation
Automatically converts PSM to executable code.
MDA Tools
Popular tools: MagicDraw, Eclipse Modeling Framework.

Example: Automotive industry uses MDA tools to model control

systems.

MDA Tools for Automotive Industry

MDA in Finance
Banks use MDA to separate
business logic from
technology.

Example: Loan processing

models adapting across
digital platforms.
1. What is MDA in Banking?
MDA in Finance
MDA (Model-Driven Architecture) is a design pattern that allows banks to decouple their business
logic from the underlying technology stack. It ensures that business rules, workflows, and services
remain independent of specific programming languages, databases, or frameworks.
2. Why Do Banks Use MDA?
•Technology Agnosticism: Banks can change technologies (e.g., migrate from legacy systems to
cloud) without rewriting business logic.
•Regulatory Compliance: Business rules can be updated independently to comply with new financial
regulations.
•Scalability: Supports high transaction volumes across different systems.
•Security & Risk Management: Keeps critical financial processes secure while allowing tech
upgrades.
3. MDA Structure in Banking
MDA typically consists of three key layers:
1.Business Logic Layer
1. Defines banking rules, workflows, and transaction policies.
2. Example: Loan approval criteria, fraud detection rules.
2.Technology Layer
1. Handles infrastructure, databases, APIs, and UI frameworks.
2. Example: Java-based microservices, cloud computing.
3.Integration Layer
1. Connects business logic with external systems (e.g., payment gateways, third-party APIs).
2. Example: API gateways for Open Banking.
Challenges in MDA
Requires expertise and tool support.