Systems Analysis and Design, Tenth Edition Page 1 of 42

Systems Analysis and Design, Tenth Edition

End of Chapter Solutions

Chapter Exercises s

Questions
1. What is object-oriented analysis, and what are some advantages of this method?
Object-oriented analysis is a popular approach that sees a system from the viewpoint of the
objects themselves as they function and interact with the system during the implementation
phase of the SDLC. Systems analysts and programmers transform the objects into program
code modules. A modular approach saves money and time, because the modules can be
optimized, tested, and reused as often as necessary. (Page 230)

2. Define an object, and provide three examples.

An object represents a real person, place, event, or transaction. For example, when a
patient makes an appointment to see a doctor, the patient is an object, the doctor is an
object, and the appointment itself is an object. (Page 230)

3. Define an attribute, and provide three examples.

Attributes are characteristics that describe the object. For example, if you own a vehicle, it
has attributes such as make, model, and color. (Page 230)

4. Define a method, and provide three examples.

A method defines specific tasks that an object can perform. Just as objects are similar to
nouns and attributes are similar to adjectives, methods resemble verbs that describe what
and how an object does something. For example, a student object can register for a course,
pay a tuition bill, and submit an assignment. (Page 230)

5. Define encapsulation, and explain how it is used in object-oriented analysis.

Encapsulation means that all data and methods are self-contained. By limiting access to
internal processes, an object prevents its internal code from being altered by another object
or process. Encapsulation allows objects to be used as modular components anywhere in
the system, because objects send and receive messages, but do not alter the internal methods
of other objects. (Page 236)

6. Define polymorphism, and provide three examples.

Polymorphism is the concept that a message can have different meanings to different
objects. For example the message GOOD NIGHT signals the PARENT object to read a
bedtime story, but the same message to the DOG object tells the dog to go to sleep. The
GOOD NIGHT message to the CHILD object signals it to get ready for bed. (Page 235)
Systems Analysis and Design, Tenth Edition Page 2 of 42

7. Define a class, subclass, and superclass, and provide three examples of each.
A class is a group of similar objects. Subclasses are more specific categories within a class.
A superclass is a more general category into which a class falls. For example, a NOVEL
class belongs to a superclass called BOOK, because all novels are books. The NOVEL class
can have subclasses called HARDCOVER and PAPERBACK. Students be able to suggest
many more examples of this concept. (Pages 236 - 237)

8. Define an actor, and provide three examples.

An actor is an external entity that initiates a use case by requesting the system to perform a
function or process. For example, in a medical office system, a PATIENT (actor) can MAKE
AN APPOINTMENT (use case). In a library, a library patron member can borrow a book,
and in an auto shop, a mechanic actor can perform tasks. (Page 239)

9. Define a use case and a use case diagram, and prepare a sample of each.
A use case represents the steps in a specific business function or process. A use case
diagram is a visual summary of related use cases within a system or subsystem. One
example is an auto service department. The operation involves customers, service writers
who prepare work orders and invoices, and mechanics who perform the work.
Example of a use case diagram for an auto service department: (Page 239; 241)
Systems Analysis and Design, Tenth Edition Page 3 of 42

10. Define the term black box, and explain why it is an important concept in object-oriented
analysis. Can you think of other black boxes that you use in everyday life?
An object can be viewed as a black box, because a message to the object triggers changes
within the object without specifying how the changes must be carried out. One advantage to
using a black box approach is that you do not need to think about how the object performs a
task, as long as it does so properly. (Page 235)

Discussion Topics
1. The chapter mentioned that systems analysts and programmers transform objects into
program code modules that can be optimized, tested, and reused. Modular design is a very
popular design concept in many industries. What other examples of modular design can you
suggest?
Examples might include the following: Car manufacturers that offer options that customers
can add or remove when they custom-order a vehicle; or computer vendors that allow
customers to pick and choose hardware and software options to build a customized
computer system.

2. You are an IT consultant, and you are asked to create a new system for a small real estate
brokerage firm. Your only experience is with traditional data and process modeling
techniques. This time, you decide to try an object-oriented approach. How will you begin?
How are the tasks different from traditional structured analysis?
After the initial research is completed, you would identify all possible actors and objects
and determine how they will interact with one another. Because this method integrates data
and processes into objects, it differs from structured analysis, which treats data and
processes as two separate concepts.

3. You are creating a system for a bowling alley to manage information about its leagues.
During the modeling process, you create a state transition diagram for an object called
LEAGUE BOWLERS. What are the possible states of a league bowler, and what happens to
a bowler who quits the league and rejoins the following season?
The possible states of a league bowler might include: Potential (signed up but has not been
sanctioned), Active (signed up, sanction fees paid), Suspended (Delinquent in dues), Former
(quit league or delinquent beyond reasonable limit).

