“A subsystem is a set of classes (and possibly other subsystems) collaborating to fulfill a set of responsibilities. Although subsystems do not exist as the software executes, they are useful conceptual entities.”

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

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 "A subsystem is a set of classes (and possibly other subsystems) collaborating to fulfill a set of responsibilities. Alt…" by Rebecca Wirfs-Brock?
Rebecca Wirfs-Brock photo
Rebecca Wirfs-Brock 13
American software engineer 1953

Related quotes

“Development of an organism from a single germ cell into a multicellular entity is a self-organizing system from any point of view and I wish to contend that this self-organizing system is a subsystem of the self-organizing system called 'evolution.”

Gordon Pask (1928–1996) British psychologist

Source: An Approach to Cybernetics (1961), p. 103-104, partly cited in: Darren Tofts, Annemarie Jonson, Alessio Cavallaro (2004) Prefiguring Cyberculture: An Intellectual History.

““The term (system-of-systems) is being applied to the creation of new systems by bringing together existing operational systems under a single umbrella and, presumably, creating or adapting links and interactions between the operational systems, which become subsystems of the higher level umbrella system.””

Derek Hitchins (1935) British systems engineer

Source: Advanced Systems Thinking, Engineering and Management (2003), p. 80 as cited in: Jung-Ho Lewe (2005) An Integrated Decision-Making Framework for Transportation Architectures https://smartech.gatech.edu/jspui/bitstream/1853/6918/1/Jung-Ho_Lewe_200505_phd.pdf. p.

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

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

Fred Brooks photo

Related topics