Reference model: Difference between revisions

Revision as of 02:58, 22 November 2008

Revision as of 12:57, 3 December 2008

Line 1:

A '''Reference model''' is a model of something that embodies the basic goal or idea of something and can then be looked at as a reference for various purposes.

== Overview ==

== Understanding a Reference Model ==

There are a number of concepts rolled up into that of a 'reference model.' Each of these concepts is important:

* '''Abstract''': a reference model is abstract. The things described by a reference model are not actual things, but an abstract representation of things. Therefore, when describing the architecture of a house, an actual exterior wall may have dimensions and materials, but the concept of a wall is part of the reference model. One must understand the concept of a wall in order to build a house that has walls.

* '''Entities and Relationships''': A reference model contains both entities (things that exist) and relationships (how they interact with one another). A list of entities, by itself, is not sufficient to describe a reference model.

* '''Within an environment''': A reference model does not attempt to describe "all things." A reference model is used to clarify "things within an environment" or a problem space. To be useful, a reference model should include a clear description of the problem that it solves, and the concerns of the stakeholders who need to see the problem get solved.

* '''Technology Agnostic''': A reference model is not useful if it makes assumptions about the technology or platforms in place in a particular computing environment. A reference model is a mechanism for understanding the problems faced, not the solutions involved, and as such, must be independent of the selected solutions in order to provide value to the practitioner. Note: That does not preclude the development of a reference model that describes a set of software applications, because the problem space may be "how to manage a set of software applications."

== The Uses of a Reference Model ==

Line 20:

A fifth use of a reference model is to allow the comparison of different things. By breaking up a problem space into basic concepts, a reference model can be used to examine two different solutions to that problem. In doing so, the component parts of a solution can be discussed in relation to one another. For example, if a reference model describes computer systems that help track contacts between a business and their customers ([[Customer Relationship Management]]), then a reference model can be used by a business to decide which of five different software products to purchase, based on their needs. A reference model, in this example, could be used to compare how well each of the candidate solutions can be configured to meet the needs of a particular business process.

== Examples ==

Instances of reference models include, among others:

* the [[Agent Systems Reference Model]],

Instances of reference models include, among others: the [[RM-ODP|Reference Model of Open Distributed Processing]], the [[OSI model|Open Systems Interconnection Basic Reference Model]], the [[Open Geospatial Consortium]] reference models, the [[Von Neumann architecture]] as a reference model for sequential computing, the [[Federal Enterprise Architecture]] reference models, and the [[Agent Systems Reference Model]].

* the [[Federal Enterprise Architecture]] reference models,

* the [[Open Geospatial Consortium]] reference models,

* the [[OSI model|Open Systems Interconnection Basic Reference Model]],

* the [[RM-ODP|Reference Model of Open Distributed Processing]], and

* the [[Von Neumann architecture]] as a reference model for sequential computing,

== See also==

Line 28 ⟶ 33:

== References ==

{{unreferenced}}

<div class="references-small">

<references/>

</div>

[[Category:Computer architecture]]

[[Category:Reference models| ]]

[[Category:Software engineering]]

[[Category:Systems engineering]]

[[de:Referenzmodell]]