4. A debate is raging at the IT consulting firm where you work. Some staff members believe
that it is harder for experienced analysts to learn object-modeling techniques, because the
analysts are accustomed to thinking about data and processes as separate entities. Others
believe that solid analytical skills are easily transferable and do not see a problem in
crossing over to the newer approach. What do you think, and why?
Some experienced analysts find it difficult to change their way of thinking; others grasp the
object-oriented approach easily. Many analysts recognize the current trend toward object-
oriented analysis and design, but differ in their views about the value of object-oriented
methodology.

Projects
1. Search the Internet for information about the history and development of UML.
Students should have no difficulty locating this information. A recent search using the
phrase “History of UML” produced many results, several of which are shown in the
following screen:
Systems Analysis and Design, Tenth Edition Page 4 of 42

2. Contact the IT staff at your school or at a local business to learn whether the organization
uses object-oriented programming languages. If so, determine what languages and versions
are used and why they were selected.
The results should be interesting. Many organizations use Visual Basic, C++, and Java. If
students cannot determine whether object-oriented languages are used, you might suggest
that they perform some research on the Internet to learn more about the growth and
popularity of various programming languages.

3. Search the Internet for information about groups and organizations that support and discuss
object-oriented methods and issues.
As in Project 1, students should have little difficulty in locating information by using
standard search techniques.

4. Search the Internet for information about CASE tools that provide UML support.
In Google and many other search engines, it is possible to base a search on more than one
phrase, or a phrase and one or more additional terms. For example, the following screen
shows the results of a Google search on the combined search terms "CASE Tools" and
“UML support”.
Systems Analysis and Design, Tenth Edition Page 5 of 42
 Systems Analysis and Design, Tenth Edition Page 6 of 42

Apply Your Knowledge al] e

1 Osceola Auto Parts

Osceola Auto Parts is an independent auto parts dealer that sells auto parts, runs tests on
customers’ cars, and delivers parts and tools to mechanic shops around town.

Tasks
1. Identify possible actors and use cases involved in Osceola’s business functions.
Answers will vary; sample answers provide a model for students.
Actors might include Customer, Mechanics, and Delivery Drivers. Use cases might include
Buy Parts, Manage Parts Inventory, Test Customers Cars, and Deliver Parts. Sample
documentation for the Buy Parts use case is shown in the following table.

Name: Buy Parts

Actor: Customer/Store Associate
Description: This use case describes the process used to buy parts at the auto parts
dealer.
Successful 1. Customer requests auto part
Completion: 2. Store Associate checks on availability of part
3. Part is available and customer pays cost
4. Customer receives part and stock is adjusted
Alternative: 1. Customer requests auto part
2. Store Associate checks on availability of part
3. Part is not available and customer selects to order part or no part
4. Customer receives part and stock is adjusted (if alternate part
ordered) or customer leaves with no part
Pre- Customer wants to purchase part
Condition:
Post- None
Condition:
Assumptions: None
 Systems Analysis and Design, Tenth Edition Page 7 of 42

2. Create a use case diagram for Osceola’s operations.

A sample use case diagram for the Buy Part and Manage Part Inventory use cases follows:

Requests Sells Part

Part

Buy Part
CUSTOMER
STORE
ASSOCIATE
Adjusts
Inventory

Changes
Min/Max
Levels

Manage Part
Inventory
Systems Analysis and Design, Tenth Edition Page 8 of 42

3. Select one of the use cases and create a class diagram.

A sample class diagram for the Buy Parts use case follows:

Requests
Store Associate parts Customer

Employee number Customer type

0..* 0..* Payment method
SSN
Name
Hire date
Date of birth

Sell Parts Request Parts

Test Cars Purchase Parts
Deliver Parts Make payment

Receive delivery
0..* Request other services

0..*
Sells Part 1..* Changes
min/max
levels

1 Adjusts 1..*

Transaction Record Parts Inventory

Part ID Part ID
Invoice Number Part Model
Date Quantity in stock
Number purchased Minimum level
Amount due Maximum level
Payment method
Adjust minimum
Adjust maximum
Adjust Part inventory Report stock value
Apply adjustment
Systems Analysis and Design, Tenth Edition Page 9 of 42

4. Create a sequence diagram for the use case you selected.

A sample sequence diagram for the Buy Parts use case follows:

Customer Store Part Inventory Transaction

Associate Record

Request Part

Check Availability
Notify
STUDENT
Pay

Handle
Transaction

Decrease
Inventory

X
 Systems Analysis and Design, Tenth Edition Page 10 of 42

2 Area Transit Authority

The Area Transit Authority (ATA) is a rural public transportation company. ATA operates a fleet
of 25 buses that serve approximately 1,000 riders each day. The bus operation involves 10 regular
routes, plus routes for special events. The ATA employs 20 full-time drivers and 10 to 15 part-
time drivers. A dispatcher coordinates the staffing and routes and relays messages to drivers
regarding traffic information and special passenger pick-up arrangements.

