“Model Driven Architecture is a style of enterprise application development and integration, based on using automated tools to build system independent models and transform them into efficient implementations.”

— Grady Booch

Attributed to Grady Booch in: Tarek M. Sobh (2008) Advances in Computer and Information Sciences and Engineering. p. 457

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 "Model Driven Architecture is a style of enterprise application development and integration, based on using automated to…" by Grady Booch?

Grady Booch 35

American software engineer 1955

Bernhard Rumpe (1967) German computer scientist

Source: Model-driven development of complex software: A research roadmap (2007), p. 37

“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

“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

“There are two fundamental ways of (re-)engineering information systems. The “formal driven” approach is based on the goal of developing and implementing a technical correct running system. The “content driven” approach is based on the goal of developing and implementing an organizational correct running system. By using reference models, content and technology can be combined in a new way”

August-Wilhelm Scheer (1941) German business theorist

Source: ARIS architecture and reference models for business process management (2000), p. 376.

“The creation and implementation of integrated information systems involves a variety of collaborators including people from specialist departments, informatics, external advisers and manufacturers. They need clear rules and limits within which they can process their individual sub-tasks, in order to ensure the logical consistency of the entire project. Therefore, an architecture needs to be established to determine the components that make up the information system and the methods to be used to describe it. The ARIS architecture developed in this book is described in concrete terms as an information model within the entity-relationship approach. This information model provides the basis for the systematic and rational application of methods in the development of information systems. It also serves as the basis for a repository in which the enterprise's application - specific data, organization and function models can be stored. The ARIS architecture constitutes a framework in which integrated applications systems can be developed, optimized and converted into EDP - technical implementations. At the same time, it demonstrates how business economics can examine and analyze information systems in order to translate their contents into EDP-suitable form.”

August-Wilhelm Scheer (1941) German business theorist

August-Wilhelm Scheer, I. Cameron (1992) Architecture of integrated information systems: foundations of enterprise modelling. Abstract.

“CIMOSA provides a Reference Architecture (known as the CIMOSA cube) from which particular enterprise architectures can be derived. This Reference Architecture and the associated enterprise modelling framework are based on a set of modelling constructs, or generic building blocks, which altogether form the CIMOSA modelling languages.”

Peter Bernus (1949) Hungarian-Australian computer scientist

Peter Bernus, Kai Mertins, Günter Schmidt (1998) Handbook on Architectures of Information Systems. p. 244

“The development of the Model Driven Architecture (MDA) standards by the Object Management Group”

Grady Booch (1955) American software engineer

OMG
The Limits of Software

“There is a paradigm shift towards a distributed and integrated enterprise. Currently, computer systems that support enterprise functions were created independently. This hampers enterprise integration Therefore, there is a need for a computer based data model which provides a shared and well deﬁned terminology of an enterprise, and has the capability to deductively answer common sense questions.
This paper discusses how TOVE tackles these needs by deﬁning a framework for modeling generic level representations such as activities, time, and resources. Since there has never been a well-deﬁned set of criteria to evaluate such models, this paper also introduces a set of evaluation criteria which may be used to evaluate modelling efforts.”

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

Mark S. Fox, John F. Chionglo, and Fadi G. Fadel (1993) " A common-sense model of the enterprise http://windsor.mie.utoronto.ca/enterprise-modelling/papers/fox-ierc93.pdf." Proceedings of the 2nd Industrial Engineering Research Conference. Vol. 1. 1993.

“Enterprise architecture is the organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of a company's operation model… The key to effective enterprise architecture is to identify the processes, data, technology, and customer interfaces that take the operating model from vision to reality.”

Jeanne W. Ross (1958) American computer scientist

Source: Enterprise architecture as strategy, 2006, p. 47

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

“Model Driven Architecture is a style of enterprise application development and integration, based on using automated tools to build system independent models and transform them into efficient implementations.”

Help us to complete the source, original and additional information

Grady Booch 35

Related quotes

Related topics