“The control objects model functionality that is not naturally tied to any other object… We do not believe that the best (most stable) systems are built by only using objects that correspond to real-life entities, something that many other object-oriented analysis and design techniques claim… Behavior that we place in control objects will, in other methods, be distributed over several other objects, making it hard to change this behavior.”

— Ivar Jacobson

Source: Object-Oriented Software Engineering: A Use Case Driven Approach (1992), p. 133 as cited in: " Object Oriented Software Engineering: A Use Case Driven Approach Ivar Jacobson, et al. (1992) http://tedfelix.com/software/jacobson1992.html", Book review by Ted Felix on tedfelix.com, 2006.

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 "The control objects model functionality that is not naturally tied to any other object… We do not believe that the best…" by Ivar Jacobson?

Ivar Jacobson photo

Ivar Jacobson6

Swedish computer scientist 1939

Related quotes

“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

“Responsibility-driven design specifies object behavior before object structure and other implementation considerations are determined. We have found that it minimizes the rework required for major design changes.”

Rebecca Wirfs-Brock (1953) American software engineer

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

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

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

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

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

“Object-oriented domain analysis seeks to identify reusable items localized around objects e. g., classes, instances, systems of interacting objects, and kits.”

Edward V. Berard

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

“To every object there corresponds an ideally closed system of truths that are true of it and, on the other hand, an ideal system of possible cognitive processes by virtue of which the object and the truths about it would be given to any cognitive subject.”

Edmund Husserl (1859–1938) German philosopher, known as the father of phenomenology

Pure Phenomenology, 1917

“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

“For any given system, the environment is the set of all objects whose behaviour is influenced by the behaviour of the primary system, and those objects whose behaviour influences the behavior of the primary system.”

Arthur D. Hall (1925–2006) American electrical engineer

Source: Definition of System, 1956, p. 20 cited in: Baleshwar Thaku eds. (2003) Perspectives in resource management in developing countries. p. 54

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

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

Related topics