Tasks
1. Identify possible actors and use cases involved in ATA’s bus operations.
Answers will vary; sample answers provide a model for students.
Actors might include Applicant, Dispatcher, Driver, and Passenger. Use cases might
include Add Driver, and Add Route. A sample use case diagram for the Add Driver use case
follows:

Name: Add Driver

Actor: Dispatcher/Driver
Description: This use case describes the process used to add a new driver assignment
Successful 1. Dispatcher adds driver to records
Completion: 2. Dispatcher assigns driver to available route
3. Dispatcher gives keys to driver
Alternative: 1. Dispatcher adds driver to records
2. Dispatcher assigns driver to substitute list
3. Dispatcher puts driver on waiting list for permanent route assignment

Pre-Condition: Applicant possesses appropriate license

Post-Condition: Driver entered in records and given assignment
Assumptions: None

2. Create a use case diagram for the bus system.

A sample use case diagram for the Add Driver and Assign Route use cases follows:
Gets
Notifies
Hired

Add Driver
Applicant Updates Dispatcher
Driver Data

Assigns
Driver

Assign Route
Systems Analysis and Design, Tenth Edition Page 11 of 42

3. Create a sequence diagram for the use case you selected.

A sample sequence diagram for the Add Driver use case follows:

Applicant Dispatcher Driver Route

Get Hired

Notify

Assign Driver

4. Create a state transition diagram that describes typical passenger states and how they change
based on specific actions and events.
A sample state transition diagram for the Add Driver use case follows:

Gets Fired

Applies Gets Quit or Retired

Hired
Prospective Current Former

Cleared to
Return
Fired
Accident or
Ticket Suspended
 Systems Analysis and Design, Tenth Edition Page 12 of 42

3 Oakwood Community College Registration

Oakwood Community College has a student registration process similar to the one at your school.
The administration asked you, as IT director, to develop a new system that would be more user-
friendly. Your first task is to create an object-oriented model of the current system. You can use
your school’s registration process as the basis for the model.

Tasks
1. List possible objects in the registration system, including their attributes and methods.
Answers will vary; sample answers provide a model for students.
Objects might include Student, Instructor, Course, Schedule, and Registration Record,
shown as follows:

Object Attributes Methods

Student Student number Add course
SSN Drop course
Name Complete course
Address Pay
Date of Birth Request transcript
Major
Credits Earned
GPA
Instructor Instructor number Teach course
SSN Advise student
Name Specify textbook
Address Serve on committee
Date of Birth
Office location
Phone
Course Course number Modify description
Course name Modify prerequisites
Credit hours Modify hours
Catalog description
Prerequisites
Schedule Term Check scheduling guidelines
Course number Notify
Course name Publish
Day/time
Instructor
Location

Registration Record Term Add course registration

Student number Drop course registration
Course number Change course registration
Grade Calculate GPA

2. Identify possible use cases and actors.

Actors might include Student, Instructor, Registrar, Advisor, and Cashier. Use cases might
include Register for Course, Process Payment, Create Course Schedule, Assign Instructor,
Print Course Roster, and Pay Tuition.
Systems Analysis and Design, Tenth Edition Page 13 of 42

3. Create a use case diagram that shows how students register.

A sample use case diagram for the Register for Course and Process Payment follows:

Adds Course

Checks
Receives Course
Fee Register for Availability
Pays Statement
Course
Registrar
Student Confirms

Receives
Payment

Process
Payment

Cashier

4. Create a state transition diagram that describes typical student states and how they change
based on specific actions and events.
A sample state transition diagram for Student states might appear as follows:

Drops Out

Admission Registers and Pays

Approved for Classes Graduates

Prospective Current Former

Probation
Removed
Disenrolled
Academic
Probation Suspended
 Systems Analysis and Design, Tenth Edition Page 14 of 42

4 Oakwood Community College Library

The library staff at Oakwood Community College works hard to satisfy students and faculty. One
of library’s main goals is to use new technology whenever possible to enhance service and
efficiency. The collection is updated constantly, and faculty members often request new books to
support current courses and research needs. Students and faculty can visit the library to use on-site
resources, including some materials that cannot be checked out. In addition, the library maintains
extensive online resources. The head librarian wants you to develop an object-oriented model for
a new library information system that would be user-friendly and cost-effective. You can use your
schools library as a model, and you are free to use your imagination. .

Tasks
1. List possible objects in the library operation, including their attributes and methods.
Objects might include Student, Instructor, book Order, and Catalog Inventory Item, which
are shown as follows:

Object Attributes Methods

