Reference model: Difference between revisions

Revision as of 04:15, 27 June 2013

Latest revision as of 15:28, 27 August 2025

(36 intermediate revisions by 31 users not shown)

Line 1:

{{Short description|Abstract model used as reference}}

A '''reference model''' is a model of models that makes model for model in the minsitry of models.in—in [[systems engineering|systems]], [[enterprise engineering|enterprise]], and [[software engineering]] is—is an abstract framework or ___domain-specific [[ontology (information science)|ontology]] consisting of an interlinked set of clearly defined concepts produced by an expert or body of experts in order to encourage clear communication. A reference model can represent the component parts of any consistent idea, from business functions to system components, as long as it represents a complete set. This frame of reference can then be used to communicate ideas clearly among members of the same community.

Reference models are often illustrated as a set of concepts with some indication of the relationships between the concepts.

== Overview ==

Leyah Marshly says that accordingAccording to [[OASIS (organization)|OASIS]] (Organization for the Advancement of Structured Information Standards) a reference model is "an abstract framework for understanding significant relationships among the entities of some environment, and for the development of consistent standards or specifications supporting that environment. A reference model is based on a small number of unifying concepts and may be used as a basis for education and explaining standards to a non-specialist. A reference model is not directly tied to any standards, technologies or other concrete implementation details, but it does seek to provide a common semantics that can be used unambiguously across and between different implementations."<ref>{{cite web|title=OASIS SOA Reference Model|url=http://www.oasis-open.org/committees/soa-rm/faq.php|publisher=OASIS SOA Technical Committee|accessdate=13/13/2011}}</ref>

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

Line 10 ⟶ 11:

* ''Entities and relationships'': A reference model describes both types of entities (things that exist) and their relationships (how they connect, interact with one another, and exhibit joint properties). A list of entity types, by itself, doesn't provide enough information to serve as 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's usefulness is limited if it makes assumptions about the technology or platforms in place in a particular computing environment. A reference model typically is intended to promote understanding a class of problems, not specific solutions for those problems. As such, it must aidassist the practitioner by aiding the process of imagining and evaluating a variety of potential solutions in order to assist 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 ==

There are many uses for a reference model. One use is to create standards for both the objects that inhabit the model and their relationships to one another. By creating standards, the work of engineers and developers who need to create objects that behave according to the standard is made easier. Software can be written that meets a standard, and developers can copy that software to use it again, or build a [[software factory]] that generates that code. When done well, a standard can make use of [[design patterns]] that support key qualities of software, such as the ability to extend the software in an inexpensive way.

Another use of a reference model is to educate. Using a reference model, leaders in software development can help break down a large problem space into smaller problems that can be understood, tackled, and refined. Developers who are new to a particular set of problems can quickly learn what the different problems are, and can focus on the problems that they are being asked to solve, while trusting that other areas are well understood and rigorously constructed. The level of trust is important to allow software developers to efficiently focus on their work.

Line 30 ⟶ 31:

* [[Federal Enterprise Architecture Framework]] reference model of the [[Federal Enterprise Architecture|FEA]]

* HP Information Security Service Management (ISSM) - Reference Model (RM)

* IBM [[Information Framework]], a reference model for financial services.

* [[NIST Enterprise Architecture Model]] reference models from several Federal Enterprise Architectures

* [[OGC Reference Model]] (Open Geospatial Consortium),

* [[Open Geospatial Consortium]] reference models,

* [[OpenReference]], an [[Open standard|open]] reference model for business performance, processes and practices<ref>OpenReference Initiative: [http://ORwiki.org/Frameworks OpenReference frameworks], December 2016</ref>

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

* [[IEEE 802]] reference model

* [[Purdue Enterprise Reference Architecture]]

* [[Real-time Control System]] for real-time control problem domains

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

* [[TAFIM]] was the 1990 reference model of the earlier version of the [[DoDAF]], and

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

* [[Digital Library]] Reference Model<ref name="DLRM2011">L. Candela, G. Athanasopoulos, D. Castelli, K. El Raheb, P. Innocenti, Y. Ioannidis, A. Katifori, A. Nika, G. Vullo, S. Ross: ''The Digital Library Reference Model''. April 2011 ([http://bscw.research-infrastructures.eu/pub/bscw.cgi/d222816/D3.2b%20Digital%20Library%20Reference%20Model.pdf PDF])</ref><ref name="DLRM2008">L. Candela et al.: ''The DELOS Digital Library Reference Model - Foundations for Digital Libraries''. Version 0.98, February 2008 ([http://www.delos.info/files/pdf/ReferenceModel/DELOS_DLReferenceModel_0.98.pdf PDF] {{webarchive|url=https://web.archive.org/web/20090304002829/http://www.delos.info/files/pdf/ReferenceModel/DELOS_DLReferenceModel_0.98.pdf |date=2009-03-04 }})</ref>

* ENVRI (Environmental Research Infrastructures) Reference Model<ref>Y. Chen, P. Martin, H. Schentz, B. Magagna, Z. Zhao, A. Hardisty, A. Preece, M. Atkinson http://envri.eu/rm{{Dead link|date=August 2025 |bot=InternetArchiveBot |fix-attempted=yes }}</ref>

== See also==

{{commonscatcommons category|Reference models}}

* [[Business reference model]]

* [[Open System Environment Reference Model]]

Line 46 ⟶ 52:

== References ==

{{Reflist}}

<references />

[[Category:Computer architecture]]

[[Category:Reference models| ]]

[[Category:Software engineering terminology]]

[[Category:Systems engineering]]