Difference between revisions of "Stakeholder (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 - "<center>'''SEBoK v. 2.6, released 20 May 2022'''</center>" to "<center>'''SEBoK v. 2.7, released 31 October 2022'''</center>")
(28 intermediate revisions by 8 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) ''Individual or organization having a right, share, claim, or interest in a system or in its possession of''
 +
characteristics that meet their needs and expectations'' (ISO/IEC/IEEE 2015) ''</blockquote>
  
====Source====
+
<blockquote>(2) ''Individual or organization having a right, share, claim, or interest in a system or in its possession of characteristics that meet their needs and expectations;  N.B. Stakeholders include, but are not limited to end users, end user organizations, supporters, developers, producers, trainers, maintainers, disposers, acquirers, customers, operators, supplier organizations and regulatory bodies.''  (ISO/IEC June 2010) </blockquote>
DAU. February 19, 2010. ''Defense Acquisition Guidebook (DAG)''. Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD).  
+
 
 +
<blockquote>(3) ''An individual, team, or organization (or classes thereof) with interests in, or concerns relative to, a system.''  (ISO/IEC 2007)</blockquote>
 +
 
 +
<blockquote>(4) ''A stakeholder in an organisation is (by definition) any group or individual who can affect or is affected by the achievement of the organisation's objectives.'' (Freeman 1984)</blockquote>
 +
 
 +
 
 +
===Source===
 +
(1) ISO/IEC/IEEE. 2015. ''Systems and Software Engineering - System Life Cycle Processes''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission/Institute of Electrical and Electronics Engineers (IEC), ISO/IEC/IEEE 15288:2015 (E).
 +
 
 +
(2) ISO/IEC. June 2010. ''Software and Systems Engineering -- Life Cycle Processes -- Requirements Engineering''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), ISO/IEC CD 29148.
 +
 
 +
(3) ISO/IEC. 2007. ''Systems Engineering--Application and Management of the Systems Engineering Process''. Geneva, Switzerland: International Organization for Standards (ISO)/International Electrotechnical Commission (IEC), ISO/IEC 26702:2007.
 +
 
 +
(4) Freeman, R.E. 1984. ''Strategic Management: A stakeholder approach'', Boston, Pitman
  
 
===Discussion===
 
===Discussion===
Discussion as to why this is the "consensus" definition for the SEBoK.
+
None.
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
 +
 +
<center>'''SEBoK v. 2.7, released 31 October 2022'''</center>

Revision as of 08:32, 10 October 2022

(1) Individual or organization having a right, share, claim, or interest in a system or in its possession of characteristics that meet their needs and expectations (ISO/IEC/IEEE 2015)

(2) Individual or organization having a right, share, claim, or interest in a system or in its possession of characteristics that meet their needs and expectations; N.B. Stakeholders include, but are not limited to end users, end user organizations, supporters, developers, producers, trainers, maintainers, disposers, acquirers, customers, operators, supplier organizations and regulatory bodies. (ISO/IEC June 2010)

(3) An individual, team, or organization (or classes thereof) with interests in, or concerns relative to, a system. (ISO/IEC 2007)

(4) A stakeholder in an organisation is (by definition) any group or individual who can affect or is affected by the achievement of the organisation's objectives. (Freeman 1984)


Source

(1) ISO/IEC/IEEE. 2015. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission/Institute of Electrical and Electronics Engineers (IEC), ISO/IEC/IEEE 15288:2015 (E).

(2) ISO/IEC. June 2010. Software and Systems Engineering -- Life Cycle Processes -- Requirements Engineering. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), ISO/IEC CD 29148.

(3) ISO/IEC. 2007. Systems Engineering--Application and Management of the Systems Engineering Process. Geneva, Switzerland: International Organization for Standards (ISO)/International Electrotechnical Commission (IEC), ISO/IEC 26702:2007.

(4) Freeman, R.E. 1984. Strategic Management: A stakeholder approach, Boston, Pitman

Discussion

None.

SEBoK v. 2.7, released 31 October 2022