Student Student number Checkout book
Name Pay late fine
Address
Method of payment
Faculty Faculty number Checkout book
Name Request book
Office location Estimate quantity needed
Phone
Book Order Order number Obtain approval
Date Send to publisher
Publisher
ISBN Add to catalog on receipt
Quantity ordered
Catalog Inventory Item ISBN Check out book to student
Title Checkout book to faculty
Quantity on hand Add text to catalog
Quantity on order Remove text from catalog
Increase quantity
Decrease quantity

2. Identify possible use cases and actors.

Use cases might include Order Book and Checkout to Student.
Actors might include Student, Faculty, library Staff, and Publisher.
Systems Analysis and Design, Tenth Edition Page 15 of 42

3. Select one of the use cases and create a sequence diagram.

A sample sequence diagram for the Faculty New Book Request use case might appear as
follows:

Faculty Head Librarian Library Catalog Order

Staff Item

Request
book Approve
book
Order Submit Order

Notify
Receive

Add to
Catalog

X
Systems Analysis and Design, Tenth Edition Page 16 of 42

4. Create an object relationship diagram that provides an overview of the system, including
how books are requested by faculty and checked out to students.
A sample object-relationship diagram might appear as follows:

Faculty
Requests
Book

Library Staff Approves book

Head librarian

Notifies

Checks Out
Adds Book

Student
Book Order

Checks Out
Adds To

Catalog Item
Systems Analysis and Design, Tenth Edition Page 17 of 42

Case Studies
Each chapter includes a Chapter Case, a Continuing Case, a Capstone Case, and an Online
Case Simulation. You can learn more about the Online Case Simulation in the MIS CourseMate
Features section.

Chapter Case: Campus Bikes

Campus Bikes is a popular bicycle shop located near a major university. The business has grown
and the owner, Mark Turner, wants to install an up-to-date computer system to handle all business
functions.

Background
Campus Bikes sells several brands of new bikes, including everything from high-end racing
models to beach cruisers. In addition to sales of new bikes and accessories, Mark’s service
department is always busy. The staff includes Mark himself, a bookkeeper, two part-time sales
reps, a full-time mechanic, and several part-time service helpers who assemble bikes.
Before opening the shop three years ago, Mark worked for many years in his father’s auto
dealership, Turner Motors, and he learned all about the automobile business. In the bike shop, he
runs a similar operation, but on a much smaller scale. For example, sales orders are recorded on
pre-printed forms, and service requests are written up just as they would be in an auto service
department.
Mark’s customers find him fair and reasonable. He likes to say that the main difference
between his business and a big-box retailer is that he knows his customers and will do whatever it
takes to keep them happy.
You work at the college as a lab assistant in the computer information department. You earned
a computer science degree at a two-year school, and you recently decided to work toward your
four-degree. The computer lab manager, Jill, often suggests that local businesses contact you for
help in troubleshooting IT issues.
This morning, you received a call from Mark, who wants to hire you as a consultant to help
plan a system for Campus Bikes. You learned that Jill had referred him, and you are excited to
have this opportunity. It probably didn’t hurt that both you and Jill had bought bikes from Mark,
and already knew him. After spending several weekends talking with Mark and the staff, you are
ready to start. You decide to use an object-oriented approach that will be easy to understand.

Tasks
1. List possible objects in the new bike shop system, including their attributes and methods.
Objects might include mechanic, sales rep, service help, and bookkeeper. Inventory objects
could include bikes and parts.

2. Identify at least three possible use cases and actors.

Use cases might include Sell bikes, Sell parts, Buy inventory, and Perform service
operations.
Systems Analysis and Design, Tenth Edition Page 18 of 42

3. Create a use case diagram that shows how service requests are handled.
Figure 6-27 on page 242 shows an excellent example of a service department at an auto
dealership. With a little imagination, students can modify this use case diagram to reflect
Mark’s operation.

4. Create a state transition diagram that describes typical customer states and how they change
based on specific actions and events.
A sample state transition diagram for Customer states might appear as follows:

Prospective
customer
Customer
visits Mark’s
makes a
site or store
purchase
Prospective Current

New order
No sales
activity in
three years
Inactive
Systems Analysis and Design, Tenth Edition Page 19 of 42

Continuing Case: Personal Trainer, Inc.

Personal Trainer, Inc. owns and operates fitness centers in a dozen Midwestern cities. The centers
have done well, and the company is planning an international expansion by opening a new
“supercenter” in the Toronto area. Personal Trainer’s president, Cassia Umi, hired an IT
consultant, Susan Park, to help develop an information system for the new facility. During the
project, Susan will work closely with Gray Lewis, who will manage the new operation.

Background
Working as an IT consultant for Personal Trainer, Susan Park used data and process modeling
tools to create a logical model of the proposed information system. Now she wants to build an
object-oriented view of the system using O-O tools and techniques. Before you perform the
following tasks, you should review the information and background in Chapters 1 and 2, and the
fact-finding summary of the case provided in Chapter 4.

