LAB MANUAL

UNIFIED MODELING LANGUAGE

(UML)
 B.Tech. (CSE)

UNIFIED MODELING LANGUAGE (UML) LAB

The student is expected to take up about five mini-projects and model them and produce - both
static & dynamic aspects of the model, using Rational Products i.e Rational Software Architect

Mini-Project - I: A Point-of-Sale (POS) System

A retail POS system typically includes a computer, monitor, keyboard, barcode scanners, weight scale,
receipt printer, credit card processing system, etc. and POS terminal software. It interfaces to various
service applications, such as a third-party tax calculator and inventory control. These systems must be
relatively fault tolerant; that is, even if remote services are temporarily unavailable they must still be of
capturing sales and handling at least cash payments. A POS system must support multiple and varied
client-side terminals and interfaces such as browser, PDAs, touch-screens.

Mini-Project - II: Online Shopping

Customer uses some web site to make purchases online. Follow the various websites like
snapdeal,flipkart,amazon.in so as to design an online shopping.

Mini-Project - III: E-Library OPAC

An Online Public Access Catalog (OPAC) is 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. Members 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. Members may
reserve or renew the resources.

Mini-Project - IV: A Multi-Threaded Airport Simulation

Simulate the operations in an airport. Your application should support multiple aircrafts using several
runways and gates avoiding collisions/conflicts. Landing: an aircraft uses the runway, lands, and then
taxis over to the terminal. Take-Off: an aircraft taxies to the runway and then takes off

Mini-Project -V: Bank ATM

An automated teller machine (ATM) or the automatic banking machine (ABM) is banking subsystem that
provides bank customers with access to financial transactions in a public space without the need for a
cashier, clerk or bank teller. Customer uses bank ATM to check balances of his/her bank
accounts, depositfunds, withdrawcash and/or transferfunds .ATMTechnician provides maintenance and
repairs.
Mini-Project -VI: Hospital Management System

Hospital Management System is a large system including several subsystems or modules

providing variety of functions. Hospital 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.

Mini-Project-VII: An Auction Application

Several commerce models exist and are the basis for a number of companies like eBay.com,
pricellne.com etc. Design and implement an auction application that provides auctioning
services. It should clearly model the various auctioneers, the bidding process, auctioning etc.

Mini-Project -VIII: A Notes and File Management System

In the course of one's student years and professional career one produces a lot of personal notes
and documents. All these documents are usually kept on papers or individual files on the
computer. Either way the bulk of the information is often erased corrupted and eventually lost.
The goal of this project is to build a distributed software application that addresses the problem.
The system will provide an interface to create, organize and manage personal notes through the
Internet for multiple users. The system will also allow users to collaborate by assigning
permissions for multiple users to view and edit notes.

Mini-Project - IX: Credit Card Processing System

Credit Card Processing System (Credit Card Payment Gateway) is a system under consideration.
Main part of the system is the Merchant’s Credit Card Processing System. The merchant submits
a credit card transaction request to the credit card payment gateway on behalf of a customer.
Bank which issued customer's credit card which could approve or reject the transaction. If
transaction is approved, funds will be transferred to merchant's bank account.

Mini-Project - X: Airport Check-In and Security Screening

Passenger, Tour Guide, Minor (Child), Passenger with Special Needs (e.g. with disabilities),
involved in relation to airport business. Individual Check-In, Group Check-In (for groups of
tourists), Security Screening, etc. – representing process taking place in airport and serving the
needs of passengers.
Text Book(s):

1. "Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design

and the Unified Process", Craig Larman, Pearson Education Asia, 2002, 2ndEdition.

Reference(s):

1. "Object Oriented Systems Analysis and Design using UML", Simon Sennet, Steve
McRobb, and Ray Farmer, McGraw Hill, 2002, 2ndEdition
2. "Object-Oriented Analysis & Design," Andrew Haigh, Tata McGraw Hill, 2001

Various Net Resources and Projects:

