TASK 2 :

CASE STUDY: CUSTOMER SUPPORTING SYSTEM (Online Book store)

Aim: Identify and analyze events

Procedure:

Generally event is specification of a significances occurrence that has a location in time & space .The Flow of
events of a usecase contains the most important information derived from usecase modeling work.it should describe the
usecases flow of events clearly enough for an outsider to easily understand it.Remember flow of events should present
what the system does,not how the system is design to perform the required behavior.

Guidelines for the contents of the flow of events are,

1)Describe how the usecase starts and ends.

2)Describe what data is exchanged between the actor and the usecase

3)Do not describe the details of the user interface,unless it is necessary to understand the behavior of the system.

b) Aim: Identify use cases:

Use case description for online book store: in these we have

Login: here we will our credentials and login to the online book store.

Browser catalog: here user can browse his required book according to his need such as amount ,author, version etc.….

Order book: after selecting the book can order the book on checking the option “buy now’.

Manage account: here we will have the option of online payment through our account were it will manage our account
details like sending OTPS checking balance ect.

Ship book: after the payment of money to the book, the book is shipped to our address in various steps.this is managed by
the system.

Manage catalog: in this the admin will check and analyze the details of shipping books.

UNIFIED MODELING LAB Page 9

WWW.KVRSOFTWARES.BLOGSPOT.COM
Login Login

Search books
Search book
books

Browse catalog
Browse catalog

Order book
Order book

Manage account
Manage account

Ship book
Ship book

Manage catalog
Manage catalog

UNIFIED MODELING LAB Page 10

WWW.KVRSOFTWARES.BLOGSPOT.COM
c) Aim: Draw Event table

Event table:

Event Actor Description Object

Login Customer Here we will open the web page and login
by using our credentials we can login
to the website of the online book store.
Search Customer In search books the users will search book
book books according to their requirements
Browser customer The user can browser his required book
catalog book according to their needs such as
author, amount ,version
Order Customer After selecting the book the customer book
book can order the book on clicking the
commands such as “buy new”(or)”add
to cart”
Manage customer Here we will have the option of cash account
account on delivery (or) online payment .if we
choose online payment through our
account ,it will manage our account
details like sending OTP,checking
balance etc.
Ship system After the payment of money to the books
book book which the customer had selected
,the book is shipped to the customer
address in various steps. This is
managed by system
Manage Administrator In managing catalog the administrator books
catalog will check and analyse the details of
shipping books like weather the
correct book is being delivered (or)not

UNIFIED MODELING LAB Page 11

WWW.KVRSOFTWARES.BLOGSPOT.COM
d) Aim: Identify and analyze domain classes:

Customer seller address

address
customer Seller
Street:string
name:string N ame:
City:string
id:string string
State:string
password:int Address:
Country:string
address:string string
Pincode:int
Orderbooks() U rl:int
Searchtitle() Check
Fill the order availability()
form() Confirm()
Give
catalog()
Send
details()
Give order
Login form() logout

Logout
confirm
Login
Customerid:string
Id:address

Mode of payment

Book Mode of
payment
Book Creditcardno:int
Title: Checkno:int
string Pay by cash()
Author: Pay through
string money order()
Publisher:
string

UNIFIED MODELING LAB Page 12

WWW.KVRSOFTWARES.BLOGSPOT.COM
 orderform

order form
Customer: string
Tax:int
Paymentmode:int
Deliveryfee:int
Totalbill:int
Dateoforder:int

e)Aim:Represent usecases and domain class diagram using rational rose

usecase diagram

UNIFIED MODELING LAB Page 13

WWW.KVRSOFTWARES.BLOGSPOT.COM
->Class diagram:

f) Aim: Develop CRUD matrix to represent relationship between use cases and problem domain classes

Entity/funct custom log addre logo sell ord bo Mode

ion er in ss ut er er ok of
payme
nt
Inventory C,R
Create C,R,D C C C,U
order
Bookcatalog R C R
Login C,R C,R
Manageme R C C C,R
nt payment
Order status R C C

Result: The Design was successfully completed.

UNIFIED MODELING LAB Page 14

WWW.KVRSOFTWARES.BLOGSPOT.COM