Responsibility-driven design: Difference between revisions

Revision as of 22:01, 20 February 2017

Revision as of 00:39, 30 April 2017

Line 1:

{{primary sources|date=December 2012}}

'''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_Object (computer_sciencecomputer science)|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.

Line 89:

;Advantages

* It is easy to understand.

* Though there is an external coordinator, Objects can be be made smarter to know what they are supposed to do and can be reused in other applications.

* Delegating coordinators tend to know about fewer objects than dominating controllers.

* Dialogs are higher-level.