Tasks
1. Identify possible actors and use cases involved in Personal Trainer’s operations.
Possible actors might include Member, Instructor, Staff, and Manager. Use cases might
include Add Member, Cancel Membership, Member Purchase, Track Usage, and Bill
Member. Sample documentation for the Bill Member use case follows:

Name: Bill Member

Actor: Member/Staff
Description: Describes the process used to bill and collect payment from members
for monthly fee at Personal Trainer
Successful 1. Staff mails member bill notification.
Completion: 2. Member pays monthly fee or fee is charged to member’s bank
account.
3. Staff updates payment on members account.
Alternative: 1. Staff mails member bill notification.
2. Member does not pay monthly fee or bank charge is rejected.
3. Staff updates members account to show suspended status.
Pre-Condition: Members monthly bill is due
Post-condition: Membership fee is paid
Assumptions: None
Systems Analysis and Design, Tenth Edition Page 20 of 42

Sample documentation for the Cancel Membership use case follows:

Name: Cancel Membership

Actor: Member/Staff
Description: Describes the process used to remove a member at Ridgewood
Successful 1. Member determines need to cancel membership
Completion: 2. Membership staff changes member state and suspends members
club privileges
3. Final bill issued
4. Membership is terminated
Alternative: 1. Staff determines need to cancel membership
2. Membership staff changes member state and suspends members
club privileges
3. Final bill issued
4. Membership is terminated
Pre- Member or staff decides to cancel membership
Condition:
Post- Membership is terminated
Condition:
Assumptions: None

Sample documentation for the Member Purchase use case follows:

Name: Member Purchase

Actor: Member/Staff
Description: Describes the process used to record and bill members for food and
beverage purchases
Successful 1. Member makes food or beverage purchase
Completion: 2. Staff records purchase and prints statement
3. Member signs statement
4. Amount in excess of remaining monthly minimum purchase is added
to members monthly statement
Alternative: None
Pre- None
Condition:
Post- Purchase is correctly recorded
Condition:
Assumptions: None
Systems Analysis and Design, Tenth Edition Page 21 of 42

2. Create an object relationship diagram for the Personal Trainer information system.
A sample object relationship diagram follows:
Systems Analysis and Design, Tenth Edition Page 22 of 42

3. Create a use case diagram for one of the use cases.

A sample use case diagram for Member Purchase, Bill Member, and Track Usage use cases
follows:

Makes
Purchase Member
Purchase Records Purchase

Updates
Updates Staff
Member
Notifies

Monitors

Bill Member

Manager
Track Usage

4. Select one of the use cases and create a state transition diagram.
A sample state transition diagram for member states follows:

Accepts
Membership Cancels Membership
Active Former
Member Member
Prospective
Member

Declines Potential
Membership Member
Systems Analysis and Design, Tenth Edition Page 23 of 42

Continuing Case: Personal Trainer, Inc. s

Background
Working as an IT consultant for Personal Trainer, Susan Park used data and process modeling
tools to create a logical model of the proposed information system. Now she wants to build an
object-oriented view of the system using O-O tools and techniques. Before you perform the
following
tasks, you should review the information and background in Chapters 1 and 2, and the
fact-finding summary of the case provided in Chapter 4.

Tasks
1. Identify possible actors and use cases involved in Personal Trainer’s operations.
Possible actors might include Member, Instructor, Staff, and Manager. Use cases might
include Add Member, Cancel Membership, Member Purchase, Track Usage, and Bill
Member.

2. Create an object relationship diagram for the Personal Trainer information system.
A sample object relationship diagram follows:

Fitness Center
Employee

Is a

Assists
Registration Member
Staff Member Manager
Services
Staff
Makes
Records
Records Monitors

Monthly
Registrations Adds To
Statement
and Purchases

Usage
Notifies
Systems Analysis and Design, Tenth Edition Page 24 of 42

3. Create a use case diagram for one of the use cases.

A sample use case diagram for Member Purchase, Bill Member, and Track Usage use cases
follows:

Makes
Purchase Member
Purchase Records Purchase

Updates
Updates Staff
Member
Notifies

Monitors

Bill Member

Manager
Track Usage

4. Select one of the use cases and create a state transition diagram.
A sample state transition diagram for member states follows:

Accepts Cancels Membership

Membership Full Former
Member Member
Prospective
Member

Declines Non-
Membership Member

Capstone Case: New Century Health Clinic c

Background
You began the systems analysis phase at New Century by completing a series of interviews,
reviewing existing reports, and observing office operations. Then, in Chapter 5, you acquired
more information and developed a set of DFDs, process descriptions, and a data dictionary. The
next step in the SDLC is to perform an object-oriented analysis of the new system. Before you
begin, go back and review the organization chart and processes list from Chapter 1, and the
diagrams data store list from Chapter 5. Then complete the following tasks.
Systems Analysis and Design, Tenth Edition Page 25 of 42

