Platform-specific model: Difference between revisions

Revision as of 15:59, 29 August 2008

Latest revision as of 11:10, 22 February 2025

(18 intermediate revisions by 16 users not shown)

Line 1:

{{Short description|Model of a software or business system}}
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]], [[document file format]] or [[database]]). Platform-specific models are indispensable for the actual implementation of a system.

For example, if a needbusiness needs to implement an online shop., then Thetheir software system will need to store informationdifferent regardingkinds users,of information: available goods, user info such as 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 database|Oracle]]'s [[SQL]] dialect. This [[Oracle database|Oracle]]'s specific [[relational model]] is an example of a ''Platform-specific model''.

In [[Model-driven architecture]], a platform-specific model is where the design of the model is constructed with the intended execution-platform driving design choices.<ref>{{cite book |url=https://www.google.com/books/edition/Software_Architecture/Xi-JoWzVF54C?hl=en&gbpv=1&dq=%22Platform-specific+model%22+-wikipedia&pg=PA76&printsec=frontcover |title=Software Architecture |first=Flavio |last=Oquendo |page=76 |date=2004}}</ref>

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]].

== See also ==

*[[platform-independent model]]

== Related Concepts ==

* [[ModelATLAS Transformation Language|MTL]] (ATL)

* [[Model-driven architecture]] (MDA is an OMG Trademark), (MDE is '''not''' an OMG Trademark)

* [[ModelDomain IntegratedSpecific ComputingLanguage]] (MICDSL)

* [[Domain-specific modelling]] (DSM)

* [[Eclipse Modeling Framework]] (EMF)

* [[Generic Modeling Environment]] (GME)

* [[Eclipse Modeling Framework]] (EMF)

* [[Graphical Modeling Framework]] (GMF)

* [[DomainMeta-Object Specific LanguageFacility]] (DSLMOF)

* [[Meta-modeling]]

* [[Domain-specific modelling]] (DSM)

* [[Model-based testing]] (MBT)

* [[Model-driven architecture]] (MDA)

* [[Meta-modeling]]

* [[ATLASModel Transformation Language|ATL]] (MTL)

* [[Object Constraint Language]] (OCL)

* [[VIATRA]]

* [[XMI]]

* [[OCL]]

* [[Model Transformation Language|MTL]]

* [[Meta-Object Facility|MOF]]

* [[Object-oriented analysis and design]] (OOAD)

* Visual Automated model Transformations [[VIATRA]]

* [[XML Metadata Interchange]] (XMI)

== References ==

{{Reflist}}

[[Category:Software architecture]]

[[Category:Systems engineering]]

[[de:Platform Specific Model]]

[[ja:プラットフォーム特化モデル]]