Creating a Use Case
Creating a Use Case
Jennifer LeClair
CIS 510
Instructor Name: Dr. Austin Umezurike
10/27/2016
Assignment 2:
Creating a Use Case
Introduction
With this paper I will show how a use case diagram should be used. I base this paper from fig. 3
– 11 pages 78 – 80 in our textbook titled: System Analysis and Design in a Changing World, 6th
edition, by Satzinger, Jackson, and Burd. In the Use Case Diagram that I make, I will depict a
use case for a RMO CSMS subsystem. I will also be describing the overview of the diagram. I
will also provide an analysis of the characters.
Use Case Introduction
An activity that a system performs is known as a use case. It is mostly in response to the
user. Use case analysis is a technique that is used for identifying the functional requirements of
the software system. A use case is to designate the point of view from a client and customer, this
is a use cases main purpose. An analytical role in the development process is done by the
developer. The other definition of a use case is as an objective or as an actor. Actors are with a
particular system and they want to achieve. In the use case diagram that I create, I will show the
actors and use cases for the RMO CSMS subsystem for marketing.
Marketing Subsystem
RMO CSMS
Marketing Merchandising
Overview
The overview of this use case diagram has the following: It shows the system boundary,
the association and the actors. The one that does the interaction with the system by entering or
receiving data is called a group, actor, external agent or person. Another part of the whole system
are the system boundaries. System boundaries are the computerized part of the application along
with the users who operate it. When a customer places a relationship between certain things such
as a certain employee in a department and an order, this would be a logical association. In my
diagram I have included two actors, one is representing marketing and the other represents
merchandising.
Analysis
The events and actions that define the interactions with a system and the role in order to
be able to discover a goal is a list of actions or steps in an event in a use case. The elements that
make up a use case diagram and the connections that are between a use case and the actors is an
association. This lets us know that there is communication between the actors and the use case.
On the marketing side they need to be able to update / add promotions, production and business
partners. On the merchandising side they need to be able to update / add production information
and accessory packages.
Summary
The important part of a use case diagram is that you can identify the users so that your
diagram has the ability to make communication with other users, and management. My use case
diagram showed a way to analyze a subsystem for a CSMS market.
Reference
Satzinger, J., Jackson, R., & Burd, S. (2012). Systems Analysis and Design in a Changing World (6th Ed.). Cambridge, Ma: Course Technology.
Miles, R., Hamilton, K. (2006). Learning UML 2.0: A Pragmatic Introduction to UML (1st Ed). Sebastopol, CA. O’Reily Media.
Use Case of Standards Development. (2016). Journal of AHIMA, 87(1), 24 – 29.
5
Add and Update
Product Information
Add and Update
Promotion
Add and Update
Accessory Package
Add and Update
Add and Update Product Information Add and Update Promotion Add and Update Accessory Package Add and Update