Tasks
1. Identify possible use cases and actors, and create a use case diagram for the New Century
Wellness Group system.
Use cases might include Establish New Patient, Make or Change Appointment, Remind
Patient, Provide Service, Bill Patient, Handle Insurance Claim, and Update Records.
Actors might include Patient, Provider, Medical Staff, and Office Staff.
A sample diagram for the Make or Change Appointment use case follows:

Name: Make or Change Appointment

Actor: Patient/Office Staff
Description: Describes the process used to make or change an appointment
Successful 1. Patient requests new appointment or change
Completion: 2. Office staff offers available appointments
3. Patient chooses an appointment
4. Office staff adds appointment and cancels changed appointment if needed
Alternative: 1. Patient requests new appointment or change
1. Office staff offers available appointments
2. Patient chooses not to schedule or change appointment
Pre-Condition: Patient needs to schedule or change an appointment
Post- Appointment is scheduled or changed.
Condition:
Assumptions: None

Sample documentation for the Make or Change Appointment use case follows:

Name: Update records

Actor: Office Staff/Medical Staff/Patient
Description: Describes the process of updating patient personal and medical information
Successful 1. Office staff receives updated information from patient or medical staff
Completion: 2. Office staff locates patient records
3. Office staff adds or corrects records
4. Office staff adds appointment and cancels changed appointment if needed
Alternative: None
Pre-Condition: Change occurs in patient’s information
Post- Patient records updated to reflect change
Condition:
Assumptions: Established patient
Systems Analysis and Design, Tenth Edition Page 26 of 42

Sample documentation for the Remind Patient use case follows:

Name: Remind Patient
Actor: Patient/Office Staff
Description: Describes the process used to remind a patient of an appointment
Successful 1. Office staff identifies following week’s appointments
Completion: 2. Office staff prints reminder postcards
3. Office staff mails postcards and calls patients two days before appointment

Alternative: None
Pre-Condition: Patient has scheduled appointment during the following week
Post- Patient receives reminder postcard and reminder calls
Condition:
Assumptions: Patient has valid mailing address and phone number

Sample documentation for the Establish New Patient use case follows:
Name: Establish New Patient
Actor: Patient/Office Staff
Description: Describes the process used to set up new patient records
Successful 1. Office staff provides patient with medical history and insurance billing forms
Completion: 2. Patient returns completed forms
3. Office staff creates a patient file
4. Office staff adds patient to current list

Alternative: 1. Office staff provides patient with medical history and insurance billing forms
2. Patient does not complete forms
3. No file is created

Pre-Condition: Patient requests medical services

Post- Patient file is created
Condition:
Assumptions: Providers are taking new patients

Sample documentation for the Submit Insurance Claim follows:

Name: Submit Insurance Claim
Actor: Office Staff/Insurance Carrier
Description: Describes the process to submit an insurance claim for covered services
Successful 1. Office staff verifies patient insurance carrier and policy number information
Completion: 2. Office staff prepares claim based on medical codes for services provided
Office staff submits claim to insurance carrier

Alternative: None
Pre-Condition: Patient has provided evidence of coverage and policy number
Post- Claim submitted with identification number
Condition:
Assumptions: Patient has insurance
 Systems Analysis and Design, Tenth Edition Page 27 of 42

Sample documentation for the Bill Patient use case follows:

Name: Bill Patient

Actor: Office Staff
Description: Describes the process to bill a patient for services
Successful 1. Office staff deducts insurance payments and calculates balance due
Completion: 2. Office staff updates patient records
Office staff produces and prints bill and mails to patient
Alternative: None
Pre-Condition: Patient has balance due
Post- Bill is prepared and sent
Condition:
Assumptions: None

A sample use case diagram for Make or Change Appointments and Remind Patient follows:

Requests
Appointment
Checks Appointment
Confirms Availability
Make or Change
Appointment
Patient Office Staff

Initiates Reminder
Notifies

Remind Patient
 Systems Analysis and Design, Tenth Edition Page 28 of 42

A sample use case diagram for Establish New Patient and Update Patient Records follows:

Provides Patient Establishes New

Information
Office Staff

Establish
New Patient
Patient Changes
Updates Existing Provides
Medical
Information

Update Records

Medical Staff

A sample use case diagram for Bill Patient and Submit Insurance Claim follows:

Request
Submits Bill
Bill Office Staff
Patient Patient
Updates
Requests

Files Claim

Submit Insurance Pays or Denies Claim

Claim
Insurance
Company
Systems Analysis and Design, Tenth Edition Page 29 of 42

2. Select one of the use cases and create a class diagram.

A sample class diagram for the Make or Change Appointment use case follows:

Requests
Office Staff Appointment Patient
Name
Name Address
Position 0..* 0..*
Phone
DOB
Sex
Schedule Appointment SSN
Confirm Appointment Insurance
Remind
Change Appointment Make New
Check Availability 0..* Appointment
Change Appointment

