Difference between revisions of "Model (glossary)"

From SEBoK
Jump to navigation Jump to search
(Created page with '''<blockquote>A comprehensive, integrated plan that identifies the acquisition approach and describes the business, technical, and support strategies that management will follow ...')
 
Line 1: Line 1:
''<blockquote>A comprehensive, integrated plan that identifies the acquisition approach and describes the business, technical, and support strategies that management will follow to manage program risks and meet program objectives. The Acquisition Strategy should define the relationship between the acquisition phases and work efforts, and key program events such as decision points, reviews, contract awards, test activities, production lot/delivery quantities, and operational deployment objectives. (DAU February 19, 2010)</blockquote>''
+
''<blockquote>(1) a representation of a real world process, device, or concept. (IEEE 1998a, Section 3.11)</blockquote>''
 +
 
 +
''<blockquote>(2) a representation of something that suppresses certain aspects of the modeled subject. (IEEE 1320.2-1998, 3.1.115)</blockquote>''
 +
 
 +
''<blockquote>(3) an interpretation of a theory for which all the axioms of the theory are true. (IEEE 1320.2-1998, 3.1.115)</blockquote>''
 +
 
 +
''<blockquote>(4) a related collection of instances of meta-objects, representing (describing or prescribing) an information system, or parts thereof, such as a software product. (ISO/IEC 15474-1:2002, 4.2) </blockquote>''
 +
 
 +
''<blockquote>(5) a semantically closed abstraction of a system or a complete description of a system from a particular perspective. (ISO/IEC 2009, 1) </blockquote>''
  
 
====Source====
 
====Source====
DAU. February 19, 2010. ''Defense Acquisition Guidebook (DAG)''. Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD).  
+
(1) IEEE. 1998. ''IEEE Guide for Developing System Requirements Specifications''. Washington, DC: Institute of Electrical and Electronics (IEEE), IEEE 1233-1998.
 +
 
 +
(2) IEEE. 1998. ''IEEE Guide for Developing System Requirements Specifications''. Washington, DC: Institute of Electrical and Electronics (IEEE), IEEE 1233-1998.
 +
 
 +
(3) IEEE. 1998. ''IEEE Guide for Developing System Requirements Specifications''. Washington, DC: Institute of Electrical and Electronics (IEEE), IEEE 1233-1998.
 +
 
 +
(4)
 +
 
 +
(5) IEEE. 1998. ''IEEE Guide for Developing System Requirements Specifications''. Washington, DC: Institute of Electrical and Electronics (IEEE), IEEE 1233-1998.  
  
 
===Discussion===
 
===Discussion===

Revision as of 19:25, 17 May 2011

(1) a representation of a real world process, device, or concept. (IEEE 1998a, Section 3.11)

(2) a representation of something that suppresses certain aspects of the modeled subject. (IEEE 1320.2-1998, 3.1.115)

(3) an interpretation of a theory for which all the axioms of the theory are true. (IEEE 1320.2-1998, 3.1.115)

(4) a related collection of instances of meta-objects, representing (describing or prescribing) an information system, or parts thereof, such as a software product. (ISO/IEC 15474-1:2002, 4.2)

(5) a semantically closed abstraction of a system or a complete description of a system from a particular perspective. (ISO/IEC 2009, 1)

Source

(1) IEEE. 1998. IEEE Guide for Developing System Requirements Specifications. Washington, DC: Institute of Electrical and Electronics (IEEE), IEEE 1233-1998.

(2) IEEE. 1998. IEEE Guide for Developing System Requirements Specifications. Washington, DC: Institute of Electrical and Electronics (IEEE), IEEE 1233-1998.

(3) IEEE. 1998. IEEE Guide for Developing System Requirements Specifications. Washington, DC: Institute of Electrical and Electronics (IEEE), IEEE 1233-1998.

(4)

(5) IEEE. 1998. IEEE Guide for Developing System Requirements Specifications. Washington, DC: Institute of Electrical and Electronics (IEEE), IEEE 1233-1998.

Discussion

Discussion as to why this is the "consensus" definition for the SEBoK.