Platform-specific model: Difference between revisions

Revision as of 08:18, 22 April 2006

Latest revision as of 11:10, 22 February 2025

(33 intermediate revisions by 27 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.

Say forFor example, thatif youa wantbusiness needs to implement an online shop., Thethen their software system will need to store informationdifferent regardingkinds users,of information: available goods, user info such as credit cards, etc. YouThe designer might decide that you willto use for this purpose an [[Oracle database]]. For this to work, youthe designer will need to express your concepts (e.g. the concept of ana 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 [[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]].

== SeeRelated alsoConcepts ==

* [[ATLAS Transformation Language]] (ATL)

*[[platform-independent model]]

* [[Domain Specific Language]] (DSL)

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

* [[Eclipse Modeling Framework]] (EMF)

* [[Generic Modeling Environment]] (GME)

* [[Graphical Modeling Framework]] (GMF)

* [[Meta-Object Facility]] (MOF)

* [[Meta-modeling]]

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

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

* [[Model Transformation Language]] (MTL)

* [[Object Constraint Language]] (OCL)

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

* Visual Automated model Transformations [[VIATRA]]

* [[XML Metadata Interchange]] (XMI)

== References ==

{{Reflist}}

[[Category:Software architecture]]

[[Category:Systems engineering]]