Difference between revisions of "Enterprise (glossary)"

From SEBoK
Jump to navigation Jump to search
m (moved Enterprise to enterprise : Changed to align with new glossary article formatting.)
(20 intermediate revisions by the same user not shown)
Line 1: Line 1:
''<blockquote>(1) one or more organizations sharing a definite mission, goals, and objectives to offer an output such as a product or service. (ISO 2000)</blockquote>
+
<blockquote>(1) ''one or more [[Organization (glossary)|organizations]] sharing a definite [[Mission|mission]], goals, and objectives to offer an [[Output (glossary)|output]] such as a [[Product (glossary)|product]] or [[Service (glossary)|service]].'' (ISO 15704 2000) </blockquote>
  
<blockquote>(2) An organization (or cross organizational entity) supporting a defined business scope and mission that includes interdependent resources (people, organizations and technologies) that must coordinate their functions and share information in support of a common mission (or set of related missions). (CIO Council 1999)</blockquote>
+
<blockquote>(2) ''An organization (or cross organizational entity) supporting a defined [[Business (glossary)|business]] scope and mission that includes interdependent resources (people, organizations and technologies) that must coordinate their [[Function (glossary)|functions]] and share information in support of a common mission (or set of related missions).'' (CIO Council 1999)</blockquote>
  
<blockquote>(3) the term enterprise can be defined in one of two ways. The first is when the entity being considered is tightly bounded and directed by a single executive function. The second is when organizational boundaries are less well defined and where there may be multiple owners in terms of direction of the resources being employed. The common factor is that both entities exist to achieve specified outcomes. (MOD 2004) </blockquote>''
+
<blockquote>(3) ''the term enterprise can be defined in one of two ways. The first is when the entity being considered is tightly bounded and directed by a single executive function. The second is when organizational [[Boundary (glossary)|boundaries]] are less well defined and where there may be multiple owners in terms of direction of the resources being employed. The common factor is that both entities exist to achieve specified outcomes.'' (MOD 2004) </blockquote>
  
====Source====
+
===Source===
(1) ISO. 2000. ''Industrial Automation Systems -- Requirements for Enterprise-Reference Architectures and Methodologies''. Geneva, Switzerland: International Organization for Standardization (ISO), ISO 15704:2000.  
+
(1) ISO 15704. 2000. ''Industrial Automation Systems -- Requirements for Enterprise-Reference Architectures and Methodologies''. Geneva, Switzerland: International Organization for Standardization (ISO), ISO 15704:2000.  
  
 
(2) CIO Council. 1999. ''Federal Enterprise Architecture Framework (FEAF)''. Washington, DC: Chief Information Officer (CIO) Council.  
 
(2) CIO Council. 1999. ''Federal Enterprise Architecture Framework (FEAF)''. Washington, DC: Chief Information Officer (CIO) Council.  
Line 13: Line 13:
  
 
===Discussion===
 
===Discussion===
Discussion as to why this is the "consensus" definition for the SEBoK.
+
Definition (1) above  is the preferred BKCASE definition. The focus of this definition is on purpose rather than structure, and the enterprise may be either enduring or transient, and either formally or informally constituted and governed. The simplest case of enterprise could be an individual and the largest a national or international undertaking.
 +
 
 +
Definition (2) is compatible with definition (1) and provides additional insight relevant to the practice of "enterprise architecting", which is closely related to [[Enterprise Systems Engineering]].
 +
 
 +
Definition (3) highlights the fact that the word "enterprise" is sometimes used synonymously with "business". However in BKCASE we use [[Business (glossary)]] to refer to a form of organization, while an [[Enterprise (glossary)]] often involves collaboration across organizational boundaries. Furthermore, we also use [[Project (glossary)]] and [[Team (glossary)]] to refer to two other forms of an organization. An enterprise ''could'' be at the business level, but some enterprises are at the project or team level. Therefore, as noted above, it is better to focus on the purpose rather than structure of an "enterprise" to facilitate the more proper use and better understanding of that term.
 +
 
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]

Revision as of 19:12, 13 September 2011

(1) one or more organizations sharing a definite mission, goals, and objectives to offer an output such as a product or service. (ISO 15704 2000)

(2) An organization (or cross organizational entity) supporting a defined business scope and mission that includes interdependent resources (people, organizations and technologies) that must coordinate their functions and share information in support of a common mission (or set of related missions). (CIO Council 1999)

(3) the term enterprise can be defined in one of two ways. The first is when the entity being considered is tightly bounded and directed by a single executive function. The second is when organizational boundaries are less well defined and where there may be multiple owners in terms of direction of the resources being employed. The common factor is that both entities exist to achieve specified outcomes. (MOD 2004)

Source

(1) ISO 15704. 2000. Industrial Automation Systems -- Requirements for Enterprise-Reference Architectures and Methodologies. Geneva, Switzerland: International Organization for Standardization (ISO), ISO 15704:2000.

(2) CIO Council. 1999. Federal Enterprise Architecture Framework (FEAF). Washington, DC: Chief Information Officer (CIO) Council.

(3) MOD. 2004. Ministry of Defence Architecture Framework (MODAF), version 2. UK: U.K. Ministry of Defence.

Discussion

Definition (1) above is the preferred BKCASE definition. The focus of this definition is on purpose rather than structure, and the enterprise may be either enduring or transient, and either formally or informally constituted and governed. The simplest case of enterprise could be an individual and the largest a national or international undertaking.

Definition (2) is compatible with definition (1) and provides additional insight relevant to the practice of "enterprise architecting", which is closely related to Enterprise Systems Engineering.

Definition (3) highlights the fact that the word "enterprise" is sometimes used synonymously with "business". However in BKCASE we use business to refer to a form of organization, while an Enterprise (glossary) often involves collaboration across organizational boundaries. Furthermore, we also use project and team to refer to two other forms of an organization. An enterprise could be at the business level, but some enterprises are at the project or team level. Therefore, as noted above, it is better to focus on the purpose rather than structure of an "enterprise" to facilitate the more proper use and better understanding of that term.