A '''reference model''' is a model of models that makes model for modelin the minsitry of models.in [[systems engineering|systems]], [[enterprise engineering|enterprise]], and [[software engineering]] 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.
== 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:
