Milestone 07参考答案
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
MILESTONE 7 – OBJECT MODELING
Activity Diagram
Answers could vary depending on student assumptions. One solution is shown below.
System Sequence Diagram
Below is one solution for one scenario of the use case. Answers may vary. Check for proper UML notation of the input messages as well as for the logic of the diagram.
Potential Object List
Again, answers could vary somewhat depending on student assumptions, although the objects and their relationships should be fairly clear from the list.
Class Diagram
Again, answers could vary somewhat depending on student assumptions. One solution is shown below.
∙Class diagrams should not include foreign key attributes. Foreign key is a relational database concept that is not used in object-oriented analysis.
∙The Gen/Spec hierarchy can be inferred from the User object.
∙Some students might try to make a Gen/Spec relationship with EquipType and Equipment. If the data storage requirements or behaviors were different for the various EquipType
instances, then a Gen/Spec can be justified. But the provided solution is based on the
assumption that all types of equipment would have an equipName and a dateInservice and
no other data attributes.
∙ A case could be made for leaving EquipType and ComponentType off the object list and the class diagram. They mainly exist to provide lookup capabilities for Equipment and
EquipmentComponent, which is essentially an implementation issue.