Difference between revisions of "Engineering the Enterprise as a System"

From SEBoK
Jump to navigation Jump to search
m (Text replacement - "<center>'''SEBoK v. 2.4, released 19 May 2021'''</center>" to "<center>'''SEBoK v. 2.5, released 15 October 2021'''</center>")
(17 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<blockquote>Rouse, W. B. 2009. "Engineering the enterprise as a system". In ''Handbook of Systems Engineering and Management''., eds. A. P. Sage, W. B. Rouse. 2nd ed. New York, NY: Wiley and Sons, Inc.</blockquote>
+
<blockquote>Rouse, W.B. 2009. "Engineering the Enterprise as a System," in ''Handbook of Systems Engineering and Management'', 2nd ed., edited by A.P. Sage and W.B. Rouse. New York, NY, USA: Wiley and Sons, Inc.</blockquote>
  
 +
==Usage==
 +
*[[Enterprise Systems Engineering]]
 +
**[[Enterprise Systems Engineering Background]]
 +
**[[The Enterprise as a System]]
 +
**[[Enterprise Capability Management]]
  
 
==Annotation==
 
==Annotation==
A primary reference has been identified as the author team as a "key" reference, which is critically important to understanding a given topic. Each article will define a set of no more than 5-10 primary references. The general concept is that if a SEBoK user were to read the article on a topic and the Primary References, he or she would have a firm grasp on the principle concepts related to that article.
+
This is a chapter in the essential handbook on SE by Sage and Rouse. It describes how the enterprise can be treated as a system, and as such how SE can contribute to the more efficient and effective running of the enterprise. An enterprise must change to survive. Determining how and when these changes should come about is rather difficult since the enterprise is a continually evolving entity and there is never a clear and complete view of the enterprise as it exists at any moment in time.  
  
'''All primary reference pages will follow these guidelines:'''
+
Changing something in a purposeful way when that thing is changing continually is the key challenge. This chapter describes how this challenge can be addressed.
*Article title is the title of reference. This may be the title of the book, article, etc.
 
*First item listed will be the complete bibliographic reference.  Please see [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for descriptions and examples of complete references.
 
*All primary reference articles will contain a 1-2 paragraph annotation with a description and explanation of value for the related topic(s).
 
  
'''Authors submitting primary references are responsible for providing the bibliographic entry and annotation.'''  If multiple authors use the same primary reference, ''each'' author must explain the value proposition to a user for that resource in terms of his/her own topics.  In this instance, there will be a heading for each article. 
+
<center>'''SEBoK v. 2.5, released 15 October 2021'''</center>
 
 
EXAMPLE:  If this is a primary reference for three articles, the below will be:
 
 
 
===Article 1===
 
Annotation for Article 1.
 
 
 
===Article 2===
 
Annotation for Article 2.
 
 
 
===Article 3===
 
Annotation for Article 3.
 
  
 
[[Category:Primary Reference]]
 
[[Category:Primary Reference]]

Revision as of 08:01, 11 October 2021

Rouse, W.B. 2009. "Engineering the Enterprise as a System," in Handbook of Systems Engineering and Management, 2nd ed., edited by A.P. Sage and W.B. Rouse. New York, NY, USA: Wiley and Sons, Inc.

Usage

Annotation

This is a chapter in the essential handbook on SE by Sage and Rouse. It describes how the enterprise can be treated as a system, and as such how SE can contribute to the more efficient and effective running of the enterprise. An enterprise must change to survive. Determining how and when these changes should come about is rather difficult since the enterprise is a continually evolving entity and there is never a clear and complete view of the enterprise as it exists at any moment in time.

Changing something in a purposeful way when that thing is changing continually is the key challenge. This chapter describes how this challenge can be addressed.

SEBoK v. 2.5, released 15 October 2021