Scribd
Upload
23 views16 pages

Model Driven Architecture Vietnamese 1

Model driven architecture is a software design approach led by OMG that uses models at different abstraction levels from conceptual to implementation. It involves creating platform independent and specific models and transforming models to code. Key aspects include independent, platform independent and specific models, transformations, standards like UML and advantages like reusability.

Uploaded by

Văn Dũng
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
23 views16 pages

Model Driven Architecture Vietnamese 1

Model driven architecture is a software design approach led by OMG that uses models at different abstraction levels from conceptual to implementation. It involves creating platform independent and specific models and transforming models to code. Key aspects include independent, platform independent and specific models, transformations, standards like UML and advantages like reusability.

Uploaded by

Văn Dũng
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16

MODEL DRIVEN ARCHITECTURE

Võ Văn Dũng
Lê Văn Duy
Nguyễn Thị Phương Duyên

Group 3
1. What is Model Driven Architecture?
A software design methodology for
software systems development and
software deployment led by Object
Management Group (OMG).
Use a subset of UML models to
describe a system
Models at different levels of
abstraction are created from a
conceptual point of view to the
smallest implementation details .

Group 3
2. MDA approach
a. Independent calculation model
(CIM -Computation-Independent Model):
• Part of the field of systems modeling
and software projects.
• It focuses on describing the system
without being constrained by specifying
the details of the system to be
implemented or how it will be
implemented.
• Practical Examples and Applications:
- Hotel reservation system
- E-commerce system
2. MDA approach
b. The model is platform independent
(PIM - Platform Independent Model):
• Is a view of the system from a platform
independent perspective.
• A PIM represents a specific level of
platform independence.
• A PIM describes a software system that best
supports some business.
• Practical Examples and Applications:
-Develop cross-platform applications
-Manage complex projects
2. MDA approach
c.Platform specific model
(PSM - Platform Specific Model):
• Is the concept of a system from a specific
platform perspective.
• A PSM combines the specifications in the
PIM with details that determine how the
system uses a particular platform.
• A PIM is converted into one or more PSMs.
• Practical Examples and Applications:
-Microservices Architecture:
-IoT Devices:
2. MDA approach
d. Code
• The final step of software development is to
convert PSMs to code.
• Because at the PSM level the technology
has been specifically chosen, so it is
relatively easy to transition.
2. MDA approach
e. Transformation.
• Is the conversion process from PIM to PSM, and from PSM to specific source code.
• Transformation Types:
-Model-to-Model (M2M):
Example : Convert from PIM to PSM.
-Model-to-Code (M2C):
Example : Convert from PSM to Java or C# code.
• Practical Examples and Applications:
-Agile Development:
-Legacy System Migration:

Group 3
3. MDA standards

The MDA model is related to many


standards, including Unified Modeling
Language (UML), Meta Object Facility
(MOF), XML Metadata Interchange
(XMI), Enterprise Distributed Object
Computing (EDOC), Software Process
Engineering Metamodel (SPEM) and
Common Warehouse Metamodel
(CWM).
Implemented UML is the UML
configuration used when MDA was
introduced. Instead, OMG is now
promoting fUML. (The action language
for fUML is ALF.)
4.Advantages and disadvantages of MDA
 Advantage:
• Consistency and efficiency
• Reusability
• Scalability and flexibility
• Easy integration
Defect:
• Complicated at first
• Weak performance
• Possibility of realization
• Compatibility

Group 3
5.MDA's potential concerns

 Incomplete standards :The MDA


approach is anchored by many
technical standards, some of which are
yet to be defined or not yet developed
in a standard way
Vendor lock-in : Although MDA was
conceived as an approach to achieving
(technical) platform independence,
existing MDA vendors have been
reluctant to design their MDA toolkits
to can interact.
5.MDA's potential concerns

Idealistic : MDA was conceived as


a transitional engineering method
in which Action Language
programming combination
models are transformed into
implementation artifacts
Specialized skill sets :
Practitioners of MDA-based
software engineering (as well as
other toolkits) are required to
have a high level of expertise in
their field
6. Practical example
Some examples of how MDA can be used in a hospital environment :
• Developing a clinical decision support system:
• Create a patient data management system:
• Implementing a remote medical system:
7.Implement MDA

Step 1 : Requirements and Analysis


Step 2 : Create Platform-Independent
Model (PIM)
Step 3 : Preliminary design
Step 4 : Convert PIM to Platform-
Specific Model (PSM)
Step 5 : Convert PSM to Source Code
Step 6: Compile and Test
Step 7 : Deploy
8.MDA support tools: OpenMDX
• OpenMDX is a layer on top of the platforms, CORBA, .NET and provides a PIM
abstraction layer for the application.
• OpenMDX is framework-based, plugins can be deployed without code
generation on supporting platforms
• OpenMDX supports a large number of pre-deployed scenarios - code.
9. Introduce more about MDA

 Youtube link to learn about MDA:


https://www.youtube.com/watch?
v=q4PjRfO5Xyc&t=420s
 Reference books :

Group 3
THANK YOU AND THANK YOU
FOR LISTENING

Group 3

You might also like