Reference model: Difference between revisions

Revision as of 11:31, 13 April 2018

Revision as of 23:13, 2 November 2019

Line 1:

A '''reference model''' in—in [[systems engineering|systems]], [[enterprise engineering|enterprise]], and [[software engineering]] is—is an abstract framework or ___domain-specific [[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.

Line 10:

* ''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 ==