Famous quotes

Quotes by famous people, credited to who said them. Your own quotes must not match any of these. More are added all the time. 1,158,808 quotes Who coined it · How we decide

English Italiano Polski עברית Français Português فارسی Español 中文 Русский Deutsch العربية हिन्दी 日本語 Ελληνικά Latina

Grady Booch

37 quotes

“Perhaps the greatest strength of an object-oriented approach to development is that it offers a mechanism that captures a model of the real world.”
Grady Booch (born 1955) first seen 1986 wikiquote, CC BY-SA 4.0 source
Recorded in: Grady Booch (1986) Software Engineering with Ada p. 220. cited in: David J. Gilmore et al. (1994) User-Centred Requirements for Software Engineering Environments. p. 108
“The entire history of software engineering is that of the rise in levels of abstraction.”
Grady Booch (born 1955) first seen 2003 wikiquote, CC BY-SA 4.0 source
Recorded in: Grady Booch in his talk "The Limits of Software."; Cited in: Gerry Boyd (2003) "Executable UML: Diagrams for the Future." published at devx.com, February 5, 2003.
“As a noun, design is the named (although sometimes unnamable) structure or behavior of a system whose presence resolves or contributes to the resolution of a force or forces on that system. A design thus represents one point in a potential decision space. A design may be singular (representing a leaf decision) or it may be collective (representing a set of other decisions).”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“The amateur software engineer is always in search of magic, some sensational method or tool whose application promises to render software development trivial. It is the mark of the professional software engineer to know that no such panacea exist.”
Grady Booch (born 1955) first seen 2007 wikiquote, CC BY-SA 4.0 source
Recorded in: Grady Booch, ‎Robert A. Maksimchuk, ‎Michael W. Engle (2007) Object-Oriented Analysis and Design with Applications Chapter 6.
“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 (born 1955) first seen 2008 wikiquote, CC BY-SA 4.0 source
Recorded in: Attributed to Grady Booch in: Tarek M. Sobh (2008) Advances in Computer and Information Sciences and Engineering. p. 457
“The function of good software is to make the complex appear to be simple.”
Grady Booch (born 1955) first seen 2010 wikiquote, CC BY-SA 4.0 source
Recorded in: Attributed to Booch in: Frank H. P. Fitzek et al. (2010) Qt for Symbian. p. xv
“In the early days of modern computing - the 40s, 50s and 60s - computing was a priesthood. Only a few were allowed to commune directly with the machine; all others would give their punched card offerings to the anointed, who would in turn genuflect before their card readers and perform their rituals amid the flashing of lights, the clicking of relays, and the whirring of fans and motors. If the offering was well-received, the anointed would call the communicants forward and in solemn silence hand them printed manuscripts, whose signs and symbols would be studied with fevered brow.”
Grady Booch (born 1955) first seen 2011 wikiquote, CC BY-SA 4.0 source
Recorded in: Grady Booch (2011) "The Computing Priesthood" on ibm.com/developerworks/community/blogs/gradybooch. November 14, 2011
“Structured design does not scale up well for extremely complex systems, and this method is largely inappropriate for use with object-based and object-oriented programming languages.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“Object-oriented programming is a method of implementation in which programs are organized as cooperative collections of objects, each of which represents an instance of some class, and whose classes are all members of a hierarchy of classes united via inheritance relationships.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“Object-oriented analysis is a method of analysis that examines requirements from the perspective of the classes and objects found in the vocabulary of the problem domain.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“Object-oriented design is a method of design encompassing the process of object-oriented decomposition and a notation for depicting both logical and physical as well as static and dynamic models of the system under design.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“The object-oriented paradigm is useful when building software systems where there is a hierarchy defined as a ranking or ordering of abstractions.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“Typically, a subclass augments or redefines the existing structure and behavior of its superclasses.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“As Cox points out, "Without inheritance, every class would be a free-standing unit, each developed from the ground up. Different classes would bear no relationship with one another, since the developer of each provides methods in whatever manner he chooses. Any consistency across classes is the result of discipline on the part of the programmers. Inheritance makes it possible to define new software in the same way we introduce any concept to a newcomer, by comparing it with something that is already familiar.”
Grady Booch (born 1955) first seen 1986 wikiquote, CC BY-SA 4.0 source
Recorded in: p. 56: Booch is citing: Cox, B. 1986. Object-Oriented Programming An Evolutionary Approach. Reading, MA: Addison-Wesley, p. 69.
“An operation is some action one object performs upon another in order to elicit a reaction.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“Ultimately, discovery and invention are both problems of classification, and classification is fundamentally a problem of finding sameness. When we classify, we seek to group things that have a common structure or exhibit a common behavior.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“If an abstraction is a kind of some other abstraction, or if it is exactly equal to the sum of its components, then inheritance is a better approach”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“The class Dog is functionally cohesive if its semantics embrace the behavior of a dog, the whole dog, and nothing but the dog.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“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 (born 1955) wikiquote, CC BY-SA 4.0 source
“Whereas object-oriented analysis typically focuses upon one specific problem at a time, domain analysis seeks to identify the classes and objects that are common to all applications within a given domain, such as missile avionics systems, compilers, or accounting software.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“Every software system needs to have a simple yet powerful organizational philosophy (think of it as the software equivalent of a sound bite that describes the system's architecture)... [A] step in [the] development process is to articulate this architectural framework, so that we might have a stable foundation upon which to evolve the system's function points.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“A class is a set of objects that share a common structure and a common behavior”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“[A class category is] a collection of classes, some of which are visible to other class categories, and others of which are hidden.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“In a quality object-oriented software system, you will find many classes that speak the language of the domain expert”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“Good people with a good process will outperform good people with no process every time.”
Grady Booch (born 1955) first seen 2004 wikiquote, CC BY-SA 4.0 source
Recorded in: p. 188 as cited in: Stefan Bergström, ‎Lotta Råberg (2004) Adopting the Rational Unified Process: success with the RUP. p. 92
“Is object-oriented technology mature enough upon which to build industrial-strength systems? Absolutely. Does this technology scale? Indeed. Is it the sole technology worth considering? No way. Is there some better technology we should be using in the future? Possibly, but I am clueless as to what that might be. It is dangerous to make predictions, especially in a discipline that changes so rapidly, but one thing I can say with confidence is that I have seen the future, and it is object-oriented.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“#The development of the Model Driven Architecture (MDA) standards by the Object Management Group (OMG)”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“#The adoption of the Precise Action Semantics for the Unified Modeling Language specification by the OMG in November of 2001”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“#A proposed profile of UML—Executable UML—supports creating a complete and implementation-neutral self-contained expression of application functionality. Steven J. Mellor and Marc J. Balcer define this profile in their book Executable UML: A Foundation for Model-Driven Architecture”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“#The availability of high-quality Model Compilers and Virtual Execution Environments (VEEs) that provide "out of the box" platforms upon which Executable UML models can execute. These VEEs, which exist today in a somewhat incipient stage, will someday soon reduce low-level system architectures to near-commodity status.”
Grady Booch (born 1955) first seen 2003 wikiquote, CC BY-SA 4.0 source
Recorded in: Cited in: Gerry Boyd (2003) "Executable UML: Diagrams for the Future." published at devx.com, February 5, 2003.
“How We Got Here”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“Where We Are Going”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“… I pounded the doors at the local IBM sales office until a salesman took pity on me. After we chatted for a while, he handed me a Fortran [manual]. I'm sure he gave it to me thinking, "I'll never hear from this kid again." I returned the following week saying, "This is really cool. I've read the whole thing and have written a small program. Where can I find a computer?" The fellow, to my delight, found me programming time on an IBM 1130 on weekends and late-evening hours. That was my first programming experience, and I must thank that anonymous IBM salesman for launching my career. Thank you, IBM.”
Grady Booch (born 1955) first seen 2003 wikiquote, CC BY-SA 4.0 source
Recorded in: Grady Booch (2003-04-03) in interview "Grady Booch polishes his crystal ball", IBM
“The (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 (born 1955) first seen 1999 wikiquote, CC BY-SA 4.0 source
Recorded in: James Rumbaugh, Ivar Jacobson, & Booch (1999) The Unified Modeling Language Reference Manual. p. 1
Also quoted by: Ivar Jacobson
“A physician, a civil engineer, and a computer scientist were arguing about what was the oldest profession in the world. The physician remarked, "Well, in the Bible, it says that God created Eve from a rib taken out of Adam. This clearly required surgery, and so I can rightly claim that mine is the oldest profession in the world." The civil engineer interrupted, and said, "But even earlier in the book of Genesis, it states that God created the order of the heavens and the earth from out of the chaos. This was the first and certainly the most spectacular application of civil engineering. Therefore, fair doctor, you are wrong: mine is the oldest profession in the world." The computer scientist leaned back in her chair, smiled, and then said confidently, "Ah, but who do you think created the chaos?”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“Philosophy and cognitive science have contributed to the advancement of the object model. The idea that the world could be viewed either in terms of objects or processes was a Greek innovation, and in the seventeenth century, we find Descartes observing that humans naturally apply an object-oriented view of the world. In the twentieth century, Rand expanded upon these themes in her philosophy of objectivist epistemology. More recently, Minsky has proposed a model of human intelligence in which he considers the mind to be organized as a society of otherwise mindless agents. Minsky argues that only through the cooperative behavior of these agents do we find what we call intelligence.”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source
“Today, we're at the beginning stages of the next level. Executable UML is the next logical, and perhaps inevitable, evolutionary step in the ever-rising level of abstraction at which programmers express software solutions. Rather than elaborate an analysis product into a design product and then write code, application developers of the future will use tools to translate abstract application constructs into executable entities. Someday soon, the idea of writing an application in Java or C++ will seem as absurd as writing an application in assembler does today. And the code generated from an Executable UML model will be as uninteresting and typically unexamined as the assembler pass of a third generation language compile is today. This shift is made possible by the confluence of four factors:”
Grady Booch (born 1955) wikiquote, CC BY-SA 4.0 source