Connie's Convenience Store - About Peter Coad
Connie's Convenience Store - About Peter Coad
Connie's Convenience Store - About Peter Coad
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
8 Connie’s <strong>Convenience</strong> <strong>Store</strong> Selecting Problem-Domain Objects<br />
Select actors and participants<br />
An actor is a person, an organization, or some other thing that participates in one or<br />
more ways over time. A participant participates in a specific way, plays a role, fulfills a<br />
specific mission.<br />
What are the actors and participants in this system?<br />
#13. “Select Actors” Strategy selecting objects (pattern players)<br />
• Look for actors: people and organizations that act as participants within the system under<br />
consideration.<br />
• Examples: person, organization (agency, company, corporation, foundation).<br />
Here, the actor is:<br />
– person.<br />
Organization could be interesting, too. Maybe later.<br />
#14. “Select Participants” Strategy selecting objects (pattern players)<br />
• Analyze how each actor participates, in ways that might be of interest to the system under<br />
consideration.<br />
• Why. Each actor participates in one or more ways through time. It’s the same actor, just<br />
different ways of participating.People talk about wearing “different hats” during the day.<br />
That’s exactly what such participation is all about.<br />
• Examples: agent, applicant, buyer, cashier, clerk, client, civilian, customer, dealer,<br />
delegate, distributor, donor, employee, investor, manufacturer, member, officer, official,<br />
order clerk, owner, participant, policy holder, professional, prospect, recipient, retailer,<br />
sales clerk, sales rep, shipper, student, subscriber, supervisor, supplier, suspect, teacher,<br />
wholesaler, worker.<br />
In what interesting ways does a person participate when using a point-of-sale system?<br />
Why, there’s:<br />
– cashier<br />
– head cashier<br />
– customer.<br />
What objects do you need? The system purpose and features give you a standard, a<br />
checkpoint, for making that decision. Here’s how. If an object fits within the context of<br />
the system’s responsibilities, then include it. If not, then (1) add to the system features<br />
or (2) put that object in the “not this time” model component.<br />
Consider cashier, head cashier, and customer.