Platform-specific model: Difference between revisions

Revision as of 19:44, 13 September 2004

Revision as of 09:45, 15 February 2005

Line 1:

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.

Say for example that you want to implement an online shop. The system will need to store information regarding users, goods, credit cards, etc. You might decide that you will use for this purpose an [[Oracle database]]. For this to work you will need to express your concepts (e.g. the concept of an 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''.

Platform-specific models are indispensable for the actual implementation of a system.

Say for example that you want to implement an online shop.

The system will need to store information regarding users, goods, credit cards, etc.

You might decide that you will use for this purpose an [[Oracle database]].

For this to work you will need to express your concepts (e.g. the concept of an 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''.

The term ''platform-specific model'' is most frequently used in the context of [[model-driven architecture]]s.

== See also ==
[[platform-independent model]].