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

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

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 "Information Engineering is the application of an interlocking set of formal techniques for the planning, analysis, desi…" by James Martin (author)?
James Martin (author) photo
James Martin (author) 9
British information technology consultant and writer 1933–2013

Related quotes

“Business System Planning (BSP) and Business Information Control Study (BICS) are two information system planning study methodologies that specifically employ enterprise analysis techniques in the course of their analysis. Underlying the BSP and BICS analysis are the data management problems that result from systems design approaches that optimize the management of technology at the expense of managing the data.”

John Zachman (1934) American computer scientist

Source: Business Systems Planning and Business Information Control Study: A comparison, 1982, p. 31

James Martin (author) photo

“Information engineering has been defined with the reference to automated techniques as follows: An interlocking set of automated techniques in which enterprise models, data models and process models are built up in a comprehensive knowledge-base and are used to create and maintain data-processing systems.”

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

Source: Information Engineering (1989), p. viii

“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

“In enterprise modelling, we want to define the actions performed within an enterprise, and define constraints for plans and schedules which are constructed to satisfy the goals of the enterprise. This leads to the following set of informal competency questions:”

Mark S. Fox (1952) Canadian computer scientist and Professor of Industrial Engineering

Temporal projection - Given a set of actions that occur at different points in the future, what are the properties of resources and activities at arbitrary points in time?
Planning and scheduling - what sequence of activities must be completed to achieve some goal? At what times must these activities be initiated and terminated?
Execution monitoring and external events - What are the effects of the occurrence of external and unexpected events (such as machine breakdown or the unavailability of resources) on a plan or schedule?
Time-based competition - we want to design an enterprise that minimizes the cycle time for a product. This is essentially the task of finding a minimum duration plan that minimizes action occurrences and maximizes concurrency of activities.
Source: Methodology for the Design and Evaluation of Ontologies (1995), p. 3-4

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

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

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

“Business System Planning (BSP) and Business Information Control Study (BICS) are representative of enterprise analysis tools that are growing in importance and are likely to become mandatory for ant business that continues to grow and evolve.”

John Zachman (1934) American computer scientist

Source: Business Systems Planning and Business Information Control Study: A comparison, 1982, p. 31

“In the early ‘80’s, there was little interest in the idea of Enterprise Reengineering or and the use of formalisms and models was generally limited to some aspects of application development within the Information Systems community. The subject of "architecture" was acknowledged at that time, however, there was little definition to support the concept. This lack of definition precipitated the initial investigation that ultimately resulted in the "Framework for Information Systems Architecture." Although from the outset, it was clear that it should have been referred to as a "Framework for Enterprise Architecture," that enlarged perspective could only now begin to be generally understood as a result of the relatively recent and increased, worldwide focus on Enterprise "engineering."”

John Zachman (1934) American computer scientist

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

Related topics