Connie's Convenience Store - About Peter Coad

More documents

Recommendations

Info

28 Connie’s Convenience Store Applying Patterns: Select and Organize Problem-Domain Objects you keep track of start and end of employment, for each cashier object. Then one person object might know a number of cashier objects over time. However, if you don’t keep track of start and end dates, then an object connection constraint of “1” for person objects makes sense (Figure 1–17): Progress at this point Figure 1–17: person object knows one cashier object (and vice versa). You’ve selected objects, using strategies and patterns. Take a look at where you are (Figure 1–18): ProblemDomain Cash CashDrawer Cashier Charge Check Item Payment Person Register Sale SaleLineItem Session Store TaxCategory NotThisTime BackRoomServer Customer HeadCashier Organization POSClient Shelf Session n 1 Person Cashier 1 n Sale 1 n 1-n 1 SaleLineItem 1 1 Person Cashier Figure 1–18: Progress at this point. 1 1 1 n 1 n 1 Store n n 1 n 1 Item TaxCategory Register CashDrawer Payment Cash Check Charge
Establishing Responsibilities for Problem-Domain Objects Connie’s Convenience Store 29 ESTABLISHING RESPONSIBILITIES FOR PROBLEM-DOMAIN OBJECTS Every object in an object model has specific responsibilities. An object knows things about itself. An object knows other objects. An object does things, too: by itself or in collaboration with others. Your job: establish responsibilities, reflecting your system’s responsibilities to know and do. To get this done, use strategies for establishing responsibilities for: – what I know – who I know – what I do. Responsibilities for actors and participants Actor: person Establish responsibilities: “what I know.” #52. “Establish Actor and Participant Attributes” Strategy establishing responsibilities / what I know (pattern players) • For actor, consider: name, address, phone. • For participants, include: number, date and time (perhaps an ending date and time), password, authorization level. What do you need to know about each person? Whether a cashier or a customer, you’re likely to need some of the same information each time (Figure 1–19): – name – address – phone. name address phone Person Figure 1–19: Person: “what I know.”
Page 1 and 2: GETTING STARTED 1 Connie’s Conven
Page 3 and 4: Identifying System Purpose and Feat
Page 5 and 6: Selecting Objects Connie’s Conven
Page 7 and 8: Selecting Problem-Domain Objects Co
Page 19 and 20: Applying Patterns: Select and Organ
Page 27: Applying Patterns: Select and Organ
Page 31 and 32: Establishing Responsibilities for P
Page 55 and 56: Applying Patterns: Establish Proble
Page 61 and 62: Working Out Problem-Domain Dynamics
Page 63 and 64: Working Out Problem-Domain Dynamics
Page 65 and 66: Scenario: sale calculates its total
Page 67 and 68: Selecting Human-Interaction objects
Page 69 and 70: Establishing Human Interaction Resp
Page 71 and 72: Establishing Human Interaction Resp
Page 73 and 74: Working Out Human-Interaction Dynam
Page 75 and 76: Scenario: actual cashier logs on. S
Page 77 and 78: Scenario: sell item. Receipt SaleLi
Page 79 and 80:
Scenario: get payment by check Rece
Page 81 and 82:
Selecting System-Interaction Object
Page 83 and 84:
Establishing System-Interaction Res
Page 85 and 86:
Working Out System-Interaction Dyna
Page 87 and 88:
Selecting Data-Management Objects a
Page 89 and 90:
Working Out Data-Management Dynamic
Page 91 and 92:
Progress at This Point Connie’s C
Page 93 and 94:
Progress at This Point Connie’s C
Page 95:
Wrap Up Connie’s Convenience Stor
show all

Connie's Convenience Store - About Peter Coad

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?