„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, p. 35
Publicidade

Citações relacionadas

Grady Booch photo
Publicidade
Grady Booch photo
Ed Yourdon photo

„OOA - Object-Oriented Analysis - is based upon concepts that we first learned in kindergarten: objects and attributes, wholes and parts, classes and members.“

—  Ed Yourdon American software engineer and pioneer in the software engineering methodology 1944 - 2016
p. 1; cited in: Sten Carlsson and Benneth Christiansson. (1999) " The Concept of Object and its Relation to Human Thinking: Some Misunderstandings Concerning the Connection between Object-Orientation and Human Thinking http://www.vits.org/publikationer/dokument/289.pdf." Informatica, Lith. Acad. Sci. 10.2. p. 147-160.

„OOA - Object-Oriented Analysis - is based upon concepts that we first learned in kindergarten: objects and attributes, wholes and parts, classes and members.“

—  Peter Coad American software entrepreneur 1953
Peter Coad & Ed Yourdon (1991, p. 1); cited in: Sten Carlsson and Benneth Christiansson. (1999) " The Concept of Object and its Relation to Human Thinking: Some Misunderstandings Concerning the Connection between Object-Orientation and Human Thinking http://www.vits.org/publikationer/dokument/289.pdf." Informatica, Lith. Acad. Sci. 10.2. p. 147-160.

Publicidade
Grady Booch photo
Lotfi A. Zadeh photo
Grady Booch photo
Grady Booch photo
Publicidade
George Dantzig photo
Grady Booch photo

„In a quality object-oriented software system, you will find many classes that speak the language of the domain expert“

—  Grady Booch American software engineer 1955
p. 39; as cited in: Journal of Database Management. Vol 10-11. p. 33

Paulo Freire photo

„A conceptual level view of an object design describes the key abstractions. While someone might think of key abstractions as being nothing more or nothing less than high-level descriptions of "candidate classes", I prefer to consider a conceptual design from a slightly different angle--I'm thinking about design at a slightly different level.
An object-oriented application is a set of interacting objects. Each object is an implementation of one or more roles. A role supports a set of related (cohesive) responsibilities. A responsibility is an obligation to perform a task or know certain information. And objects don't work in isolation, they collaborate with others in a community to perform the overall responsibilities of the application. So a conceptual view, at least to start, is a distillation of the key object roles and their responsibilities (stated at a fairly high level). More than likely (unless you form classification hierarchies and use inheritance and composition techniques) many candidates you initially model will map directly to a single class in some inheritance hierarchy. But I like to open up possibilities by think first of roles and responsibilities, and then as a second step towards a specification-level view, mapping these candidates to classes and interfaces.“

—  Rebecca Wirfs-Brock American software engineer 1953
Rebecca Wirfs-Brock (2003) in " An Interview with Rebecca Wirfs-Brock Author of Object Design http://www.objectsbydesign.com/books/RebeccaWirfs-Brock.html" 2003-2005 Objects by Design, Inc: Answer to the question Can you clarify what you consider to be the essential elements of a "conceptual view".

Próximo