http://user-mode-linux.sourceforge.net/case-studies.html
http://www.onesmartclick.com/programming/case-studies.html
http://www.tigris.org/sarvlets/ProjectList?type=P rejects
http://hotscripts.com/
http://www.developingwebs.net/
http://sourceforge.net/projects/
http://governing.com/gpp/gponline.htm
http://www.cio.com/research/government/gov.html
http://www.whitehouse.gov/omb/inforeg/egovstrategy.pdf
http://www.andhrapradesh.com/
http://www.ap-lt.com/
http://www.aponline.gov.in

INTRODUCTION

The development of UML began in late 1994 when Grady Booch and Jim Rumbaugh of Rational Software
Corporation began their work on unifying the Booch and OMT (Object Modeling Technique) methods. In
the Fall of 1995, Ivar Jacobson and his Objectory company joined Rational and this unification effort,
merging in the OOSE (Object-Oriented Software Engineering) method.1

As the primary authors of the Booch, OMT, and OOSE methods, Grady Booch, Jim Rumbaugh, and Ivar
Jacobson were motivated to create a unified modeling language for three reasons. First, these methods
were already evolving toward each other independently. It made sense to continue that evolution together
rather than apart, eliminating the potential for any unnecessary and gratuitous differences that would
further confuse users. Second, by unifying the semantics and notation, they could bring some stability to
the object-oriented marketplace, allowing projects to settle on one mature modeling language and letting
tool builders focus on delivering more useful features. Third, they expected that their collaboration would
yield improvements in all three earlier methods, helping them to capture lessons learned and to address
problems that none of their methods previously handled well.1
The efforts of Booch, Rumbaugh, and Jacobson resulted in the release of the UML 0.9 and 0.91
documents in June and October of 1996. During 1996, the UML authors invited and received feedback
from the general community. They incorporated this feedback, but it was clear that additional focused
attention was still required.1

While Rational was bringing UML together, efforts were being made on achieving the broader goal of an
industry standard modeling language. In early 1995, Ivar Jacobson (then Chief Technology Officer of
Objectory) and Richard Soley (then Chief Technology Officer of OMG) decided to push harder to achieve
standardization in the methods marketplace. In June 1995, an OMG-hosted meeting of all major
methodologists (or their representatives) resulted in the first worldwide agreement to seek methodology
standards, under the aegis of the OMG process.1

During 1996, it became clear that several organizations saw UML as strategic to their business. A
Request for Proposal (RFP) issued by the Object Management Group (OMG) provided the catalyst for
these organizations to join forces around producing a joint RFP response. Rational established the UML
Partners consortium with several organizations willing to dedicate resources to work toward a strong UML
1.0 definition. Those contributing most to the UML 1.0 definition included: Digital Equipment Corp., HP, i-
Logix, IntelliCorp, IBM, ICON Computing, MCI Systemhouse, Microsoft, Oracle, Rational Software, TI,
and Unisys. This collaboration produced UML 1.0, a modeling language that was well defined,
expressive, powerful, and generally applicable. This was submitted to the OMG in January 1997 as an
initial RFP response.1

In January 1997 IBM, ObjecTime, Platinum Technology, Ptech, Taskon, Reich Technologies and Softeam
also submitted separate RFP responses to the OMG. These companies joined the UML partners to
contribute their ideas, and together the partners produced the revised UML 1.1 response. The focus of
the UML 1.1 release was to improve the clarity of the UML 1.0 semantics and to incorporate contributions
from the new partners. It was submitted to the OMG for their consideration and adopted in the fall of
1997.1
 A POINT OF SALE SYSTEM
A POS System is a computerized application used to record sales and handle payments.It is
typically used in a retail store.It includes hardware components such as a computer and
bar code scanner and software to run the system. It interfaces to various service
applications such as a third party tax calculator and inventory control.It allows users to just
view the products available and buy them if they like. Here three levels of users are defined
in this system. Customers can enter into the system and view and buy the products.
Cashier is the one who is responsible for selling the products.Manager has access to all the
users of the system and is responsible for creating users or deleting user accounts and

1.1 Use Case Scenario:

A use case diagram describes event sequences for an actor to use the system.It is a
anarrative description of process.A use case is normally actor or event based.An actor will
begin a process or an event will happen that the system must respond to.

