Reference model: Difference between revisions

Revision as of 12:21, 2 May 2013

Revision as of 12:30, 2 May 2013

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 not usefullimited if it makes assumptions about the technology or platforms in place in a particular computing environment. A reference model typically is aintended mechanismto forpromote understanding thea problemsclass facedof problems, not thespecific solutions involved,for andthose asproblems. As such, it must beaid independentthe process of theimagining selectedand evaluating a variety of potential solutions in order to provide value toassist 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 ==