USECASE DIAGRAM:

Airport Check-In and Security Screening

This is an example of a business use case diagram.
Primary actors are Passenger, Tour Guide, Minor (Child), Passenger with Special Needs (e.g.
with disabilities), all playing  roles in relation to airport business.
Use cases are Individual Check-In, Group Check-In (for groups of tourists), Security Screening,
etc. - representing business functions or processes taking place in airport and serving the needs of
passengers.
Business use cases Baggage Check-in and Baggage Handling extend Check-In use cases,
because passenger might have no luggage, so baggage check-in and handling are optional.

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 - Credit Cards Processing
Primary actor for the system is a Merchant’s Credit Card Processing System. The merchant
submits some credit card transaction request to the credit card payment gateway on behalf of a
customer. Bank which issued customer's credit card is actor which could approve or reject the
transaction. If transaction is approved, funds will be transferred to merchant's bank account.
Authorize and Capture use case is the most common type of credit card transaction. The
requested amount of money should be first authorized by Customer's Credit Card Bank, and if
approved, is further submitted for settlement. During the settlement funds approved for the credit
card transaction are deposited into the Merchant's Bank account.
In some cases, only authorization is requested and the transaction will not be sent for
settlement. In this case, usually if no further action is taken within some number of days, the
authorization expires. Merchants can submit this request if they want to verify the availability of
funds on the customer’s credit card, if item is not currently in stock, or if merchant wants to
review orders before shipping.
Capture (request to capture funds that were previously authorized) use case describes several
scenarios when merchant needs to complete some previously authorized transaction - either
submitted through the payment gateway or requested without using the system, e.g. using voice
authorization
Credit use case describes situations when customer should receive a refund for a transaction that
was either successfully processed and settled through the system or for some transaction that was
not originally submitted through the payment gateway.
Void use case describes cases when it is needed to cancel one or several related transactions that
were not yet settled. If possible, the transactions will not be sent for settlement. If the Void
transaction fails, the original transaction is likely already settled.
Verify use case describes zero or small amount verification transactions which could also
include verification of some client's data such as address.
You can find excellent resources, documentation, white papers, guides, etc. related to the credit
card processing at Authorize.Net - Payment Gateway to Accept Online Payments.

Hospital Management
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.

Online Library Public Access Catalog

An Online Public Access Catalog (OPAC) is an e-Library website which is part of Integrated
Library System (ILS), also known as a Library Management System (LMS), and managed by
a library or group of libraries.
Patrons of the library can search library catalog online to locate various resources - books,
periodicals, audio and visual materials, or other items under control of the library. Patrons may
reserve or renew item, provide feedback, and manage their account.
Activity Diagrams
Online Shopping
Online customer can browse or search items, view specific item, add it to shopping cart, view
and update shopping cart, checkout. User can view shopping cart at anytime. Checkout is
assumed to include user registration and login.

Ticket Vending Machine

This is an example of UML activity diagram describing behavior of the Purchase Ticket use
case.
Activity is started by Commuter actor who needs to buy a ticket. Ticket vending machine will
request trip information from Commuter. This information will include number and type of
tickets, e.g. whether it is a monthly pass, one way or round ticket, route number, destination or
zone number, etc.
Based on the provided trip info ticket vending machine will calculate payment due and request
payment options. Those options include payment by cash, or by credit or debit card. If payment
by card was selected by Commuter, another actor, Bank will participate in the activity by
authorizing the payment.
Resolve Software Issue
An example of UML activity diagram which shows how to resolve an issue in a software
design. After ticket is created by some authority and the issue is reproduced, issue is identified,
resolution is determined, issue is fixed and verified, and ticket is closed, if issue was resolved.
Document Management Process
An example of UML activity diagram describing a Document Management Process. Some
kind of formal and properly communicated document management process is usually required in
any major corporation especially under a regulatory compliance.
A document goes through different state or stages - it is created, reviewed, updated, approved,
and at some point archived. Different roles participating in this process
are Author, Reviewer, Approver, and Owner. These roles are represented on the diagram
by partitions rendered as horizontal "swimlanes".
Sentinel HASP SL - Activation of Trial Product
An example of activity diagram describing manual activation of trial (provisional) product
which was protected by Sentinel HASP SL software key of the Sentinel HASP - software
protection and licensing security solution.
Sentinel HASP protects against losses from software piracy and intellectual property theft. For
example, it offers industry-leading support for licensing in virtual environments, and is the first
software licensing and reverse engineering protection tool solution on the market to support
J2EE applications.
Sentinel HASP software includes Business Studio - a powerful, role-based software licensing
and management tool. The Business Studio is used by product, marketing and development staff
to prepare software product for market and includes all of the tools necessary to license and lock
application to a Sentinel HASP HL hardware or HASP SL software product key, to manage and
track licenses, to create product keys that are later used for the product activation process, etc.
Three activity partitions are shown on the diagram as vertical swimlanes and
represent actors participating in the activity - Order Management, Customer Service,
and Customer.
Customer has some trial product installed, for example, some game or tool, which has specific
trial period and could have some limited features or options. After using the product for some
time customer decides to activate product by requesting a permanent, full product license.
Order Manager will have to create a new activation key for the product while the customer could
create and deliver C2V file ("computer fingerprint"). Once both the new product key and the
C2V file become available to the customer service, it could activate product, generate V2C file
and deliver it back to the customer.
The customer applies license received and thus activates installed trial product to become a full
product. The product could be protected from copying to other computers or virtual machines by
the HASP SL license and protection key.
State Machine
Water Phases
Water can exist in several states - liquid, vapor, solid, and plasma. Several transitions are
possible from one state to another. For example, freezing is phase change from liquid state to ice.
Condensation is phase change from vapor state to liquid. Water vapor could turn directly into
frost through deposition.

