Difference between revisions of "Enterprise Systems Engineering (ESE) (glossary)"

From SEBoK
Jump to navigation Jump to search
Line 9: Line 9:
 
(2) The body of knowledge for enterprise systems engineering is evolving under such titles as enterprise engineering, [[Business (glossary)]] engineering, and [[Enterprise Architecture (glossary)]]. Many systems and software engineering principles are applicable to enterprise engineering, but enterprise engineering’s unique [[Complexity (glossary)|complexities]] require additional principles. Enterprise engineering’s intent is to deliver a targeted level of enterprise performance in terms of shareholder [[Value (glossary)]] or [[Customer (glossary)]] satisfaction. Enterprise systems engineering methods include modeling; [[Simulation (glossary)]]; total [[Quality (glossary)]] management; change management; and bottleneck, [[Cost (glossary)]], workflow, and value-added analysis. (Joannou 2007)''
 
(2) The body of knowledge for enterprise systems engineering is evolving under such titles as enterprise engineering, [[Business (glossary)]] engineering, and [[Enterprise Architecture (glossary)]]. Many systems and software engineering principles are applicable to enterprise engineering, but enterprise engineering’s unique [[Complexity (glossary)|complexities]] require additional principles. Enterprise engineering’s intent is to deliver a targeted level of enterprise performance in terms of shareholder [[Value (glossary)]] or [[Customer (glossary)]] satisfaction. Enterprise systems engineering methods include modeling; [[Simulation (glossary)]]; total [[Quality (glossary)]] management; change management; and bottleneck, [[Cost (glossary)]], workflow, and value-added analysis. (Joannou 2007)''
  
(3) A useful distinction between [[Product System (glossary)]] design and enterprise system design is that “enterprise design does not occur at a single point in time like the [[Design (glossary)]] of most systems. Instead, enterprises evolve over time and are constantly changing, or are constantly being designed.” (Giachetti 2010)
+
(3) A useful distinction between [[Product System (glossary)]] design and enterprise system design is that “enterprise design does not occur at a single point in time like the design of most systems. Instead, enterprises evolve over time and are constantly changing, or are constantly being designed.” (Giachetti 2010)
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]

Revision as of 20:11, 13 September 2011

The application of systems engineering principles, concepts, and methods to the planning, design , improvement, and operation of an enterprise .

Source

This definition was developed for the SEBoK version 0.5. ‘’Note to reviewers’’: If you are aware of a more authoritative definition, please provide this information in your review.

Discussion

(1) To enable more efficient and effective enterprise transformation, the enterprise needs to be looked at “as a system ,” rather than as a collection of functions connected solely by information systems and shared facilities (Rouse 2009).

(2) The body of knowledge for enterprise systems engineering is evolving under such titles as enterprise engineering, business engineering, and enterprise architecture . Many systems and software engineering principles are applicable to enterprise engineering, but enterprise engineering’s unique complexities require additional principles. Enterprise engineering’s intent is to deliver a targeted level of enterprise performance in terms of shareholder value or customer satisfaction. Enterprise systems engineering methods include modeling; simulation ; total quality management; change management; and bottleneck, cost , workflow, and value-added analysis. (Joannou 2007)

(3) A useful distinction between product system design and enterprise system design is that “enterprise design does not occur at a single point in time like the design of most systems. Instead, enterprises evolve over time and are constantly changing, or are constantly being designed.” (Giachetti 2010)