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.

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.

Potential Object / Notes / Obj / Reason
Address / The street address, city, state, and zip of a client / X / Attribute of Client
Bar Code / A unique identifier stamped on each component in inventory or installed in equipment. / X / Attribute of Inventory
Client / Someone who Coastline works for. They may own equipment serviced by Coastline. / √
Client Name / The name of the client. / X / Attribute of Client
Component Type / A classification of components, such as NIC, video card, mouse, keyboard, etc. / √
Configuration / A software configuration setting for the client. / √
Contact Name / The first and last name of the contact person for a client. / X / Attribute of Client
Date Installed / The date a component was installed in a piece of equipment. / X / Attribute of Equipment Component
Date Purchased / The date an inventory item was purchased. / X / Attribute of Equipment
Date Removed / The date a component was removed from a piece of equipment / X / Attribute of Equipment Component
LAN IP / The IP address of a piece of equipment on a client network. / X / Instance of Configuration
Email / The client's e-mail address. / X / Attribute of Client
Equip Name / Each piece of equipment can be given a name. / X / Attribute of Equipment
Equip Type / We need to track whether a piece of equipment is a PC, a printer, a network device, or something else. / √
Equipment / Equipment that is owned by a client and serviced by Coastline. / √
Equipment Component / Equipment is made up of its components. Some components are an entire computer or printer (because they are purchased as a unit). Some are component pieces such as monitors, mice, etc. / √
Finish Time / The ending time for a work record. / X / Attribute of Work Record
In Service Date / When a piece of equipment was placed in service. / X / Attribute of Equipment Component
Information Name / A name identifier for a configuration data. / X / Attribute of Configuration
Information Value / The data value of configuration data. / X / Attribute of Configuration
Installed Date / The date that a component was installed in a piece of equipment. / X / Attribute of Equipment Component
Inventory / A collection of all the items placed into inventory. / √
Inventory Description / A descriptive name of an item in inventory. / X / Attribute of Inventory
Management / A user of the system. / √ / A specialized type of User
Model Num / The model number of an item in inventory. / X / Attribute of Inventory
Phone / Every client has a phone number. / X / Attribute of Client
Problem / A problem reported by a client. / X / A synonym for Service Request
Problem Description / A description of the service request problem. / X / Attribute of Service Request
Quantity / The quantity of a component installed on a piece of equipment. / X / Attribute of Equipment Component
Receptionist/Bookkeeper / A user of the system. / √ / A specialized type of User
Removed Date / The date a component was removed from a piece of equipment. / X / Attribute of Equipment Component
Report Date / The date a service request is reported. / X / Attribute of Service Request
Reported By / The person at the client’s office reporting a service request. / X / Attribute of Service Request
Request Num / An identifier for each service request. / X / Attribute of Service Request
Resolution Date / When a problem is solved. / X / Attribute of Service Request
Resolved / A service request that has been resolved. / X / State of Service Request that can be determined by Resolution Date.
Service Request / Submitted by or for a client to report a problem that needs to be worked on. May be related to a specific piece of equipment. / √
Start Time / The starting time for a work record. / X / Attribute of Work Record
Technician / Someone who does work for a client and records that work in various work records. / √ / A specialized type of User
User Name / A login name for the system. Various groups of users will have differing rights within the system. / X / Attribute of User. The User object can be inferred from User Name and User Password.
User Password / A password used to verify a user name. / X / Attribute of User
Vendor / The seller of an item in inventory. / X / Attribute of Inventory
Work Date / The date of a work record. / X / Attribute of Work Record
Work Description / The description of a work record. / X / Attribute of Work Record
Work Record / Work done by a technician, in response to a service request. / √

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.

Prepared by Gary B. Randolph for

Systems Analysis & Design Methods 6ed

by J. L. Whitten, L. D. Bentley, & K. C. DittmanCopyright Irwin/McGraw-Hill 2004