Connie's Convenience Store - About Peter Coad
Connie's Convenience Store - About Peter Coad
Connie's Convenience Store - About Peter Coad
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
84 Connie’s <strong>Convenience</strong> <strong>Store</strong> Establishing System-Interaction Responsibilities<br />
Add both objects to your model (Figure 1–58):<br />
Figure 1–58: Objects for an interacting system.<br />
A collection of authorization systems<br />
What if you want to work with many authorization systems, using the least expensive<br />
one first, then others on an as-needed basis? That’s responsibility across a collection of<br />
authorization systems.<br />
#23. “Select a Collection” Strategy selecting objects (pattern players)<br />
• What if you need a collection of objects, yet such a collection has no special name?<br />
Add a collection, using a plural form of the worker name. Example: authorization<br />
systems.<br />
Add a collection, using the worker name, followed by the word “collection” or “server.”<br />
Example: authorization server.<br />
You need a collection of authorization systems. You could call it:<br />
– authorization system collection<br />
– authorization systems<br />
– authorization server.<br />
Go ahead and use “authorization server.” It sounds cool.<br />
Establish responsibility: “what I know.”<br />
Nothing is needed here.<br />
AuthorizationSystem<br />
operationalState<br />
address<br />
vendorNumber<br />
type<br />
cost<br />
authorizationSystemSI<br />
getAuthorization<br />
AuthorizationSystemSI<br />
address<br />
connect<br />
logon<br />
query<br />
logoff<br />
disconnect