“Object-oriented programming increases the value of these metrics by managing this complexity. The most effective tool available for dealing with complexity is abstraction. Many types of abstraction can be used, but encapsulation is the main form of abstraction by which complexity is managed in object-oriented programming.
Programming in an object-oriented language, however, does not ensure that the complexity of an application will be well encapsulated. Applying good programming techniques can improve encapsulation, but the full benefit of object-oriented programming can be realized only if encapsulation is a recognized goal of the design process.”

—  Rebecca Wirfs-Brock

Source: Object-oriented design: a responsibility-driven approach (1989), p. 71

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 "Object-oriented programming increases the value of these metrics by managing this complexity. The most effective tool a…" by Rebecca Wirfs-Brock?
Rebecca Wirfs-Brock photo
Rebecca Wirfs-Brock 13
American software engineer 1953

Related quotes

Grady Booch photo

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

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

“Object-oriented programming languages support encapsulation, thereby improving the ability of software to be reused, refined, tested, maintained, and extended. The full benefit of this support can only be realized if encapsulation is maximized during the design process.
We argue that design practices which take a data-driven approach fail to maximize encapsulation because they focus too quickly on the implementation of objects. We propose an alternative object-oriented design method which takes a responsibility-driven approach. We show how such an approach can increase the encapsulation by deferring implementation issues until a later stage.”

Rebecca Wirfs-Brock (1953) American software engineer

Source: Object-oriented design: a responsibility-driven approach (1989), p. 71: Abstract

“Encapsulation is the key to increasing the value of such software metrics as reusability, refinability, testability, maintainability, and extensibility. Object-oriented languages provide a number of mechanisms for improving encapsulation, but it is during the design phase that the greatest leverage can be realized.
The data-driven approach to object-oriented design focuses on the structure of the data in a system. This results in the incorporation of structural information in the definitions of classes. Doing so violates encapsulation.
The responsibility-driven approach emphasizes the encapsulation of both the structure and behavior of objects. By focusing on the contractual responsibilities of a class, the designer is able to postpone implementation considerations until the implementation phase.
While responsibility-driven design is not the only technique addressing this problem, most other techniques attempt to enforce encapsulation during the implementation phase. This is too late in the software life-cycle to achieve maximum benefits.”

Rebecca Wirfs-Brock (1953) American software engineer

Source: Object-oriented design: a responsibility-driven approach (1989), p. 75: Conclusion

Grady Booch photo

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

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

“In order to better understand object-oriented methodologies in general, it helps to understand the people who make up the "object-oriented community" itself. Far from being monolithic, there is a great deal of diversity within this community. Many object-oriented people, for example, seem to focus almost entirely on programming language issues. They tend to cast all discussions in terms of the syntax and semantics of their chosen object-oriented programming language. These people find it impossible (for all intents and purposes) to discuss any software engineering activity (e. g., analysis, design, and testing) without direct mention of some specific implementation language.
Outside of producing executable "prototypes", people who emphasize programming languages seldom have well-defined techniques for analyzing their clients' problems or describing the overall architecture of the software product. A great deal of what they do is intuitive. If they happen to have a natural instinct/intuition for good analysis or good design, their efforts on small-to-medium, non-critical projects can result in respectable software solutions.”

Edward V. Berard

Source: Essays on object-oriented software engineering (1993), p. 5

Grady Booch photo

“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

Brian W. Kernighan photo

“Controlling complexity is the essence of computer programming.”

Brian W. Kernighan (1942) Canadian computer scientist

Software Tools (1976), p. 319 (with P. J. Plauger).

Dwight D. Eisenhower photo

“The details of such disarmament programs are manifestly critical and complex.”

Dwight D. Eisenhower (1890–1969) American general and politician, 34th president of the United States (in office from 1953 to 1961)

1950s, The Chance for Peace (1953)
Context: The details of such disarmament programs are manifestly critical and complex. Neither the United States nor any other nation can properly claim to possess a perfect, immutable formula. But the formula matters less than the faith -- the good faith without which no formula can work justly and effectively. The fruit of success in all these tasks would present the world with the greatest task, and the greatest opportunity, of all. It is this: the dedication of the energies, the resources, and the imaginations of all peaceful nations to a new kind of war. This would be a declared total war, not upon any human enemy but upon the brute forces of poverty and need. The peace we seek, founded upon decent trust and cooperative effort among nations, can be fortified, not by weapons of war but by wheat and by cotton, by milk and by wool, by meat and timber and rice. These are words that translate into every language on earth. These are the needs that challenge this world in arms.

Grady Booch photo

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

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

Edsger W. Dijkstra photo

“The art of programming is the art of organizing complexity, of mastering multitude and avoiding its bastard chaos as effectively as possible.”

Edsger W. Dijkstra (1930–2002) Dutch computer scientist

Dijkstra (1970) " Notes On Structured Programming http://www.cs.utexas.edu/users/EWD/ewd02xx/EWD249.PDF" (EWD249), Section 3 ("On The Reliability of Mechanisms"), p. 7.
1970s

Related topics