uml课件Lect12-RESTAURANT SYSTEM-DESIGN.pptVIP

Lecture 12. System Design:  Restaurant Example 6-RESTAURANT SYSTEM-DESIGN Chapter 5已经完成了应用层用例实现。 We have finished application-layer use case realizations in Chapter 5. 本章任务是将建模应用到整个系统（包括其他层） Now we extend this level of modeling to the whole system. 6-RESTAURANT SYSTEM-DESIGN 本章研究输入, 输出, 永久数据存储 Now, some basic strategies for handling Input, output and persistent storage will be discussed 从分析得到的类图需要加细。 The analysis class diagram will be refined to contain fuller information about data types, message parameters and so on. 6-RESTAURANT SYSTEM-DESIGN 在设计结束时,我们对系统有一个比较完全的了解,系统实现可以开始. By the end of the design stage, we aim to have an understanding of the system that is detailed enough to permit implementation to begin. 6-RESTAURANT SYSTEM-DESIGN Some assumptions 餐馆定单系统是桌面单用户. The restaurant booking system will be implemented as a single-user desktop application (在局域网下，稍加修改，可以是多用户的). Java应用,基于Windows的用户界面. We will design it as a Java application with a window-based user interface. 用关系型数据库存储永久数据. A relational database will be used to store permanent data about bookings, customers and so on. 内容提要： Receiving Input From The User (Mark Priestley: 6.1) Producing Output (Mark Priestley: 6.2) Observer Pattern publisher-subscriber example Eaxmples of Observable/Observer 6.1 RECEIVING INPUT FROM THE USER 评论：在分析阶段，用户输入端系统消息被直接发送到应用层的BookingSystem, 这不合适。 In system analysis, system messages from the user were directed to a control object BookingSystem, which is an application layer object, This is not proper. 6.1 RECEIVING INPUT FROM THE USER We should use an object in the presentation layer to receive user input and forward requests on to the control object. The object in the presentation layer that receives user input can reasonably be characterized as a boundary object. 6.1 RECEIVING INPUT FROM THE USER Fig 6.1 collaboration diagram to handle a system message 6.1 RECEIVING INP