Use Case Diagram:

 Search Product

Buy Product

Customer
Billing

Bar Code Scanning

Tax Calculation
Cashier

Manager
InventoryControl

Manage Employees

Place Order

Use case of Manager:

Search Product

InventoryControl
Manager

Manage Employees

Place Order

Use case of Cashier:

 Search Product

Buy Product

Billing
Cashier

Bar Code Scanning

Tax Calculation

INTERACTION DIAGRAM:

A sequence diagrams depicts the sequence of actions that occur in a system.It captures the
invocation of methods in each object and order in which invocation occurs.It is used to
represent the behavior of a system.

Sequence diagram:

Description for sale sequence:

 Customer first enters into shop.

 Searches for required product
 Takes the product to cashier
 Then cashier scans it and calculates tax
 Cashier generates bill for products
 Customer pays the bill
 Takes the product and leaves
 Products Inventory Bar Code Tax
Scanner Calculator
: Customer : Cashier

1: search for the products

2: get product details

3: display details

4: confirm buy

5: scans the bar code

6: calculates tax

7: bill details

8: pays bill

9: updates stock

10: gives product and receipt

Collaboration Diagram:
 4: confirm buy
8: pays the bill

10: take product and receipt

: Customer : Cashier
1: search for the products

Products 9: updates the stock

3: display details
2: get product details

7: bill details 5: scans the bar code

Inventory

Tax Bar Code

Calculator Scanner
6: calculates the tax

Class Diagram:

The Class diagram shows the building blocks of an object oriented system.They are used to
illustrate relationships between classes and interfaces.It depicts the static view of the model
describing what attributes and behavior it has.
State Chart Diagram:

State chart diagram is a powerful tool for specifying the dynamic behavior of reactive
objects.The response of reactive object depends on what state the object is in at the time
that the event occurred.
Description for sale sequence:

 Customer searches for required product

 Prepares the list of items he/she wants to buy
 Pays the bill

if not
Search product found Prepare
item list

search for product

calculate get bill confirm buy continue

tax get bill shopping

leave the shop

generate Pay
bill take products

Activity Diagram:

Description for sale sequence:

 Customer searches for required product

 Prepares the list of items he/she wants to buy
 Pays the bill
 enter the
shop

search for
product
search for
if not
product
search for product found getproduct
product details

continue
shopping
get bill
calculate generate get bill pay bill
confirm buy
tax bill

no

1.6 Component Diagram:

A Component diagram shows the components in the system and their dependencies.Any
physical module is represented by a component.
 cashier. productinfo search. pay.class
class .class class
products.
db
displaydet viewdetails
ails.class scanbarco
.class
de.class
manager.
customer.
class
class
Control Database
Point of transaction
getdetails. System
sale s.db
class
scan.class
proinfo.
class
sell.class buy.class caltax.clas
getproduct Users.db
info.class s
billing. transaction
class .class

1.7 Deployment Diagram:

This system needs a server ,database to store the data,a point of sale component and some
terminals like customers.

customer1

Point Of Sale server database

customer2

Online Shopping
Online shopping is a computer based system allowing users anywhere around the world to
just view the products available and buy them if they like. Here three levels of users are
defined in this system. Customers can enter into the system and view the products.To gain
full access they should login and only such users will have privilege to buy products. Seller
is the one who is responsible for selling the products. Here they allow customers to pay bill
through secure online payment basis. Admin has access to all the users of the system and is
responsible for creating users or deleting users accounts.

Use Case Scenario:

A use case diagram describes event sequences for an actor to use the system. It is a
narrative description of process. A use case is normally actor or event based. An actor will
begin a process or an event will happen that the system must respond to.

Use Case Diagram:

Search for product

Add to cart

Customer Login

Payment

Connect to bank Seller

Order Status
Admin

Shipping

Manage Inventory

Add/remove users

Use case of Customer:

 Search for product

Add to cart

Customer Login

Payment

Connect to bank

Order Status

Use case of Seller:

Search for product

Login

Seller Connect to bank

Order Status

Shipping

