Platform-specific model: Difference between revisions
m Date maintenance tags and general fixes |
Wikification, a start |
||
| Line 5: | Line 5: | ||
The term ''platform-specific model'' is most frequently used in the context of the [[model-driven architecture|MDA]] approach. This '''MDA''' approach corresponds the [[Object Management Group|OMG]] vision of [[Model Driven Engineering]]. The main idea is that it should be possible to use a [[Model Transformation Language|MTL]] to transform a [[Platform-independent model]] into a Platform-specific model. In order to achieve this transformation, one can use a language compliant to the newly defined [[QVT]] standard. Examples of such languages are [[AndroMDA]], [[VIATRA]] or [[ATLAS Transformation Language|ATL]]. |
The term ''platform-specific model'' is most frequently used in the context of the [[model-driven architecture|MDA]] approach. This '''MDA''' approach corresponds the [[Object Management Group|OMG]] vision of [[Model Driven Engineering]]. The main idea is that it should be possible to use a [[Model Transformation Language|MTL]] to transform a [[Platform-independent model]] into a Platform-specific model. In order to achieve this transformation, one can use a language compliant to the newly defined [[QVT]] standard. Examples of such languages are [[AndroMDA]], [[VIATRA]] or [[ATLAS Transformation Language|ATL]]. |
||
| ⚫ | |||
| ⚫ | |||
== Related Concepts == |
== Related Concepts == |
||
| Line 25: | Line 24: | ||
* [[Meta-Object Facility|MOF]] |
* [[Meta-Object Facility|MOF]] |
||
* [[Object-oriented analysis and design]] (OOAD) |
* [[Object-oriented analysis and design]] (OOAD) |
||
| ⚫ | |||
| ⚫ | |||
== References == |
|||
{{unreferenced}} |
|||
[[Category:Software architecture]] |
[[Category:Software architecture]] |
||
Revision as of 15:31, 23 April 2009
A platform-specific model is a model of a software or business system that is linked to a specific technological platform (e.g. a specific programming language, operating system or database). Platform-specific models are indispensable for the actual implementation of a system.
For example, a need to implement an online shop. The system will need to store information regarding users, goods, credit cards, etc. The designer might decide to use for this purpose an Oracle database. For this to work, the designer will need to express concepts (e.g. the concept of a user) in a relational model using the Oracle's SQL dialect. This Oracle's specific relational model is an example of a Platform-specific model.
The term platform-specific model is most frequently used in the context of the MDA approach. This MDA approach corresponds the OMG vision of Model Driven Engineering. The main idea is that it should be possible to use a MTL to transform a Platform-independent model into a Platform-specific model. In order to achieve this transformation, one can use a language compliant to the newly defined QVT standard. Examples of such languages are AndroMDA, VIATRA or ATL.
Related Concepts
- Model-driven architecture (MDA is an OMG Trademark), (MDE is not an OMG Trademark)[clarification needed]
- Model Integrated Computing (MIC)
- Generic Modeling Environment (GME)
- Eclipse Modeling Framework (EMF)
- Graphical Modeling Framework (GMF)
- Domain Specific Language (DSL)
- Domain-specific modelling (DSM)
- Model-based testing (MBT)
- Meta-modeling
- ATL
- VIATRA
- XMI
- OCL
- MTL
- MOF
- Object-oriented analysis and design (OOAD)
See also
References
 |