1..*
Appointment Medical Staff
Patient Name Name
Provider Name Position
Appointment Date Hours
Appointment Time
0..* 0..*
Type of Appointment Notifies
Clear Schedule
Block Dates
Add
Delete
Verify
Print
Systems Analysis and Design, Tenth Edition Page 30 of 42

3. Create a sequence diagram for the use case that you selected.
A sample sequence diagram for the Make or Change Appointment and Remind Patient use
case follows:

Patient Office Staff Appointments Remind

Requests
Appointment Check Availability

Offers Available

Schedules Notifies
Selects
Request Reminder

Reminds

x
A sample sequence diagram for the Bill Patient and Submit Insurance Claim use case
follows:

Patient Billing Staff Insurance Company

File Insurance Claim

Response
Bill Patient

Payment
Systems Analysis and Design, Tenth Edition Page 31 of 42

4. Create a state transition diagram that describes typical patient states and how they change
based on specific actions and events.
Sample Patient State Transition Diagram:

Patient chooses
another practice

Request first Accepted by

appointment provider, supplies
needed information
Patient Dies
Prospective Current Former

Patient completes
treatment
Systems Analysis and Design, Tenth Edition Page 32 of 42

CASE Tool Workshop s

Background
In the previous chapter, you created a data and process model for a new business venture. You
plan to operate a mobile auto detailing service that will visit customers at their homes or
businesses, and offer traditional, high-quality hand washing and waxing. In addition to retail
customers, several auto dealers have expressed interest in your services, and you are eager to get
started. You will hire college students as technicians, train and supply them, and offer them a
share of the profits as an incentive.
Your friend, who is an IT major, offered to help you set up an information system by
customizing several Microsoft Office applications to meet your needs. In addition to the data and
process model you created, she recommended that you prepare an object model. She suggested
that you focus on the main actors and events, and that it was OK to use your imagination.
Thinking it over, you know that you will have employees, retail customers, auto dealer accounts,
one or more suppliers, and your local bank, where you plan to set up a business checking account.
You also plan to keep track of customers, employee information, profit-sharing data, and an
operations log.

Tasks
1. List possible objects in the new business, including their attributes and methods, and create a
use case diagram that shows how an on-site service request would be handled.
Some possible objects, attributes, and methods might include:

OBJECT ATTRIBUTES METHODS

CUSTOMER Name Makes service request
Contact information Has vehicle ready on schedule
Type of vehicle Pays for service
Location of vehicle
AUTO DEALER Name Makes service request
Contact information Has vehicle ready on schedule
Location of dealership Pays for service
TECHNICIAN Name Is available per schedule
Personnel info Performs service tasks
Availability Receives pay
Performance appraisal
SERVICE REQUEST Date Is created upon customer
Location request
Type of vehicle Is paid by customer
Type of service
Technician assigned
Amount
Systems Analysis and Design, Tenth Edition Page 33 of 42

A sample use case diagram might look like this:

Customer

Maintains service log

Requests
Service

Scheduler
Determine Schedule
Requests
Service
Receives
Auto Dealer Receives Schedule
Roster

Trains

Evaluates
ins Performs
Tasks Employee

Deliver Services Receives

Manager Reports
Systems Analysis and Design, Tenth Edition Page 34 of 42

2. Create a sequence diagram that models the on-site service request mentioned in Task 1.
A sample sequence diagram for the Make or Change Appointment and Remind Patient use
case follows:

Customer Scheduler Service Request Technician

Requestr
Requests
Service Check Availability

Makes vehicle Check Schedule

available

Creates
Pays for Service Performs Tasks

x
Systems Analysis and Design, Tenth Edition Page 35 of 42

MIS CourseMate Features

If your students have MIS CourseMate access codes, you can reinforce and extend their learning
with premium content created for this textbook. For example, you can launch interactive Video
Learning Sessions to help you understand systems development concepts and practice your
skills. In addition, you can use MindTap Reader, which is a full, interactive, digital e-book.

Online Case Simulation: SCR Associates

Session 6: Object Modeling

Preview
In the last session, you used data and process modeling techniques to develop a logical model of
the new system. Now you will apply your object modeling skills to create various diagrams and
documentation for the new TIMS system. You will review the background material and develop
an object-oriented model that includes several types of diagrams.

Tasks
1. I need to review Jesse’s e-mail message regarding object modeling and the JAD session
summary. I need to identify possible use cases and actors, and create a use case diagram for
the TIMS system.
Possible use cases might include Student Payment, Register, Request Course, Teach Course,
Determine Schedule, and Maintain Training Records. Possible actors might include
Student, Instructor, Training Administrator, and Corporate Client. A sample use case
diagram for Determine Schedule, Register, and Prepare Training Report follows:
Systems Analysis and Design, Tenth Edition Page 36 of 42