INTERACTION DIAGRAM:
Sequence diagram:

Description for sale sequence:

 Customer first searches for required product

 Places an order and adds to cart.
 To add to the cart, he/she should login into the system.
 Buys it by making a secure connection with bank
 Checks order status

create order book inventory add to cart login register pay bill bank database
Customer buy
catalog
seller

1: create order

2: search

3: available
4: add to cart

5: loginrequest

6: login

7: validate

8: fail

9: registerrequest

10: register

11: validate

12: success

13: logged in successfully

14: buy a book

15: shipment details

16: payment details

17: confirm buy

18: pay bill

19: enter bank details

20: validate

21: success

22: update inventory

23: ship book

Collaboration Diagram:
 2: search 3: available
create book
order inventory
catalog
1: create order

add to 4: add to cart

cart
8: fail
6: login 11: success
login

Customer 10: validate

databas
12: buy a book 9: register 5: loginrequest
e
register
7: validate
15: confirm buy

buy
20: update inventory 18: validate
16: pay bill 21: ship book
13: shipment details 19: success

pay bill
bank
14: payment details 17: enter bank details

seller

Class Diagram:
The Class diagram shows the building blocks of an object oriented system.T hey are used to
illustrate relationships between classes and interfaces. It depicts the static view of the
model describing what attributes and behavior it has.

State Chart Diagram:

State chart diagram is a powerful tool for specifying the dynamic behavior of reactive
objects.The response of reactive object depends on what state the object is in at the time
that the event occurred.

Description for sale sequence:

 Customer searches for required product

 On finding,adds it the cart
 For that he has to login into the system
 After getting logged in, he’ll buy it through online basis
 After paying for the product, the seller will ship the product.

validate

found book
search getbook addtocart login
info

valid
invalid

validate bankdeta pay

ils

valid

ship

Activity Diagram:

Description for sale sequence:

  Customer searches for required product
 On finding it, adds it the cart
 For that he has to login into the system
 After getting logged in, he’ll buy it through online basis
 After paying for the product, the seller will ship the product.

search for
product

found required book

if not

add to cart

loginstatus
valid
invalid

login register

invalid validate

valid
yes

logged in continue
successfully shopping

no

display bill yes confirm

details buying

no
invalid
pay bill enter bank validate
details

valid

ship book

Component Diagram:

A Component diagram shows the components in the system and their dependancies.Any
physical module is represented by a component.
 bank.class shipping.cl
ass buy.class
login.class
payment.cl users.db
ass
cart.class
sellers.
class

database
register. online book Transaction producs.db
class store

prodetails.
class users.clas
s account.
transaction
shipping.cl class
.db
ass
books.
payment. sell.class class
class

Deployment Diagram:

This system needs a server to carry out operations of a product store, a bank server to
carry out the bank transactions,database to store the data,a product store component and
some terminals like customers

customer1
bank
server

online central
book store server

customer2 database

E-Library OPAC
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.
Let us just have an overview of the Library Management System (LMS):
 Librarian lends books and magazines
 Librarian maintains the list of all the members of library
 Borrower makes reservation online
 Borrower can remove reservation online
 Librarian issues books to the borrower
 Librarian calculates dues to be paid by the borrower
 Borrower issues/returns books and/or magazines
 Librarian places order about the requirements to the master librarian
 Librarian updates system
 Master librarian maintains librarians

TEXTUAL ANALYSIS
(a) ACTORS
i. Librarian
ii. Borrower
iii. Catalog
iv. Master Librarian
Librarian:
1. Manages and validates members
2. View reports from the system
3. Issues books
4. Calculates dues
5. Takes books
6.
7. Places orders to the master librarian
8. Maintains list of books and magazine
USECASE DIAGRAM:
 Use case diagram is created to visualize the interaction of our system with the outside
world. The components of use case diagram are:

Use Case: Scenarios of the system

Actor: Someone or something who is interacting with the system
Relationship: Semantic link between use case and actor.

ACTIVITY DIAGRAM:

Activity diagram shows the flow of events within our system.

The components are:

