(Translated by https://www.hiragana.jp/)
Platform-specific model: Difference between revisions - Wikipedia Jump to content

Platform-specific model: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Thijs!bot (talk | contribs)
m r2.6.3) (robot Adding: pt:Modelo Específico de Plataforma
RedBot (talk | contribs)
m r2.5.2) (robot Modifying: pt:Modelo específico de plataforma
Line 33: Line 33:


[[ja:プラットフォームとくモデル]]
[[ja:プラットフォームとくモデル]]
[[pt:Modelo Específico de Plataforma]]
[[pt:Modelo específico de plataforma]]

Revision as of 11:47, 15 March 2011

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.

See also

References