Difference between revisions of "Stakeholder (glossary)"
(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> | + | ''<blockquote>(1) Party having a right, share or claim in a system or in its possession of characteristics that meets that party's needs and expectations. (ISO/IEC 2008) </blockquote>'' |
| + | |||
| + | ''<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>'' | ||
| + | |||
| + | ''<blockquote>(3) An individual, team, or organization (or classes thereof) with interests in, or concerns relative to, a system. (ISO/IEC 2007)</blockquote>'' | ||
====Source==== | ====Source==== | ||
| − | + | (1) ISO/IEC. 2008. ''Systems and Software Engineering - System Life Cycle Processes''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electronical Commission (IEC), ISO/IEC 15288:2008 (E). | |
| + | |||
| + | (2) ISO/IEC. June 2010. ''Software and Systems Engineering -- Life Cycle Processes -- Requirements Engineering''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electronical 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 Electronical Commission (IEC), ISO/IEC 26702:2007. | ||
===Discussion=== | ===Discussion=== | ||
Revision as of 16:07, 18 May 2011
(1) Party having a right, share or claim in a system or in its possession of characteristics that meets that party's needs and expectations. (ISO/IEC 2008)
(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)
Source
(1) ISO/IEC. 2008. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electronical Commission (IEC), ISO/IEC 15288:2008 (E).
(2) ISO/IEC. June 2010. Software and Systems Engineering -- Life Cycle Processes -- Requirements Engineering. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electronical 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 Electronical Commission (IEC), ISO/IEC 26702:2007.
Discussion
Discussion as to why this is the "consensus" definition for the SEBoK.