a) Start State
b) End State
c) Transition
d) Decision Box
e) Synchronization Bar
f) Swim Lane
INTERACTION DIAGRAM:

An interaction diagram models the dynamic aspects of the system by showing the
relationship among the objects and messages they may dispatch. There are two types of
interaction diagrams:
SEQUENCE DIAGRAM:
Sequence diagram shows the step to step what mush happen to accomplish a piece
of functionality provided by the system. The components are:

a) Actor
b) Object
c) Messages
d) Lifeline
e) Focus of Control

COLLABORATION DIAGRAM:
Collaboration diagram displays object interactions organized around objects and their links to
one another. The components are:
a) Actor
b) Object
 c) Link

CLASS DIAGRAM:

Class diagram shows structure of the software system. The class diagram shows a set of
classes, interfaces and their relationships. The components are:

a) Class
b) Relationship:
The forms of relationship are:

1. Association
2. Aggregation
3. Generalization
4. Composition
5. Dependency
STATE CHART DIAGRAM:
State chart diagram show a life cycle of a single class. The state is a condition where the
object may be in. The components are:
a) Start state
b) End state
c) State
d) Transition

Member: Librarian:
Library Administrator:

A Multi-Threaded Airport Simulation

A multi threaded airport simulation is a computerized application used to simulate the
operations in an airport system.It should support multiple aircrafts using several runways
and terminals.It should be able to send/receive signals.On receiving a signal,if aircraft is to
be landed it allots a free runway.If the next departure of the aircraft is after a long time,it
sends a signal to park the aircraft by assigning a free terminal that is suitable to the
aircraft. Here five levels of users are defined in this system. Pilots who send/receive signal
to land/takeoff the aircraft. Head is the one who is responsible for allotting a free
runway/terminal whenever it receives a signal to land an aircraft.Aircraft Controller is
responsible for finding a free runway/terminal.Terminal Controller is the one who sends a
signal whenever it finds a free terminal.Runway Controller is the one who sends a signal
whenever it finds a free runway.

Use Case Scenario:

send/receive signal

runway availability

Runway controller
Update runway status

Air traffic controller

send/rceive runway number

Heads
check free terminals

Update terminal status

Pilots

send/receive terminal
number
Terminal Controller

land/park aircraft

manage employees

Use case of Head:

 send/receive signal

send/rceive runway number

Heads
send/receive terminal
number

manage employees

Use case of Pilots:

send/receive signal

send/rceive runway number

Pilots

send/receive terminal
number

land/park aircraft

Use case of Terminal Controller:

 check free terminals

Update terminal status

Terminal Controller

send/receive terminal
number

Use case of Air Traffic Controller:

send/receive signal

send/rceive runway number

Air traffic controller

send/receive terminal
number

INTERACTION DIAGRAM:

A sequence diagrams depicts the sequence of actions that occur in a system.It captures the
invocation of methods in each object and order in which invocation occurs.It is used to
represent the behavior of a system.

Description for land/take-off aircraft:

 Pilot first sends a signal either to takeoff or land aircraft.

 Head checks for weather condition
 Head sends a signal to aircraft controller
 Air craft controller checks if there is any free runway if aircraft is to be landed and
sends it
 Else it checks for a free terminal and sends a signal
 Pilot takes off/lands aircraft depending on signal

4.3.1 Sequence diagram:

 runway terminal weather
pilot head air traffic runway controller terminal
controller controller

1: sends signal

2: checks weather condition

3: checks

4: sends weather report

5: asks for free runway

6: check availabilty
7: checks

8: found a free runway

9: send runway no

10: update status

11: send runway no

12: lands aircraft if next dept time

13: else asks for free terminal

14: asks for free terminal

15: checks availablity

16: checks for free terminal

17: found a free terminal

18: send terminal no

19: update status

20: send terminal no

21: park aircraft

Collaboration Diagram:
 3: checks
1: sends signal
13: else asks for free terminal 2: checks weather condition
weather

4: sends weather report

head
pilot

21: park aircraft

11: send runway no

20: send terminal no 12: lands aircraft if next dept time
5: asks for free runway
14: asks for free terminal

