“Constructs extraneous to the real world should be eliminated from the analysis model. They may be needed later during design, but not now. For example, CPU subroutine, process, algorithm, and interrupt are implementation constructs for most applications [and should be excluded from the analysis model]…”

— James Rumbaugh

Source: Object-oriented modeling and design (1990), p. 155; as cited in: Roger Chiang et al (2009, p. 165)

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 "Constructs extraneous to the real world should be eliminated from the analysis model. They may be needed later during d…" by James Rumbaugh?

James Rumbaugh 5

Computer scientist, software engineer 1947

Related quotes

“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

“The first consequence of the principle of bounded rationality is that the intended rationality of an actor requires him to construct a simplified model of the real situation in order to deal with it. He behaves rationally with respect to this model, and such behavior is not even approximately optimal with respect to the real world. To predict his behavior we must understand the way in which this simplified model is constructed, and its construction will certainly be related to his psychological properties as a perceiving, thinking, and learning animal.”

Herbert A. Simon (1916–2001) American political scientist, economist, sociologist, and psychologist

Source: 1940s-1950s, Models of Man, 1957, p. 198; Cited in P. Slovic (1972, p. 2).

“In object-oriented analysis, we seek to model the world by identifying the classes and objects that form the vocabulary of the problem domain, and in object-oriented design, we invent the abstractions and mechanisms that provide the behavior that this model requires.”

Grady Booch (1955) American software engineer

Source: Object-oriented design: With Applications, (1991), p. 141

“Clearly, programming courses should teach methods of design and construction, and the selected examples should be such that a gradual development can be nicely demonstrated.”

Niklaus Wirth (1934) Swiss computer scientist

Program Development by Stepwise Refinement (1971)

“What is it that breathes fire into the equations and makes a universe for them to describe? The usual approach of science of constructing a mathematical model cannot answer the questions of why there should be a universe for the model to describe.”

Stephen Hawking book A Brief History of Time

Source: A Brief History of Time (1988), Ch. 12
Context: Even if there is only one possible unified theory, it is just a set of rules and equations. What is it that breathes fire into the equations and makes a universe for them to describe? The usual approach of science of constructing a mathematical model cannot answer the questions of why there should be a universe for the model to describe. Why does the universe go to all the bother of existing?

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

“As a mathematical object, the constitution is maximally simple, consistent, necessarily incomplete, and interpretable as a model of natural law. Political authority is allocated solely to serve the constitution. There are no authorities which are not overseen, within nonlinear structures. Constitutional language is formally constructed to eliminate all ambiguity and to be processed algorithmically. Democratic elements, along with official discretion, and legal judgment, is incorporated reluctantly, minimized in principle, and gradually eliminated through incremental formal improvement. Argument defers to mathematical expertise. Politics is a disease that the constitution is designed to cure.”

Nick Land (1962) British philosopher

"A Republic, If You Can Keep It" https://web.archive.org/web/20140327090001/http://www.thatsmags.com/shanghai/articles/12321 (2013) (original emphasis)

“Models are used essentially for evaluation and prediction purposes as well as for the analysis and study of the different parts of the system so that the systems engineer or designer may arrive at sound engineering decisions regarding the system design.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), p. 113; As cited in: Alberto Ortiz (1992, p. 12-13)

“The Unified Modeling Language (UML) is a general-purpose visual modeling language that is used to specify, visualize, construct, and document the artifacts of a software system. It captures decisions and understanding about systems that must be constructed. It is used to understand, design, browse, conﬁgure, maintain, and control information about such systems. It is intended for use with all development methods, lifecycle stages, application domains, and media. The modeling language is intended to unify past experience about modeling techniques and to incorporate current software best practices into a standard approach. UML includes semantic concepts, notation, and guidelines. It has static, dynamic, environmental, and organizational parts. It is intended to be supported by interactive visual modeling tools that have code generators and report writers. The UML speciﬁcation does not deﬁne a standard process but is intended to be useful with an iterative development process. It is intended to support most existing object-oriented development processes.”

James Rumbaugh (1947) Computer scientist, software engineer

James Rumbaugh, Ivar Jacobson & Grady Booch (1998) The Unified Modeling Language Reference Manual. p. 1

“The Uniﬁed Modeling Language (UML) is a general-purpose visual modeling language that is used to specify, visualize, construct, and document the artifacts of a software system. It captures decisions and understanding about systems that must be constructed. It is used to understand, design, browse, conﬁgure, maintain, and control information about such systems. It is intended for use with all development methods, lifecycle stages, application domains, and media. The modeling language is intended to unify past experience about modeling techniques and to incorporate current software best practices into a standard approach. UML includes semantic concepts, notation, and guidelines. It has static, dynamic, environmental, and organizational parts. It is intended to be supported by interactive visual modeling tools that have code generators and report writers. The UML speciﬁcation does not deﬁne a standard process but is intended to be useful with an iterative development process. It is intended to support most existing object-oriented development processes.”

Grady Booch (1955) American software engineer

James Rumbaugh, Ivar Jacobson, & Booch (1999) The Unified Modeling Language Reference Manual. p. 1

Help us to complete the source, original and additional information

James Rumbaugh 5

Related quotes

Related topics