Scribd
Upload
50 views

Use Case Diagram

Uploaded by

Rajesh Madathil
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
50 views

Use Case Diagram

Uploaded by

Rajesh Madathil
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Use Case Diagram

Case Study 1:
Software Protection and Licensing
Sentinel License Development Kit (Sentinel LDK) is a Software Digital Rights
Management (DRM) solution by SafeNet Inc. that delivers strong copy protection,
protection for Intellectual Property (IP), and secure and flexible licensing. Sentinel
LDK separates licensing and production processes (implemented with Sentinel
EMS) from the software protection process (implemented with Sentinel Licensing
API or Sentinel LDK Envelope).
Sentinel EMS is a web-based graphical application provided as part of Sentinel
LDK that is used to perform a range of functions required to manage the licensing,
production, distribution, customer support, and maintenance of protected
applications. This application is a role-based application designed to manage the
business activities required to implement and maintain Sentinel LDK in the
organization which needs to protect its software. Sentinel EMS Server maintains a
database containing a wide range of information, including data related to product
features, licenses, sales, orders, and customers.
Use case diagram below shows some simplified view of software licensing use
cases supported by Sentinel EMS Application (shown as «Application»
stereotyped subject). The Sentinel EMS handles three major workflows:
license planning,
order processing and production, and
activation of trial software.
Software licensing with Sentinel EMS application UML use case diagram example.
Product Manager defines Features and Products. Each Product has one or more
Features. After Features and Products have been defined in Sentinel EMS,
entitlements can be processed and produced using the Production group of
functions.
Users assigned the Development role can fulfil one of the following development-
related activities:
 Generate bundles of Provisional (Trial) Products
 Generate a customized Sentinel LDK Run-time Environment (RTE) installer
file
 Customize the Sentinel Remote Update System utility (RUS utility)
Entitlement Manager defines and manages customers, and also enters and manages
entitlements. An entitlement is the execution of a customer order for Sentinel LDK
items, and can be either an order for Products to be supplied with one or more
Sentinel protection keys, or a Protection Key Update that specifies changes to be
made to the license terms and/or data stored in Sentinel protection keys that have
already been deployed.
Customer Services role can manage customers the same way as Entitlement
Manager does, and can also manage Product activation.
For entitlements that generate Product Keys, the customer receives an email from
Sentinel EMS that contains the keys. The customer is able to log in to the EMS
Customer Portal using the Product Key in order to activate the Product.

Case Study 2:
Hospital Management System
Hospital Management System is a large system including several subsystems or
modules providing variety of functions. UML use case diagram example below
shows actor and use cases for a hospital's reception.
Purpose: Describe major services (functionality) provided by a hospital's reception.
Hospital Reception subsystem or module supports some of the many job duties of
hospital receptionist. Receptionist schedules patient's appointments and admission
to the hospital, collects information from patient upon patient's arrival and/or by
phone. For the patient that will stay in the hospital ("inpatient") she or he should
have a bed allotted in a ward. Receptionists might also receive patient's payments,
record them in a database and provide receipts, file insurance claims and medical
reports.
Case Study 3:
Online Shopping
Web Customer actor uses some web site to make purchases online. Top level use
cases are View Items, Make Purchase and Client Register. View Items use case
could be used by customer as top level use case if customer only wants to find and
see some products. This use case could also be used as a part of Make Purchase use
case. Client Register use case allows customer to register on the web site, for
example to get some coupons or be invited to private sales. Note,
that Checkout use case is included use case not available by itself - checkout is part
of making purchase.
Except for the Web Customer actor there are several other actors which will be
described below with detailed use cases.

Online shopping UML use case diagram example - top level use cases.
View Items use case is extended by several optional use cases - customer may
search for items, browse catalog, view items recommended for him/her, add items
to shopping cart or wish list. All these use cases are extending use cases because
they provide some optional functions allowing customer to find item.
Customer Authentication use case is included in View Recommended
Items and Add to Wish List because both require the customer to be authenticated.
At the same time, item could be added to the shopping cart without user
authentication.

Online shopping UML use case diagram example - view items use case.
Checkout use case includes several required uses cases. Web customer should be
authenticated. It could be done through user login page, user authentication cookie
("Remember me") or Single Sign-On (SSO). Web site authentication service is
used in all these use cases, while SSO also requires participation of external
identity provider.
Checkout use case also includes Payment use case which could be done either by
using credit card and external credit payment service or with PayPal.

You might also like