terminal
runway

air traffic controller 7: checks

10: update status
16: checks for free terminal
15: checks availablity 19: update status
6: check availabilty

9: send runway no 8: found a free runway

18: send terminal no 17: found a free terminal

runway controller terminal controller

Class Diagram:

The Class diagram shows the building blocks of an object oriented system.They are used to
illustrate relationships between classes and interfaces.It depicts the static view of the model
describing what attributes and behavior it has.
State Chart Diagram:

State chart diagram is a powerful tool for specifying the dynamic behavior of reactive
objects.The response of reactive object depends on what state the object is in at the time
that the event occurred.

Description for land/take-off aircraft:

 Pilot sends a signal to land

 Head checks for free runway
 If aircraft leaves immediately,it sends a free runway signal.
 Else it sends a free terminal number
 Pilot then lands/parks the aircraft
 send land aircraft check leaves free
signal weather if ok immnediately runway
updates status
no

update
signal to update terminal free terminal found free runway status
park status terminal
assigns free terminal assigns free runway

signal to
land

Activity Diagram:

Description for land/take-off aircraft:

 Pilot sends a signal to land

 Head checks for free runway
 If aircraft leaves immediately,it sends a free runway signal.
 Else it sends a free terminal number
 Pilot then lands/parks the aircraft
 pilot sends
signal

check
weather cond

land
assign
takes off runway
immediately
take off no

yes any aircraft ready check for head checks

to takeoff free terminal
runway status

no
sends runway
assign free number
terminal

send signal update update runway

to take off terminal status status

send signal
to land

Component Diagram:

A Component diagram shows the components in the system and their dependencies.Any
physical module is represented by a component.
 employees freetermin
al.class land.class
getterminal .class
.class
aircrafts.db

land.class send.class

central runway.db
takeoff.cla aircraft database
ss simulation

receive.
class freerunway employees
.class .db
take.class
pilots.class
weather.cl getrunway. getstatus.
ass class class

Deployment Diagram:

This system needs a server to carry out operations of a airport,database to store the data,a
airport simulation component and some terminals like heads and a pilot.

head1

airport
pilot server database
simulation

head2
 Bank ATM
Introduction:

ATM system needs enhancement to record card information electronically is

automatically displays the details in the card. The ATM will communicate with the bank
computer over an appropriate communication link. The ATM will serve one customer at a time.
A customer will be required to insert an ATM card and enter a PIN number both of which will be
sent to bank for valuation as a part of each transaction. The customer will then be able to perform
one or more transactions. The card will be retained in the machine until the customer indicates
that he/she desires no further transactions, at which point it will be returned.

Withdraw usecase diagram :-

+sselecting cash

+mode of payment

+Enter Amount

+User asked for amount +selecting

Controller ATM
User

+various methods of payment

Withdraw cash usecase diagram :-

+cash is provide from system +updating database

ATM Database
user

Withdraw sequence diagram :-

Withdraw cash sequence diagram :-

user ATM database

1: cash is provided from system

2: updating database

Withdraw collaboration:-
2: enter the amount 4: select mode of payment
Withdraw cash collaboration :-
user

1: cash is provided from the system

2: updating database
ATM database

Withdraw class diagram :-

Withdraw cash class diagram:-

State Transition diagram :

start login valid user

logged on

invalid login
relogin transition

withdrawl

logout updation
transaction completed

stop

Component Diagram :-

Login local
Controller bank

Login user

account
info and

Perform Transaction
Transaction Manager

Deployment Diagram :-
Hospital Management System
Hospital Management System is a large system including several subsystems or modules
providing variety of functions. Hospital 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.

USE CASE DIAGRAM

Class Diagram:
Activity Diagram:
Sequence Diagram
Collaboration diagram
Deployment DIAGRAM

An Auction Application
An Auction Application is a computer based system allowing users anywhere around the
world to search for the products available, to bid and buy them if they like. Here two levels
of users are defined in this system. Customers (bidders) can enter into the system and
search for the products and to bid them. To gain full access they should login and only such
users will have privilege to bid the products. Auctioneer is the one who is responsible for
auction process and delivering the product.

Use Case Scenario:

A use case diagram describes event sequences for an actor to use the system. It is
a narrative description of process. A use case is normally actor or event based. An
actor will begin a process or an event will happen that the system must respond to.

Use Case Diagram

sign up/login

search for product

request/send details

bidder
bid the product
auctioner

buy the product

sell the product

pay the price

deliver the product

Use case of Bidder:

 sign up/login

search for product

request/send details

bidder
bid the product

buy the product

pay the price

Use case of auctioner :

sign up/login

request/send details

auctioner

sell the product

deliver the product

SYSTEM DESIGN

Class Diagram:
The Class diagram shows the building blocks of an object oriented system. They are used to
illustrate relationships between classes and interfaces. It depicts the static view of the
model describing what attributes and behavior it has.

INTERACTION DIAGRAM:

Sequence Diagram:
A sequence diagrams depicts the sequence of actions that occur in a system. It captures the
invocation of methods in each object and order in which invocation occurs. It is used to
represent the behavior of a system.

Description for auction sequence:

 Bidder first signup/login to the site.

 He/she searches for the required product. If it is not available he/she will request the
product.
 If found he/she will bid the product and pay the price if satisfied.
 Auctioneer will accept the bidder request and delivers the product

login bidder search for productinfo request bid the buy sell delivery
products product product
: bidder : auctioner
1: enter details

2: authenticate

3: wrong password

4: valid user

5: search for products

6: product not found

7: display product details

8: request for the product

9: accept the request

10: bid the product

11: pay the price

12: accept the payment

13: deliver the product

Collaboration Diagram:
 3: wrong password

1: enter details login 2: authenticate

bidder 13: deliver the product

sell deliver product
4: valid ... y
: bidder info

5: search for products

7: display product details
6: product not found 8: request for the product

12: accept the payment

request
search for product
products
9: accept the request

10: bid the product

bid the
: auctioner buy product
11: pay the price

State Chart Diagram:

State chart diagram is a powerful tool for specifying the dynamic behavior of reactive
objects. The response of reactive object depends on what state the object is in at the time
that the event occurred.

Description for auction sequence:

 Bidder first signup/login to the site.

 He/she searches for the required product. If it is not available he/she will request the
product.
 If found he/she will bid the product and pay the price if satisfied.
 Product not found

Enter details
sign Enter product details search for
in/signup the product

product found

buy the bid the

product pay the price product

accept the delivery

Activity Diagram:

Activity diagrams describe the workflow behavior of a system. They are similar to state
diagrams because activities are the state of doing something. They describe the state of
activities by showing the sequence of activities performed. They show activities that are
conditional or parallel. They are used for analyzing a use case by describing what actions
need to take place and when they should occur.
 Enter details

Sign
in/sign up

authenticate Reenter
details

Enter product details

search for
product

productfound? no search for

other product
yes

bid the
product

Pay the price

Buy the
product

Accept the payment

Sell the
product

deliver the
product

Component Diagram:

A Component diagram shows the components in the system and their dependencies. Any
physical module is represented by a component.
 Bidder.class productinfo.cl
ass
user.db

auctioner.cla java.awt database

ss auction
application

product.db
site.class

Deployment Diagram:

Deployment and diagrams are used to model the physical aspects of an object oriented
system.It shows the configuration of runtime processing nodes components.

database

Produ user
bidder central ct
s server

update
list

A Notes and File Management System

File management system is computer based application where in a course of one’s students years and
professional career one produces a lot of professional documents and all these documents are kept
usually on papers or individual files on computers. Either way bulk of the information is often erased
corrupted or eventually lost. The goal of this project is to build a distributed software application that
addresses this problem.

Use Case Scenario:

A use case diagram describes event sequences for an actor to use the system. It is
a narrative description of process. A use case is normally actor or event based. An
actor will begin a process or an event will happen that the system must respond to.

Use Case Diagram

login

search

admin
faculty data
student

student data

faculty modify

delete

internal operations

USE CASE FOR FMS

SYSTEM DESIGN

Class Diagram:

