Difference between revisions of "Product (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 ...')
 
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023")
 
(38 intermediate revisions by 7 users not shown)
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 system considered from the point of view of a physical “system end product” (ANSI/EIA 2003) made of system elements that may include hardware, software, infrastructure and support services. The people and organizational aspects of the “whole system” of which the “product system” forms a part have to be considered in the design, but are provided by another organization. ''(INCOSE UK Chapter 2010)</blockquote>
  
====Source====
+
<blockquote>(2) ''An artifact that is produced, is quantifiable, and can be either an end item in itself or a component item.''  (PMI 2008)</blockquote>
DAU. February 19, 2010. ''Defense Acquisition Guidebook (DAG)''. Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD).  
+
 
 +
===Source===
 +
(1) INCOSE UK Chapter. 2010. ''Applying Systems Engineering to In-Service Systems: Supplementary Guidance to the INCOSE Systems Engineering Handbook''. Version 3.2, issue 1.0. Foresgate, UK: International Council on Systems Engineering (INCOSE) UK Chapter: 10, 13, 23.
 +
 
 +
(2) PMI. 2008. ''A Guide to the Project Management Body of Knowledge (PMBOK® Guide)'', 4th ed. Newtown Square, PA, USA: Project Management Institute (PMI).
  
 
===Discussion===
 
===Discussion===
Discussion as to why this is the "consensus" definition for the SEBoK.
+
This definition is a systems engineering definition, which is consistent with the concept of a system-of-interest (SoI) focused on the product system to be delivered to an acquirer who will use it to help deliver user outcomes.
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
 +
 +
<center>'''SEBoK v. 2.9, released 20 November 2023'''</center>

Latest revision as of 22:23, 18 November 2023

(1) A system considered from the point of view of a physical “system end product” (ANSI/EIA 2003) made of system elements that may include hardware, software, infrastructure and support services. The people and organizational aspects of the “whole system” of which the “product system” forms a part have to be considered in the design, but are provided by another organization. (INCOSE UK Chapter 2010)

(2) An artifact that is produced, is quantifiable, and can be either an end item in itself or a component item. (PMI 2008)

Source

(1) INCOSE UK Chapter. 2010. Applying Systems Engineering to In-Service Systems: Supplementary Guidance to the INCOSE Systems Engineering Handbook. Version 3.2, issue 1.0. Foresgate, UK: International Council on Systems Engineering (INCOSE) UK Chapter: 10, 13, 23.

(2) PMI. 2008. A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 4th ed. Newtown Square, PA, USA: Project Management Institute (PMI).

Discussion

This definition is a systems engineering definition, which is consistent with the concept of a system-of-interest (SoI) focused on the product system to be delivered to an acquirer who will use it to help deliver user outcomes.

SEBoK v. 2.9, released 20 November 2023