Connie's Convenience Store - About Peter Coad

More documents

Recommendations

Info

68 Connie’s Convenience Store Selecting Human-Interaction objects Window objects for this system What’s needed at Connie’s Convenience Store? – a logon window – a transaction window – a sale (and payment) window – some transaction participant windows a store window a cashier window a register window a cash drawer window a tax category window a UPC window an item (and price) window – a results window a store assessment window. Select reports What kind of reports might you need? – legally required reports – business-required reports. You don’t need to attempt to model all of the reports you may eventually get with ad hoc queries to a database. That would be silly. You don’t need batch-checking reports of an existing system. You don’t need hardcopy “nut and bolts” like printers. Report objects for this system What’s needed this time? #31. “Select Reports” Strategy selecting objects (model components) • Put together key summaries and specialized outputs, meeting specific legal or business needs. • Look carefully at who (audience) needs what (content), and why (purpose). • Don’t include every ad hoc query that someone might eventually ask; don’t include outdated batch reports. A cashier works with one important report: – a receipt. What other reports do you need? Check out the system features. These reports support those objectives: – a store report – an item report – a cashier report where each report spans a requested time interval, whatever that interval might be.
Establishing Human Interaction Responsiblities Connie’s Convenience Store 69 Add windows and reports to the human interaction component (Figure 1–44): HumanInteraction CashierDrawerWindow CashierReport CashierWindow ItemReport ItemWindow LogonWindow Receipt RegisterWindow SaleWindow StoreAssessmentWindow StoreReport StoreWindow TaxCategoryWindow UPCWindow LogonWindow StoreWindow CashierWindow TaxCategoryWindow StoreAssessmentWindow Receipt UPCWindow ItemWindow SaleWindow Figure 1–44: Select human interaction windows and reports. ESTABLISHING HUMAN INTERACTION RESPONSIBILITIES Responsibilities for windows RegisterWindow StoreReport CashierReport ItemReport CashDrawerWindow How to model a window effectively In an object model, a window knows what it holds: its components and its screen layout. Consider a window’s components. A window may contain many objects, including views, panes, edit fields, list boxes, menus, buttons, and the like. These objects all work together to create the effect of one large object, a window. You could build a rather large and complex model for each window. But why? Face it: the tool of choice for building windows in most applications is a GUI builder, one that generates C++ or Smalltalk code. (The only time you would write something yourself, with the help of some graphic class libraries, is when you are building an application that requires some specialized graphics manipulation.) A far better approach? Here it is: – In your object model, establish what each window knows and does. – While working with your GUI builder, select mechanisms (views, panes, edit fields, list boxes, menus, buttons, and the like) so that a window fulfills its responsibilities.
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 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18: Selecting Problem-Domain Objects Co
Page 19 and 20: Applying Patterns: Select and Organ
Page 29 and 30: 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: Selecting Human-Interaction objects
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?