2. She wants me to create a model of the use case that shows how students register. She also
wants to see a class diagram.
A sample class diagram for the Register use case follows:

Student Registration Record

Student number
Name 0..* 0..* Student number
Address Course number
Registers Payment method
SSN
Tuition due

Request course
Add course
Determine tuition
Complete course
Prepare roster
Drop course
Confirm
Change student data

Includes 1..*
1..*

Instructor Course
Instructor ID Course number
Name Course name
Courses qualifications Instructor
Teaches Day/Time
Location
Phone 1 1..*
Add Course
Teach course Change Course
Report outcome Delete Course

Updates Training Record

Student number
Course number
Date
Completion data

Output to SCR staff

Output to student
Output to corporate client
Systems Analysis and Design, Tenth Edition Page 37 of 42

3. I need to create a sample registration sequence diagram that shows the steps in the
registration process.
Sample Registration Sequence Diagram:

Student Registration Courses Instructor

Requests
Course Checks
Availability
Confirms
Available
Bill Schedules

Payment Confirms

Bills
Notifies

4. Jesse asked me to create a state transition diagram that describes typical student states and
how they change based on certain actions and events. She said to include a brief cover
memo.
Possible use cases might include Student Payment, Register, Request Course, Teach Course,
Determine Schedule, and Maintain Training Records. Possible actors might include
Student, Instructor, Training Administrator, and Corporate Client. A sample use case
diagram for Determine Schedule, Register, and Prepare Training Report follows:
Systems Analysis and Design, Tenth Edition Page 38 of 42

Critical Thinking Challenge

Background
The IT team at Game Technology prepared DFDs for the new C3 system. You will help the team
develop a set of object models. The C3 system model will include use cases that represent various
business processes. The customer and sales rep entities will be actors, with these methods:

Entity Methods
Customer  Request product information
 Place order
 Respond to Web promotion
 Sign up on game blog
Sales Rep  Initiate sales call to customer
 Respond to customer inquiry
 Follow up after prior order
 Follow up after prior information request

You also learned that customer categories are based on specific conditions, as shown:
Category Conditions
Potential Has not placed an order in the last 24 months, but has responded to a Web
promotion or requested product information or signed up on our game blog
Active Has placed at least one order in the last 24 months
Preferred Has placed at least three orders in the last 24 months
Former An Active or Preferred customer with no orders in the last 24 months

Practice Tasks and Answers

1. Draw a use case diagram that includes the entities and the use cases.
Systems Analysis and Design, Tenth Edition Page 39 of 42

2. Draw a state transition diagram that shows the customer categories and the conditions for each
category.
Systems Analysis and Design, Tenth Edition Page 40 of 42

Challenge Tasks and Answers

After you complete the Practice Tasks, you learn about new developments at Game Technology.
The marketing group added a new data analyst position to provide IT support. The new person
will track customer response times, prepare contact management plans for sales reps, and develop
customer satisfaction surveys. Marketing also decided to update customer categories. The
Potential and Former categories are not affected. The new categories are Silver, which replaces
the Active category; Gold, which replaces the Preferred category; and Platinum, which includes
any customer whose orders total at least $1,000 in the last 24 months.

1. Draw a new version of the use case diagram that adds the new marketing technician.
Systems Analysis and Design, Tenth Edition Page 41 of 42

2. Draw a state transition diagram that shows the new customer categories and the conditions
for each category.
Systems Analysis and Design, Tenth Edition Page 42 of 42

Video Learning Sessions

Note: The textbook includes 18 Video Learning Sessions and an introductory session to help
students become familiar with this feature. In Chapters 2, 3, 4, 5, 6, 7, 9, and 11, students assist
the IT Training Director by creating a preview to boost interest in the VLS for that chapter. In the
role of a training assistant, the student must be perceptive, creative, and an effective
communicator.
Chapters 1, 8, 10, and 12 do not align with a specific VLS, so students are asked to help
create a new VLS for that chapter. Still in the role of a training assistant, the student is asked to
describe the specific skills and concepts to be covered, explain how the material would be
presented, and describe at least three graphic images to be included in the session.

Practice Tasks (Your Turn)

Students should perform these tasks after watching each VLS to practice their skills and check the
sample answers. For convenient reference, a full set of Your Turn tasks and solutions is included
in the Additional Activities for Students section of the Instructor materials.

Training Tasks
These tasks might seem quite simple, but they actually require metacognition, which can be
described as “knowing what you know.” Students need to step back and provide an overview of
the session and why it is important, and then select a specific segment that does a “good job” of
explaining a skill or concept. To do that, the student must evaluate the topics, and choose one that
is effective, in his or her view. The topic is not important, and answers will vary.
The real issue is the student’s ability to grasp the objective of the training and come up with
effective ways to explain key points and concepts. Those skills will be extremely valuable in the
workplace.