SADM 5/ed – CASE STUDY 3 – Milestone A: Object Modeling
Page: A-1
MILESTONE A – OBJECT MODELING 1
 Synopsis
O
bject-oriented analysis techniques are best suited to projects that will
implement systems using emerging object technologies. The object-oriented
approach is centered around a technique referred to as object modeling.
The object-oriented approach to system development is based on the concept
of objects that exist within a system’s environment. Objects are everywhere. Let’s
consider your environment, look around. What are some of the objects present within
your environment? Perhaps you see a door, a window, or the room itself. What about
this book  it’s an object, and so is the very page you are reading. And of course,
don’t forget about you. You are an object. Perhaps you also have a student workbook
with you, and there are other individuals in the room. You may also see phone, a
chair, and perhaps a table. All of these things represent objects that may be clearly
visible within your immediate environment.
In performing Object-Oriented Analysis (OOA), like any other systems analysis
method, the purpose is to gain a better understanding of the system and its functional
requirements. In other words, OOA requires that we identify the objects, their data
attributes, associated behavior, and relationships that support the required business
system functionality. We perform object modeling to document the identified
objects, the data, and the behavior they encapsulate, plus their relationships with
other objects.
1
The object modeling milestone can be done as a substitute for Milestones 3-5 (in a pure OO project), or as a
complement to Milestones 3-5 (to compare and contrast structured and object methods).
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2001
SADM 5/ed – CASE STUDY 3 – Milestone A: Object Modeling
Page: A-2
In this milestone you will construct various object models used to communicate the
scope and requirements of the project. First, you will create a context model. Second,
you will perform use case modeling to document the business requirements and
identify the necessary objects required by the system. Finally, you will construct a
class structure diagram to graphically depict the object classes that make up the
system as well as the objects’ relationships with each other.
 Objectives
After completing this milestone, you should be able to:
 Construct a context model to communicate project scope and boundaries.
 Prepare use case diagrams to depict the scope and boundaries of a system in terms
of actors and use cases.
 Document a use case’s course of events.
 Construct a class structure diagram to depict the objects of the system and how
they are related to each other.
 Prerequisites
Before starting this milestone, the following topics should be covered:
1. Object Modeling – Module A
 Assignment
There are two general activities when performing object-oriented analysis and they
are as follows:
1. Finding and identifying the business objects (use case analysis).
2. Organizing the objects and identifying their relationships (structure analysis).
 Activities
1. Construct the context model using the accompanying narrative (Exhibit A.1).
Make assumptions where necessary.
2. Construct the use case models. Make assumptions where necessary.
3. Document a use case’s course of events based upon the provided narrative
describing the event of Make New Assignment (Exhibit A.2). Make assumptions
where necessary.
4. Construct the class structure diagram using the use case course of events
completed in Activity 3 above. Make assumptions where necessary.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2001
SADM 5/ed – CASE STUDY 3 – Milestone A: Object Modeling
Page: A-3
Deliverable format and software to be used are according to your instructor’s
specifications. Deliverables should be neatly packaged in a binder, separated with a
tab divider labeled “Milestone A” and accompanied with a Milestone Evaluation
Sheet.
References:
Pinnacle Publishing Scope Narrative
Exhibit A.1
Pinnacle Make New Assignment Narrative
Exhibit A.2
Templates
See online learning center web site for the textbook.
Deliverables:
Context Model:
Due: __/__/__
Time:_______
Use Case Model:
Due: __/__/__
Time:_______
Course Of Events:
Due: __/__/__
Time:_______
Class Structure Diagram:
Due: __/__/__
Time:_______
Milestone’s Point Value:
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
_______
Copyright Irwin/McGraw-Hill 2001
SADM 5/ed – CASE STUDY 3 – Milestone A: Object Modeling
Page: A-4
Exhibit A.1
Use the following narrative to construct the Context Model for the Pinnacle Publishing sales and
book tracking system.
The purpose of the sales and book tracking system is to provide a single central
repository of all information about sales leads, books in process, and books for
sale. The Sales Department will enter new authors to the system as they gather
leads from various sources. Salespeople can also request mailing labels at any
time for sending information to authors. As salespeople enter information on their
phone calls, the system will produce weekly recall lists to help the salespeople
schedule their calls. Management also wants to receive a weekly sales
performance report from the system.
Once a salesperson sells a publishing contract to an author and the author sends in
a manuscript, the Production Department will create a book record to track the
book through the production process. Each book will be assigned a “shepherd”
who will oversee the production process for that book. The system will provide
the shepherd with a list of the status of each of his or her books each day. When
the shepherd sees that a task has been finished for a book, the shepherd will assign
another task and select the technician to accomplish that task. The system will
communicate that assignment to the technician via e-mail as soon as the new task
is created. Technicians will enter updated information to the system as they
complete their tasks. The system will also output information daily from the
database to a self-service web site where authors can check on the status of their
books. As the book comes to press, production people will enter information
about promotions being done, ISBN, and other information.
When the Accounting Department requests it, sales information on books that are
published will be imported from several external e-commerce web sites. The
Accounting Department also can request royalty reports that are calculated from
this information.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2001
SADM 5/ed – CASE STUDY 3 – Milestone A: Object Modeling
Page: A-5
Exhibit A.2
Use the following narrative to construct the use case course of events for “Make New Assignment.”
As the Book “Shepherd” enters a Book ID, Task ID, and Technician ID for the
new assignment, verify all IDs. If any of the IDs are not valid, send a response to
the Book “Shepherd.” Add the new task assignment to the Task Work data store.
Generate e-mail to technician.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2001