Case Study CTTS - Milestone 07 Object Analysis Solution

March 27, 2018 | Author: Aly A Aly | Category: Object (Computer Science), Inventory, Software Engineering, Computer Engineering, Software


Comments



Description

SADM 7/ed - CTTS CASE STUDY - Milestone 7: Object Analysis SolutionPage: 7-1 MILESTONE 7 – OBJECT MODELING Activity Diagram Answers could vary depending on student assumptions. One solution is shown below. Prepared by Gary B. Randolph for Systems Analysis & Design Methods 6ed by J. L. Whitten, L. D. Bentley, & K. C. Dittman Copyright Irwin/McGraw-Hill 2004 Milestone 7: Object Analysis Solution Page: 7-2 System Sequence Diagram Below is one solution for one scenario of the use case. Bentley. Randolph for Systems Analysis & Design Methods 6ed by J. L. Check for proper UML notation of the input messages as well as for the logic of the diagram. L. C. & K. D. Answers may vary. Whitten.SADM 7/ed . Dittman Copyright Irwin/McGraw-Hill 2004 . Prepared by Gary B.CTTS CASE STUDY . SADM 7/ed . although the objects and their relationships should be fairly clear from the list. a network device. a printer. C. Whitten. Someone who Coastline works for.CTTS CASE STUDY . keyboard. The ending time for a work record. Bentley. The date a component was removed from a piece of equipment The IP address of a piece of equipment on a client network. L. D. They may own equipment serviced by Coastline. and zip of a client A unique identifier stamped on each component in inventory or installed in equipment. The first and last name of the contact person for a client. Some components are an entire computer or printer (because they are purchased as a unit). Randolph for Systems Analysis & Design Methods 6ed by J. video card. The client's e-mail address. Equipment that is owned by a client and serviced by Coastline. A classification of components. etc. state. L. The date a component was installed in a piece of equipment. The date an inventory item was purchased. Obj X X √ X √ √ X X X X X X X √ Instance of Configuration Attribute of Client Attribute of Equipment Attribute of Equipment Attribute of Equipment Component Attribute of Client Attribute of Equipment Component Attribute of Client Reason Attribute of Client Attribute of Inventory Equipment Equipment Component √ √ Finish Time In Service Date X X Attribute of Work Record Attribute of Equipment Component Prepared by Gary B. city. Equipment is made up of its components. The name of the client. Some are component pieces such as monitors. or something else. We need to track whether a piece of equipment is a PC. mice. When a piece of equipment was placed in service. A software configuration setting for the client.Milestone 7: Object Analysis Solution Page: 7-3 Potential Object List Again. etc. Dittman Copyright Irwin/McGraw-Hill 2004 . such as NIC. Potential Object Address Bar Code Client Client Name Component Type Configuration Contact Name Date Installed Date Purchased Date Removed LAN IP Email Equip Name Equip Type Notes The street address. Each piece of equipment can be given a name. mouse. & K. answers could vary somewhat depending on student assumptions. X X X √ X √ X X X X X √ X X X X X X Attribute of Service Request Attribute of Service Request Attribute of Service Request Attribute of Service Request A specialized type of User Attribute of Inventory A specialized type of User Attribute of Inventory Attribute of Client Attribute of Configuration Attribute of Configuration Page: 7-4 Attribute of Equipment Component A synonym for Service Request Attribute of Service Request Attribute of Equipment Component Attribute of Equipment Component State of Service Request that can be determined by Resolution Date. A password used to verify a user name. Attribute of User Start Time Technician User Name X X X User Password Prepared by Gary B. Dittman Copyright Irwin/McGraw-Hill 2004 . L. The model number of an item in inventory. Various groups of users will have differing rights within the system. When a problem is solved.SADM 7/ed . D. The date a component was removed from a piece of equipment.Milestone 7: Object Analysis Solution Information Name Information Value Installed Date Inventory Inventory Description Management Model Num Phone Problem Problem Description Quantity Receptionist/Bookkeeper Removed Date Report Date Reported By Request Num Resolution Date Resolved Service Request A name identifier for a configuration data. Every client has a phone number. An identifier for each service request. May be related to a specific piece of equipment. A login name for the system. Bentley. Randolph for Systems Analysis & Design Methods 6ed by J. The date a service request is reported. Submitted by or for a client to report a problem that needs to be worked on. The data value of configuration data. A descriptive name of an item in inventory. √ Attribute of Work Record A specialized type of User √ Attribute of User. C. The date that a component was installed in a piece of equipment. Someone who does work for a client and records that work in various work records. The starting time for a work record. A collection of all the items placed into inventory. A user of the system. & K. A description of the service request problem.CTTS CASE STUDY . Whitten. The quantity of a component installed on a piece of equipment. The User object can be inferred from User Name and User Password. The person at the client’s office reporting a service request. A service request that has been resolved. A user of the system. L. A problem reported by a client. Bentley. The description of a work record. Dittman Copyright Irwin/McGraw-Hill 2004 . Randolph for Systems Analysis & Design Methods 6ed by J. The date of a work record. D. in response to a service request.CTTS CASE STUDY . X X X √ Attribute of Inventory Attribute of Work Record Attribute of Work Record Page: 7-5 Prepared by Gary B. L. & K. Whitten. C.Milestone 7: Object Analysis Solution Vendor Work Date Work Description Work Record The seller of an item in inventory. L. Work done by a technician.SADM 7/ed . If the data storage requirements or behaviors were different for the various EquipType instances. Some students might try to make a Gen/Spec relationship with EquipType and Equipment. Prepared by Gary B. L. A case could be made for leaving EquipType and ComponentType off the object list and the class diagram. • • • • Class diagrams should not include foreign key attributes. answers could vary somewhat depending on student assumptions. One solution is shown below.CTTS CASE STUDY . which is essentially an implementation issue. Dittman Copyright Irwin/McGraw-Hill 2004 . L. D. then a Gen/Spec can be justified. & K. The Gen/Spec hierarchy can be inferred from the User object. Randolph for Systems Analysis & Design Methods 6ed by J. C. Bentley. They mainly exist to provide lookup capabilities for Equipment and EquipmentComponent. Foreign key is a relational database concept that is not used in object-oriented analysis.Milestone 7: Object Analysis Solution Page: 7-6 Class Diagram Again. 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. Whitten.SADM 7/ed .
Copyright © 2024 DOKUMEN.SITE Inc.