SADM 7/ed - CTTS CASE STUDY - Milestone 7: Object Analysis Solution

Page: 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

SADM 7/ed - CTTS CASE STUDY - Milestone 7: Object Analysis Solution

Page: 7-2

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.

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

SADM 7/ed - CTTS CASE STUDY - Milestone 7: Object Analysis Solution

Page: 7-3

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
Address
Bar Code
Client
Client Name
Component Type
Configuration
Contact Name
Date Installed
Date Purchased
Date Removed
LAN IP
Email
Equip Name
Equip Type

Equipment
Equipment Component

Finish Time
In Service Date

Notes
The street address, city, state,
and zip of a client
A unique identifier stamped on
each component in inventory or
installed in equipment.
Someone who Coastline works
for. They may own equipment
serviced by Coastline.
The name of the client.
A classification of components,
such as NIC, video card,
mouse, keyboard, etc.
A software configuration setting
for the client.
The first and last name of the
contact person for a client.
The date a component was
installed in a piece of
equipment.
The date an inventory item was
purchased.
The date a component was
removed from a piece of
equipment
The IP address of a piece of
equipment on a client network.
The client's e-mail address.
Each piece of equipment can
be given a name.
We need to track whether a
piece of equipment is a PC, a
printer, a network device, or
something else.
Equipment that is owned by a
client and serviced by
Coastline.
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.
The ending time for a work
record.
When a piece of equipment
was placed in service.

Prepared by Gary B. Randolph for

Systems Analysis & Design Methods 6ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman

Obj
X

Reason
Attribute of Client
Attribute of Inventory

Attribute of Client

Attribute of Client
Attribute of Equipment Component

X
X

Attribute of Equipment
Attribute of Equipment Component

X
X
X
X

Instance of Configuration
Attribute of Client
Attribute of Equipment

X
X

Attribute of Work Record

Attribute of Equipment Component

Copyright Irwin/McGraw-Hill 2004

SADM 7/ed - CTTS CASE STUDY - Milestone 7: Object Analysis Solution

Information Name
Information Value
Installed Date
Inventory
Inventory Description
Management
Model Num
Phone
Problem
Problem Description
Quantity
Receptionist/Bookkeepe
r
Removed Date
Report Date
Reported By
Request Num
Resolution Date
Resolved
Service Request

Start Time
Technician
User Name

User Password

A name identifier for a

configuration data.
The data value of configuration
data.
The date that a component was
installed in a piece of
equipment.
A collection of all the items
placed into inventory.
A descriptive name of an item
in inventory.
A user of the system.
The model number of an item
in inventory.
Every client has a phone
number.
A problem reported by a client.
A description of the service
request problem.
The quantity of a component
installed on a piece of
equipment.
A user of the system.
The date a component was
removed from a piece of
equipment.
The date a service request is
reported.
The person at the clients office
reporting a service request.
An identifier for each service
request.
When a problem is solved.
A service request that has been
resolved.
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.
The starting time for a work
record.
Someone who does work for a
client and records that work in
various work records.
A login name for the system.
Various groups of users will
have differing rights within the
system.
A password used to verify a
user name.

Prepared by Gary B. Randolph for

Systems Analysis & Design Methods 6ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman

X
X

Page: 7-4

Attribute of Configuration
Attribute of Configuration
Attribute of Equipment Component

X
X
X
X

Attribute of Inventory
A specialized type of User
Attribute of Inventory
Attribute of Client
A synonym for Service Request
Attribute of Service Request
Attribute of Equipment Component

A specialized type of User

Attribute of Equipment Component

X
X
X
X

Attribute of Service Request

Attribute of Service Request
Attribute of Service Request

Attribute of Service Request

State of Service Request that can

be determined by Resolution Date.

Attribute of Work Record

A specialized type of User

X
X

Attribute of User. The User object

can be inferred from User Name
and User Password.
Attribute of User

Copyright Irwin/McGraw-Hill 2004

SADM 7/ed - CTTS CASE STUDY - Milestone 7: Object Analysis Solution

Vendor
Work Date
Work Description
Work Record

The seller of an item in

inventory.
The date of a work record.
The description of a work
record.
Work done by a technician, in
response to a service request.

Prepared by Gary B. Randolph for

Systems Analysis & Design Methods 6ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman

X
X
X

Page: 7-5

Attribute of Inventory
Attribute of Work Record
Attribute of Work Record

Copyright Irwin/McGraw-Hill 2004

SADM 7/ed - CTTS CASE STUDY - Milestone 7: Object Analysis Solution

Page: 7-6

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

Copyright Irwin/McGraw-Hill 2004