This link has been bookmarked by 15 people . It was first bookmarked on 06 Sep 2008, by Perry Branch.
-
14 Oct 17
-
31 Aug 14
-
21 Mar 13
-
A role interface is defined by looking at a specific interaction between suppliers and consumers.
-
-
07 Feb 13
-
With a role interface, however, we look at how the collaborating objects are actually used
-
a successor as a role that a collaborating object plays with respect to this object
-
with a role interface you only need to implement exactly what's needed
-
you should only use interfaces when you really need substitutability
-
-
28 Sep 12
-
The strength of a role interface is that it clearly communicates the actual collaboration between an activity and its successors
-
-
22 Dec 10
-
08 Feb 10
-
06 Sep 08
-
With a role interface, however, we look at how the collaborating objects are actually used. In this case a successor is only used for its
latestStartand a predecessor is only used for itsearliestFinish. So as a result we create two interfaces which only have the methods we actually use. -
The strength of a role interface is that it clearly communicates the actual collaboration between an activity and its successors
-
A header interface forces you to implement every method, even if you're not going to need them; but with a role interface you only need to implement exactly what's needed.
-
On the whole I much prefer role interfaces, so I suggest pushing towards them as much as you can.
-
belief has always been that you should only use interfaces when you really need substitutability, and if you do need interfaces you should think hard about what the consumer of that interface needs.
-
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.