“Enterprise Engineering is defined as that body of knowledge, principles, and practices having to do with the analysis, design, implementation and operation of an enterprise. In a continually changing and unpredictable competitive environment, the Enterprise Engineer addresses a fundamental question: “how to design and improve all elements associated with the total enterprise through the use of engineering and analysis methods and tools to more effectively achieve its goals and objectives”…”

—  Donald H. Liles

Source: The Enterprise Engineering Discipline (1996), p. 1

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Enterprise Engineering is defined as that body of knowledge, principles, and practices having to do with the analysis, …" by Donald H. Liles?
Donald H. Liles photo
Donald H. Liles 7
American engineer 1947

Related quotes

“Enterprise Engineering is the collection of those tools and methods which one can use to design and continually maintain an enterprise.”

Peter Bernus (1949) Hungarian-Australian computer scientist

Peter Bernus, ‎Laszlo Nemes, ‎Günter Schmidt (eds.) Handbook on Enterprise Architecture. 2003. p. 22; Cited in: Dennis F.X. Mathaisel (2007) Sustaining the Military Enterprise. p. 69

“Enterprise engineering is an emerging discipline that studies enterprises from an engineering perspective. The first paradigm of this discipline is that enterprises are purposefully designed and implemented systems. Consequently, they can be re-designed and re-implemented if there is a need for change. The second paradigm of enterprise engineering is that enterprises are social systems. This means that the system elements are social individuals, and that the essence of an enterprise's operation lies in the entering into and complying with commitments between these social individuals.”

Erik Proper (1967) Dutch computer scientist

Preface.
Advances in Enterprise Engineering II (2009)

“Enterprise architecture (EA) promotes the belief that an enterprise, as a complex system, can be designed or improved in an orderly fashion achieving better overall results than ad-hoc organisation and design. EA is a co-operative effort of designers, analysts and managers and uses enterprise models in the process… enterprise models carry meaning. This resulted in requirements for the enterprise engineering process, which—if not met—can limit the viability of the process. The analysis of the same factors resulted in requirements for improved Enterprise Modelling Tools.”

Peter Bernus (1949) Hungarian-Australian computer scientist

Peter Bernus (2003) "Enterprise models for enterprise architecture and ISO9000: 2000." Annual Reviews in Control 27.2 : 211-220.

James Martin (author) photo

“Enterprise Engineering is not a single methodology, but a sophisticated synthesis of the most important and successful of today's change methods. "Enterprise Engineering" first explains in detail all the critical disciplines (including continuous improvement, radical reinvention of business processes, enterprise redesign, and strategic visioning). It then illustrates how to custom-design the right combination of these change methods for your organization's specific needs.”

James Martin (author) (1933–2013) British information technology consultant and writer

Book summary
The great transition (1995)

James Martin (author) photo

“Information Engineering is the application of an interlocking set of formal techniques for the planning, analysis, design, and construction of information systems on the enterprise wide basis or across a major sector of the enterprise.”

James Martin (author) (1933–2013) British information technology consultant and writer

Source: Information Engineering (1989), p. 1; cited in Karl E. Kurbel (2008) The making of information systems [electronic resource]. p. 176

“There are several world view assumptions present in enterprise engineering. The first assumption is that the enterprise can be viewed as a complex system. This is necessary because systems in organizations are systems of organized complexity. Complexity is the result of the multiplicity and intricacy of man’s interaction with other components of the system. Secondly, the enterprise is to be viewed as a system of processes. These processes are engineered both individually and holistically. The final assumption is the use of engineering rigor in transforming the enterprise. The enterprise engineering paradigm views the enterprise as a complex system of processes that can be engineered to accomplish specific organizational objectives. In the Enterprise Engineering paradigm, the enterprise is viewed as a complex system of processes that can be engineered to accomplish specific organizational objectives.”

Donald H. Liles (1947) American engineer

Source: Enterprise modeling within an enterprise engineering framework (1996), p. 993

“Enterprise Engineering is based on the belief that an enterprise, as any other complex system can be designed or improved in an orderly fashion thus giving a better overall result than ad hoc organisation and design.”

Peter Bernus (1949) Hungarian-Australian computer scientist

Peter Bernus, Laszlo Nemes, and R. Morris (1994) " Possibilities and limitations of reusing enterprise models http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.50.1736&rep=rep1&type=pdf." IFAC Workshop, Proceedings from Intelligent Manufacturing Systems.

“Enterprise engineering is rooted in both the organizational sciences and the information system sciences. In our current understanding, three concepts are paramount to the theoretical and practical pursuit of enterprise engineering: enterprise ontology, enterprise architecture, and enterprise governance.”

Erik Proper (1967) Dutch computer scientist

Preface
Advances in Enterprise Engineering II (2009)

“Although many popular information systems planning methodologies, design approaches, and various tools and techniques do not preclude or are not inconsistent with enterprise-level analysis, few of them explicitly address or attempt to define enterprise architectures. Some examples of such popular offerings include”

John Zachman (1934) American computer scientist

Planning Methodologies: Stage Assessment, Critical Success Factors, Strategy Set Transformation, etc.
Design Approaches: Structured Analysis, Entity-Relationship Approaches, etc.
Tools and Techniques"Problem Statement Language/Problem Statement Analyzer (PSL/PSA), Prototype Development Methodology, Structured Analyses and Design Techniques, etc.
From an historical perspective, BSP and BICS likely will be looked back on as primitive attempts to take an explicit, enterprise-level architectural approach to information systems.
Source: Business Systems Planning and Business Information Control Study: A comparison, 1982, p. 32

Qian Xuesen photo

“An engineering science aims to organize the design principles used in engineering practice into a discipline and thus to exhibit the similarities between different areas of engineering practice and to emphasize the power of fundamental concepts. In short, an engineering science is predominated by theoretical analysis and very often uses the tool of advanced mathematics.”

Qian Xuesen (1911–2009) Chinese rocket scientist

Source: Engineering cybernetics, (1954), p. vii

Related topics