“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)

Book summary
The great transition (1995)

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 not a single methodology, but a sophisticated synthesis of the most important and successful …" by James Martin (author)?
James Martin (author) photo
James Martin (author) 9
British information technology consultant and writer 1933–2013

Related quotes

“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 (1947) American engineer

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

“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 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

“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

“The Generic Enterprise Reference Architecture and Methodology is about those methods, models and tools which are needed to build the integrated enterprise. The architecture is generic because it applies to most, potentially all types of enterprise. The coverage of the framework spans Products, Enterprises, Enterprise Integration and Strategic Enterprise Management, with the emphasis being on the middle two. The proposal for the architecture follows the architecture itself improving the quality of the presentation and of the outcome. De nitions of Generic Enterprise Reference Architecture, Enterprise Engineering/ Integration Methodology, Enterprise Modelling Languages, Enterprise Models, and Enterprise Modules are given. It is proposed how the above could be developed on the basis of previously analysed architectures (and other results too), such as the Purdue Enterprise Reference Architecture, the GRAI Integrated Methodology, CIM-OSA, and TOVIE.”

Peter Bernus (1949) Hungarian-Australian computer scientist

Peter Bernus and Laszlo Nemes (1996) "A framework to define a generic enterprise reference architecture and methodology." Computer Integrated Manufacturing Systems Vol 9 (3) p. 179

James Martin (author) photo

“Enterprise engineering is an integrated set of disciplines for building an enterprise, its processes, and systems.”

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

Source: The great transition (1995), p. 58; As cited in: Jan Hoogervorst (2009, p. 9)

“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.

“An enterprise architecture can be thought of as a "blueprint" or "picture" which assists in the design of an enterprise. The enterprise architecture must define three things. First, what are the activities that an enterprise performs? Second, how should these activities be performed? And finally, how should the enterprise be constructed? Consequently, the architecture being developed will identify the essential processes performed by a virtual company, how the virtual company and the agile enterprises involved in the virtual company will perform these processes, and include a methodology for the rapid reconfiguration of the virtual enterprise.”

Donald H. Liles (1947) American engineer

William Barnett, Adrien Presley, Mary Johnson, and Donald H. Liles (1994) "An architecture for the virtual enterprise." Systems, Man, and Cybernetics, 1994.' Humans, Information and Technology'., 1994 IEEE International Conference on. Vol. 1. IEEE, 1994

“The older disciplines of Architecture and Manufacturing have accumulated considerable bodies of product knowledge through disciplined management of the "product definition" design artifacts. This has enabled enormous increases in product sophistication and the ability to manage high rates of product change over time. Similarly, disciplined production and management of "Enterprise definition" (i. e. the set of models identified in the Framework for Enterprise Architecture) should provide for an accumulation of a body of Enterprise knowledge to facilitate enormous increases in Enterprise sophistication and accommodation of high rates of Enterprise change over time.”

John Zachman (1934) American computer scientist

Source: Concepts of the Framework for Enterprise Architecture, 1993, p. 3

“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.

Related topics