Connie's Convenience Store - About Peter Coad

Establishing System-Interaction Responsibilities Connie’s Convenience Store 83
ESTABLISHING SYSTEM-INTERACTION RESPONSIBILITIES
Authorization system and authorization system SI
The point-of-sale system interacts with some number of authorization systems.
Establish responsibility: “what I know.”
#56. “Establish Interacting System establishing responsibilities /
and Device Attributes” Strategy what I know (pattern players)
• For another system or device, include: number, name, operational state.
• For its companion object, in the system interaction component, include: address,
password.
An authorization system knows its:
– type (check or credit card)
– cost per transaction
– vendor number
– operational state.
An authorization-system SI object knows its:
– address.
Establish responsibility: “who I know.”
An authorization system object knows its authorization system SI object. Show this
with an attribute (textually), rather than with an object connection (graphically).
Establish responsibility: “what I do.”
#98. “Establish Interacting System or establishing responsibilities /
Device Services” Strategy what I do (pattern players)
• For an interacting system or device, include: activate, monitor (maintain), report,
deactivate (plus calculate for me, rate me, is ).
• For an interacting system or device as a collection, include: how many, how much, rank
parts, calculate over parts.
• Add a corresponding object in the system interaction (SI) component, to isolate specific
interaction needs (examples: connect, logon, query, logoff, disconnect).
An authorization system knows how to:
– get authorization (payment type, amount; authorization code).
An authorization system SI object knows how to connect, log on, query, log off,
and disconnect.