Revision as of 11:44, 4 March 2012 edit Mdd (talk \| contribs) Autopatrolled, Extended confirmed users 54,583 edits (Again) Removed article which hardly seems to be related with this matter. See also http://www.tandfonline.com/doi/abs/10.1080/101967800750050371 ← Previous edit		Revision as of 18:04, 20 March 2012 edit undo Nickmalik (talk \| contribs) Extended confirmed users 688 edits Rewrote the definition using Richard Veryard's suggestion from the Talk page...a better distillation of the idea than prior edit Next edit →
Line 1: A '''reference model''' in [[systems engineering\|systems]], [[enterprise engineering\|enterprise]], and [[software engineering]] is ~~usually~~an aabstract ~~diagram~~framework ~~that~~or ~~depicts~~___domain-specific aontology ~~complete set~~consisting of ~~some~~an ~~kind~~interlinked ~~and illustrates how the elements~~set of ~~the~~clearly ~~set~~defined ~~relate~~concepts toproduced ~~one~~by ~~another.~~an expert ~~This~~or ~~kind~~body of ~~diagram~~experts ~~may~~in ~~illustrate~~order ~~subsets~~to ~~contained~~encourage ~~within~~clear ~~the set~~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 ~~diagram~~frame of reference can then be used asto acommunicate ~~reference~~ideas ~~for~~clearly among members of the ~~various~~same ~~purposes~~community. == Overview ==

Reference model: Difference between revisions