Student_Answers_Chapter_【DOC精选】.doc

Suggested answer for Exercise 5.1 The restaurant object is clearly not a boundary object, but it might appear to share some characteristics of both control and entity objects. As it is responsible for maintaining data, it might be argued that the entity stereotype was appropriate. This stereotype is normally used for data in the system that represents a single external entity, however. The restaurant object does not represent an entity in this sense, however, but instead makes other entities available in the system. The entity stereotype is probably not appropriate for the restaurant object, therefore. There is a control aspect to the restaurant object, as it is controlling access to the entity data held by the system. This is more a question of being a `gatekeeper to some system resources than controlling a number of interactions, as the booking system object does, and it is probably clearer not to represent both by the same stereotype. It therefore appears that none of the analysis class stereotypes straightforwardly applies to the restaurant object, and it has been left in Figure 5.4 as a plain object. Suggested answer for Exercise 5.2 The date attribute in the booking system class represents the date for which booking information is currently being displayed by the system. The date attribute in the `current bookings should be the same as this, therefore, otherwise the system will be displaying bookings for the wrong date. This can be specified by a constraint on the `current association as shown below. Suggested answer for Exercise 5.3 On the face of it, this proposal might seem to be attractive on the grounds of removing redundancy, following the guideline that data should not be stored in more than one place. However, removing the date attribute from the booking system object would create problems in the situation where there are no bookings yet recorded for a date the system is asked to display. In this case, the system would have no record of wha