Bank ATM
ATM is initially turned off. After the power is turned on, ATM performs startup action and
enters Self Test state. If the test fails, ATM goes into Out of Service state, otherwise there
is triggerless transition to the Idle state. In this state ATM waits for customer interaction.
The ATM state changes from Idle to Serving Customer when the customer inserts banking or
credit card in the ATM's card reader. On entering the Serving Customer state, the entry
action readCard is performed. Note, that transition from Serving Customer state back to
the Idle state could be triggered by cancel event as the customer could cancel transaction at any
time. Serving Customer state is a composite state with sequential substates Customer
Authentication, Selecting Transaction and Transaction. Customer
Authentication and Transaction are composite states by themselves which is shown with
hidden decomposition indicator icon. Serving Customer state has triggerless transition back to
the Idle state after transaction is finished. The state also has exit action ejectCard which releases
customer's card on leaving the state, no matter what caused the transition out of the state.
Online Shopping - User Account
Every company having customers maintains customer accounts and supports a complete life
cycle of the account from its creation until it is closed. There are differences in what are the
stages (states) in the account's life cycle, and what are conditions or events causing account to
change its state.
Here we provide an example of user account life cycle in the context of online shopping, shown
as UML protocol state machine diagram.
For the user account to be created, it has to meet some initial requirements. For example, user id
(used as a login name) must be unique, at least for the existing accounts. After account was
created, it might need to be verified. Verification depends on the company and could include e-
mail, phone, and/or address verification. If account was not verified during some predefined
period of time, that account could be moved to the suspended accounts.
New, active, or suspended accounts could be cancelled at any time by client's request. Note, the
precondition for this usually includes payment of any outstanding balances, and might require
some separate account state or substate to handle this case.
User account might be suspended for security reasons, manually or automatically. For example,
website intrusion detection system locks user account for predefined period of time, if there were
several unsuccessful login attempts using incorrect account password. After account lock times
out, account is activated back automatically.
Some user accounts could be inactive for a long period of time. Company policy or business
rules could require moving such dormant for a year or two accounts to the suspended state.
Once we listed user account states and specified all possible transitions from one state to another,
we can review the diagram with other subject matter experts to see if anything is missing or
needs further clarifications.

Library Management System

1:available :- the book is available in library and can be issued to member.
2:issued to member: Book is with member and is not available in library
State chart diagram contain following states.
states are librarian are :
1)Validate member
2)Issuing book
3)returning book
4)checking availability of book
5)calculating fine
6)idle
Component Diagram
Online Shopping
An example of UML 2.5 component diagram for online shopping. The diagram shows "white-
box" view of the internal structure of three related subsystems - WebStore, Warehouses, and
Accounting. In UML «Subsystem» is a standard component stereotype for larger components,
usually containing some smaller components.
WebStore subsystem contains three components related to online shopping - Search
Engine, Shopping Cart, and Authentication. Search Engine component allows to search or
browse items by exposing provided interface Product Search and uses required
interface Search Inventory provided by Inventory component. Shopping Cart component
uses Manage Orders interface provided by Orders component during
checkout. Authentication component allows customers to create account, login, or logout
and binds customer to some account.
Accounting subsystem provides two interfaces - Manage Orders and Manage
Customers. Delegation connectors link these external contracts of the subsystem to the
realization of the contracts by Orders and Customers components.
Warehouses subsystem provides two interfaces Search Inventory and Manage Inventory used
by other subsystems and wired through dependencies.
University management system

Hospital Management System

School Registration System
Class Diagram
College Management System

Library Management System:

UML Class diagram for library management system contains classes such as
1.Book class
2.librarian class
3. Transaction class
4.Member record class
5.Bill class

Each class contains various attributes and methods(Functions) which call other class attributes to
share data.
1.Book Class contains attributes such as author,book name,price status,rack no,edition.
and functions such as display book details,update status.
2.librarian class contains attributes such as name,password and functions such as search
book,issue book,calculate fine,calculate bill.
3.transaction class contains attributes such as transaction id,member id bill id date of issue etc.
and functions such as create transaction delete transaction
4.Member record class contains attributes such as member id,type,date of issue,no of books,etc.
and functions such as increase book issue, decrease book issue,pay bill.
5.Bill class contains attributes such as bill no,date,member,amount and functions such as create
bill,update bill.
Online Shopping:
Each customer has unique id and is linked to exactly one account. Account owns shopping cart
and orders. Customer could register as a web user to be able to buy items online. Customer is not
required to be a web user because purchases could also be made by phone or by ordering from
catalogues. Web user has login name which also serves as unique id. Web user could be in
several states - new, active, temporary blocked, or banned, and be linked to a shopping cart.
Shopping cart belongs to account. Account owns customer orders. Customer may have no orders.
Customer orders are sorted and unique. Each order could refer to several payments, possibly
none. Every payment has unique id and is related to exactly one account.
Each order has current order status. Both order and shopping cart have line items linked to a
specific product. Each line item is related to exactly one product. A product could be associated
to many line items or no item at all.
ATM System: