Scribd
Upload
60 views1 page

Responsibility-Driven Design

Responsibility-driven design is an object-oriented design technique that improves encapsulation using the client-server model by focusing on the responsibilities and shared information between objects. It avoids dealing with implementation details by specifying only the intent of requests between clients and servers.

Uploaded by

ChickenAdobo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
60 views1 page

Responsibility-Driven Design

Responsibility-driven design is an object-oriented design technique that improves encapsulation using the client-server model by focusing on the responsibilities and shared information between objects. It avoids dealing with implementation details by specifying only the intent of requests between clients and servers.

Uploaded by

ChickenAdobo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Responsibility-Driven Design (RDD)

Description:
Responsibility-driven design is a design technique in object-oriented programming, which improves
encapsulation by using the client–server model. It focuses on the contract by considering the actions that
the object is responsible for and the information that the object shares. It was proposed by Rebecca Wirfs-
Brock and Brian Wilkerson. Responsibility-driven design is in direct contrast with data-driven design,
which promotes defining the behavior of a class along with the data that it holds. Data-driven design is
not the same as data-driven programming, which is concerned with using data to determine the control
flow, not class design.

In the client–server model they refer to, both the client and the server are classes or instances of classes.
At any particular time, either the client or the server represents an object. Both the parties commit to a
contract and exchange information by adhering to it. The client can only make the requests specified in
the contract and the server must answer these requests. Thus, responsibility-driven design tries to avoid
dealing with details, such as the way in which requests are carried out, by instead only specifying the
intent of a certain request. The benefit is increased encapsulation, since the specification of the exact way
in which a request is carried out is private to the server.

To further the encapsulation of the server, Wirfs-Brock and Wilkerson call for language features that
limit outside influence to the behavior of a class. They demand that the visibility of members and
functions should be finely grained, such as in Eiffel programming language. Even finer control of the
visibility of even classes is available in the Newspeak programming language.

You might also like