The Class diagram shows the building blocks of an object oriented system. They are used to
illustrate relationships between classes and interfaces. It depicts the static view of the
model describing what attributes and behavior it has.
INTERACTION DIAGRAM:

Sequence Diagram:

A sequence diagrams depicts the sequence of actions that occur in a system. It captures the
invocation of methods in each object and order in which invocation occurs. It is used to
represent the behavior of a system.

Description for faculty sequence:

 faculty first signup/login to the site.

 He/she searches for the required file. If it is not available he/she will request the
particular file.
 If found he/she will modify if needed.
 Internal operations are done if necessary
 login details search files deletions internal
: faculty modification
s operations
1: login details

2: any error

3: error status is sent

4: fac searches files

5: modifies if necessary

6: deletes if necessary

7: performs int operations if necessary

8: if required file is not found

9: failure msg is sent

SEQUENCE FOR FACULTY

Description for student sequence:

 student first signup/login to the site.

 He/she searches for the required file. If it is not available he/she will request the
particular file.
 If found he/she will modify if needed.
 Internal operations are done if necessary
 login details search files deletions internal
modification
: student operations
s

1: login details are givan

2: any error occurs

3: error status is sent

4: stu searches files

5: modifies if necessary

6: deletes if necessary

7: performs int operations if necessary

8: if required file is not found

9: failure msg is sent

SEQUENCE FOR STUDENT

Collaboration Diagram:

2: any error 8: if required file is not found

4: fac searches files 5: modifies if necessary

login search modificati
details files ons
9: failure msg is sent

7: performs int operations if necessary

3: error status is sent

1: login details 6: deletes if necessary

internal
deletion operations
s

: faculty

COLLABORATION FOR FACULTY

 2: any error

1: login details
login
details
3: error status is sent
: admin
7: verifies or modifies fac data
6: error is reported
9: error is reported
5: any error
8: any error
4: verifies or modifies stu data

student
faculty
data
data

COLLABORATION FOR ADMIN

State Chart Diagram:

State chart diagram is a powerful tool for specifying the dynamic behavior of reactive
objects. The response of reactive object depends on what state the object is in at the time
that the event occurred.

Description:

 user first signup/login to the site.

 He/she searches for the required product. If it is not available he/she will request the
product.
 If needed user modifies the data

key word for data to be searched is given data to be modified is entered

user search modifications
login the files if needed

file name to be deleted is given

internal operations deletions done

done if needed if needed
save,edit etc operations are given

STATE CHART DIAGRAM

Activity Diagram:
Activity diagrams describe the workflow behavior of a system. They are similar to state
diagrams because activities are the state of doing something. They describe the state of
activities by showing the sequence of activities performed. They show activities that are
conditional or parallel. They are used for analyzing a use case by describing what actions
need to take place and when they should occur.

login details

no
valid
yes
no search for
the files yes
no
search found serach not
found
yes
exit any
no application
yes
search again
no
modificatio deletions
ns

int operations
done if needed

want to exit

ACTIVITY DIAGRAM

Component Diagram:
A Component diagram shows the components in the system and their dependencies. Any
physical module is represented by a component.

save.class
edit.class open.class
add.class

internal
Operations
facultyData
delete .db
search
modify
databas studentDat
e a.db
fms server

COMPONENT DIAGRAM

Deployment Diagram:

Deployment and diagrams are used to model the physical aspects of an object oriented
system.It shows the configuration of runtime processing nodes components.

FMS SERVER

Terminal Database System

DEPLOYMENT DIAGRAM
 Credit Card Processing System

Airport Check-In and Security

Screening
Passenger, Tour Guide, Minor (Child), Passenger with Special Needs (e.g. with disabilities),
involved in relation to airport business. Individual Check-In, Group Check-In (for groups of
tourists), Security Screening, etc. – representing process taking place in airport and serving the
needs of passengers.

USE CASE DIAGRAM

CLASS DIAGRAM
SEQUENCE DIAGRAM

COLLABORATION DIAGRAM
STATE CHART
DEPLOYMENT DIAGRAM

COMPONENT DIAGRAM