Contents: Page No

Object Oriented Modeling and Design
ONLINE SHOPPING CART

SYSTEM
CONTENTS :
Page No.
1. SCOPE
1.1 AUDIENCE
1.2 ORGANISATION
1.3 APPLICABLE DOCUMENTS
2. SOFTWARE REQUIREMENT SPECIFICATION
3. FUNCTIONAL MODEL
4. ACTIVITY DIAGRAM
5. USE CASE DIAGRAM
11
6. INTERACTION DIAGRAM
6.1.1
SEQUENCE DIAGRAM
19
6.1.2
COLLABORATION DIAGRAM
23
7. STATE CHART DIAGRAM
26
8. CLASS DIAGRAM
28
9. IMPLEMENTATION DIAGRAM
RGIT, MUMBAI.
9.1 COMPONENT DIAGRAM
29
9.2 DEPLOYMENT DIAGRAM
31
Page 1
Department of MCA.

SYSTEM
1. Scope :
The following subsections describe the scope of the fast food outlet system in
terms of its audience, organization, and applicable documents
1.1 Audience :
Customers, Administrators, Sellers.
1.2 Organization :
ONLINE SHOPPING CART SYSTEM
1.3 Applicable Documents :
The following documents provide information necessary to understand this
documentation:
RGIT, MUMBAI.
Page 2
Department of MCA.

SYSTEM
2 Software Requirement Specification:

System Abstract
The Online Shopping Cart system facilitates the Customer to view the Items
Products, inquire about the item details, availability of seats and many more. The major
functionality of system is to allow the user to book and cancels the flights as per user
requirements. It also provides the administrator or manager to modify existing flights or
to introduce a new flights in the schedule.
Major features provided by the system are :
1. Customer
The system allows the user or member to perform flight qnuiry including flight
scheduling, seats availability status, fare details, etc.
2. Administrator
It allows the customer to register in order to give the services to its member .
3. Online shopping system
The system allows the member to order the product as per his/her requirements. The
customer is prompt to enter the customer details and credit card details. The member
then receives the unique cart number .
4.
Product Listing
This process gives the details about the purchasing process made by the customer at
the details of the shipping and taxes involved with the cost
5.
Administrator
The administrator module of the system allows the admin/manager to manage the
products item It provides the admin /manger to modify or change the existing items or to
introduce a new items. Apart from modifying the category it also allow the
admin/manager to take the taxes and include the shipping charges along with the h/w s/w
and service requirements.
RGIT, MUMBAI.
Page 3
Department of MCA.

SYSTEM
3. Functional Model.
Context Level / Level 0
Customer
Admin detail
places order
Gives the
shopping cart to
place the i tems
Administrator
Online
Shopping
System
Gives the
services
Fig 3.1 Data Flow Diagram for Online Shopping Cart Software
RGIT, MUMBAI.
Page 4
Department of MCA.

SYSTEM
LEVEL 1
Product Listing
Login Info
Customer
Lo
gi
n/
Pa
ss
w
or
d
Request f or
Registeration
R egistration
Login
1.1
User
Verification
User Login
Request
for
products
Product Product Product

Id
item
Id
listing
1.3
1.2
Product LIst
Master
Product Detail
Purchase
Process
Product
Purchased
1.4
Shipping Info
Pay
Process
Pay
1.5
Pending
Product
Data
Pending
Product Data
Product
Shipping
1.6
1.7
Shipping
Data
Registration
Shipping
Charges
User
registration
Fig 3.2 Data Flow Diagram for Product Listing
RGIT, MUMBAI.
Page 5
Department of MCA.

SYSTEM
LEVEL 2
Administrator
Login/
Password
Login
2.1
Admin
Verification
Home
Shipping
Pending
Data
Shipping
Pending
Add
Category
2.5
Add
Product
Master
Product
Home
2.2
Shipping
Pending
Order
2.3
Update
Category
2.6
Delete
Category
2.7
Delete
Product
Edit
Product
Master
Product
Order
Details
Master
Product
Order
Detail
2.4
Add
Shipping
Charges
2.8
Add
Shipping
Order
Detail
Add
Tax
2.9
Add
Shipping
Charges
Add
Item
2.10
Pending
Order
2.11
Pending
Data
Edit
Pending
Order
Tax
Add New H /W
Manage
Software
Team
2.12
Add
Add S /W
Add New
S/W
Add
new
services
Manage
Hardware
Team
2.13
Add
Add H/W
Manage
Service
Team
2.14
Add
Add
Service
Fig 2.3
Fig : 3.3Data Flow Diagram for Administrator.
RGIT, MUMBAI.
Page 6
Department of MCA.

SYSTEM
LEVEL 3
Payment Info
Customer
Payment made through credit

cards
Payment made on
Delivery
Final calculate amount displayed on

the items purchased
Secure
Gateway
Provider
3.1
Gives the Payment

details of
Authorized
Customers
Customer
Payment
System
3.2
Customer Info
Fig
Fig: Data Flow Diagram for Secure Gateway Provider.
RGIT, MUMBAI.
Page 7
Department of MCA.

SYSTEM
4. Activity Diagram.
An Activity diagram is a visual representation of any system's activities and flows of data
or decisions between activities.
Activity diagrams provide a very broad view of a business process.
They represent the dynamics of a system.
They are flow charts that are used to show the work flow of a system.
They show the flow of control from activity to activity in the system.
They show what activities can be done in parallel, and any alternative paths through the
flow.
Purpose
Model business workflows
Model operations
Activity diagrams commonly contain
Activity states and action states
Transitions
Objects
Action States and Activity States

Action states are atomic and cannot be decomposed

Work of the action state is not interrupted.
Activity states can be further decomposed
Their activity being represented by other activity diagrams
They may be interrupted
Represented in UML by a rounded rectangle.
Activity represents the performance of some behavior in the work flow.
Transitions
Transitions are used to show the passing of the flow of control from activity to activity.
They are typically triggered by the completion of the behavior in the originating activity.
When the action or activity of a state completes, flow of control passes immediately to
the next action or activity state
RGIT, MUMBAI.
Page 8
Department of MCA.

SYSTEM
A flow of control has to start and end at some place

initial state -- a solid ball
stop state -- a solid ball inside a circle
Branching
When modeling the workflow of a system, it is often necessary to show where the
flow of control branches based on a decision point.
The transition from a decision point contain a guard condition.

The guard condition is used to determine which path from the decision point is taken.
Decisions along with their guard conditions allow you to show alternative paths
through a work flow.
A branch specifies alternate paths taken based on some Boolean expression
A branch may have one incoming transition and two or more outgoing ones
Synchronization Bars
In a workflow there are typically some activities that may be done in parallel.
A synchronization bar allows you to specify what activities may be done
concurrently.
A synchronization bar may have
many incoming transition and one outgoing transition, or
one incoming transition and many outgoing transitions.
It is use to specify the forking and joining of parallel flows of control
A synchronization bar is rendered as a thick horizontal or vertical line
A fork may have one incoming transitions and two or more outgoing transitions
each transition represents an independent flow of control
conceptually, the activities of each of outgoing transitions are concurrent
either truly concurrent (multiple nodes)
or sequential yet interleaved (one node)
RGIT, MUMBAI.
Page 9
Department of MCA.

SYSTEM
A join may have two or more incoming transitions and one outgoing transition
above the join, the activities associated with each of these paths continues in
parallel
at the join, the concurrent flows synchronize
each waits until all incoming flows have reached the join, at which point one
flow of control continues on below the join
RGIT, MUMBAI.
Page 10
Department of MCA.

SYSTEM
Fig 4.1 Activity Diagram :

customer
view the
product
want to purchase?
no
yes
Item not found
visit faq
no
product avilable in india?

yes
go through the
product details
Login
yes
are u member?
no
Register
shopping cart is
assigned to customer
item get added

to shopping cart
no
confirm the shopp...
yes
generate purchase
details
do you want to cancel the product?

yes
Cancel
Product
no
payment
details
payment on
delivery
no
paying by creditcard?
yes
getway system
activated
no
varification of customer?
yes
yes
want to purchase?
no
final bill
want to fill feedback?
no
yes
Fill feedback
signout
RGIT, MUMBAI.
Page 11
Department of MCA.

SYSTEM
5. Use-Case Diagram.
The use-case concept was introduced by Ivar Jacobson in the object-oriented software
engineering (OOSE) method.
A use-case diagram is a graph of actors, a set of use cases enclosed by a system boundary,
communication (participation) associations between the actors and the use cases, and
generalization among the cases.
Use case diagrams show how users interact with the system.
Use case diagrams describe what a system does from the standpoint of an external observer.
The emphasis is on what a system does rather than how.
Use case diagrams are closely connected to scenarios. A scenario is an example of what
happens when someone interacts with the system. Here is a scenario for a medical clinic.
"A patient calls the clinic to make an appointment for a yearly checkup. The receptionist
finds the nearest empty time slot in the appointment book and schedules the appointment
for that time slot. "

Used during requirements elicitation to represent external behavior

Actors represent roles, that is, a type of user of the system
Use cases represent a sequence of interaction for a type of functionality
The use case model is the set of all use cases. It is a complete description of the functionality
of the system and its environment
Actors
An actor models an external entity which communicates with the system:
o User
o External system
o Physical environment
An actor has a unique name and an optional description.
Customer
Examples:
Passenger: A person in the train
GPS satellite: Provides the system with GPS coordinates
Use Cases
A use case represents a class of functionality provided by the system as an event flow.
A use case consists of:

Unique name
Participating actors
Pre-conditions
Entry conditions (triggers)
Flow of events
Exit conditions (success guarantees)
Special requirements
RGIT, MUMBAI.
Page 12
Item Purchased
Department of MCA.

SYSTEM
The Use Case diagram for whole system is as shown in fig 5.3
The <<extend>> Relationship

<<extend>> relationships represent exceptional or seldom invoked cases.

The exceptional event flows are factored out of the main event flow for clarity.
Use cases representing exceptional flows can extend more than one use case.
The direction of a <<extend>> relationship is to the extended use case
The <<include>> Relationship

An <<include>> relationship represents behavior that is factored out of the use case.
An <<include>> represents behavior that is factored out for reuse, not because it is an
exception.
The direction of a <<include>> relationship is to the using use case (unlike <<extend>>
relationships).
<<include>>

Online customer
<<include>>
Add shipping address
Select shipping address
Select credit card

<<include>>
<<include>>
Add credit card
<<include>>
<<include>
>
Add Credit card type
Add Credit card number
Add Expiration date
Fig :5.1 Use Case Diagram
RGIT, MUMBAI.
Page 13
Department of MCA.

SYSTEM
Update Items
Administrator
Register Customer
Customer
Search Item
<<include>>
Validate Customer
<<include>>
<<include>>
Registered
Customer
<<include>>
Buy Item
Prepare Bill
Pay Bill
Fig 5.2 Use case Diagram
RGIT, MUMBAI.
Page 14
Department of MCA.

SYSTEM
USE CASE DESCRIPTION :

Actors:
2.1 New Customers
2.2 Registered Customer
2.3 Administrator
Use cases:
1. Search Item
2. Register Item
3. Buy Item
4. Update Item
1. Search Item
Any user can search the item. User can search the item by name or company.
2. Register Customer
To buy the item, the customer has to be a registered customer. This process is used to register
a customer.
3. Buy Item
A registered customer can buy a item using this process. This process include search item,
validate customer, prepare bill, pay bill.
RGIT, MUMBAI.
Page 15
Department of MCA.

SYSTEM
Use Case Table

Use case ID
Use case ID
Use case ID
RGIT, MUMBAI.
Page 16
Department of MCA.
Use case ID
Use case ID
Use case ID
RGIT, MUMBAI.

SYSTEM
Page 17
Department of MCA.
Use case ID
Use case ID
Use case ID
RGIT, MUMBAI.

SYSTEM
Page 18
Department of MCA.
View shopping cart

SYSTEM
Search for product
Add item to shopping cart
Create new user

Online Customer
Administrator
Change item information
Select credit card
Purchase item
Review order confirmation
Block users
Choose shipping type

Login as registered user
Shopping Cart system

Inform the deal to seller
Register Item
Online seller
fig 5.3. Use case diagram for Online Shopping System
RGIT, MUMBAI.
Page 19
Department of MCA.

SYSTEM
6. UML Interaction Diagram

6.1 Sequence Diagram :
Shopping cart
system
user
Administrator
User Login
user name & password
gives the details

give access to member
Fig.6.1.1 Sequence Diagram for User registeration
RGIT, MUMBAI.
Page 20
Department of MCA.

SYSTEM
Administrator
: Online seller
Item Registration
Log out();
Fig.6.1.2 Sequence Diagram for Seller registeration
RGIT, MUMBAI.
Page 21
Department of MCA.
Shopping cart

SYSTEM
Cart item
Process
order
: Online
Customer
Logout
Order
summary
Adds Item
Gets Item
Product Details
Add the products
Shipping Charges
Taxes Taxes
Payment Details
Processes
Processes
Displays the ordered item
Displays the Orderd Item
Confirms
Checks Out
Confirms
Checkout
Fig.6.1.3 Sequence Diagram for Online Customer
RGIT, MUMBAI.
Page 22
Department of MCA.

SYSTEM
Shopping
system
Cart system
Ordering
system
: Online Customer
Login
Add item
Add category
Add user
Delete user
Change password
Delete item
Delete category
Logout
Fig.6.1.4 Sequence Diagram for Online Administrator
RGIT, MUMBAI.
Page 23
Department of MCA.

SYSTEM
6.2 Collaboration diagrams:

They are also interaction diagrams. They convey the same information as sequence
diagrams, but they focus on object roles instead of the times that messages are sent. In a
sequence diagram, object roles are the vertices and messages are the connecting links.
Collaboration diagrams show (used to model) how objects interact and their roles.
They are very similar to sequence diagrams. Actually they are considered as a cross
between class and sequence diagram.
Sequence Diagrams are arranged according to Time.
Collaboration Diagrams represent the structural organization of object.
[Both sequence and collaboration diagrams are called interaction diagrams]
Forms a context for interactions
o May realize use cases
o May be associated with operations
o May describe the static structure of classes
Collaboration diagrams contain the following:
o Class roles (subsystems/objects/classes/actors/ external systems) as before.
o Association roles (pathways or links over which messages flow)
o Message flows (messages sent between class roles)
1:
User Login
user
Shopping cart
system
4: give access to member
3: gives detail
2: user name & password
Administrator
Fig.6.2.1 Collaboration Diagram for User registration
RGIT, MUMBAI.
Page 24
Department of MCA.

SYSTEM
Item registration
log out();
1:
2:
Administrator
: Online seller
Fig.6.2.2Collaboration Diagram for Seller registeration
Shopping
cart
1: Adds Item
11: Checkout
Logout
2: Gets Item
: Online customer
10: Confirms
Cart item
9: Displays the Orderd Item
8: Processes
Order
summary
3: Product Details
4: Add the products
5: Shipping Charges
6: Taxes
7: Payment Details
Process
order
Fig.6.2.3 Collaboration Diagram for Online Customer
RGIT, MUMBAI.
Page 25
Department of MCA.

SYSTEM
1: Logiin
: Online Customer
Shopping
system
9: Logout
Cart
system
2: Add item
3: Add category
7: Delete item
8: Delete category
4: Add user
5: Delete user
6: Change password
Ordering
system
Fig.6.2.4 Collaboration Diagram for Online Administrator
RGIT, MUMBAI.
Page 26
Department of MCA.

SYSTEM
7. Statechart Diagram:
The name of the diagram itself clarifies the purpose of the diagram and other details. It
describes different states of a component in a system. The states are specific to a
component/object of a system.
A Statechart diagram describes a state machine. Now to clarify it state machine can be
defined as a machine, which defines different states of an object, and these states are
controlled by external or internal events.
Member
Logging
Member Login
Verifying
Valid login
Accessing the
account
Invalid Login
Member Access
Re-Logging
managing
account
Member Relogin
Perform Reservation
Invalid >3 times
Reserving
Perform cancellation
Cancelling
Process credit card details
Process credit card details

Credit card
Processing
Transaction Processing
Transaction
Performing
transaction Processed
Printing
Ticket
Fig.7.1 State Chart diagram for Online Shopping System
RGIT, MUMBAI.
Page 27
Department of MCA.
Searching
registered customer
buy the item

new customer
Register

SYSTEM
Selecting
more items
buy item
Buying
item selection over

Pay bill
Fig7.2 State diagram for customer.
RGIT, MUMBAI.
Page 28
Department of MCA.

SYSTEM
8. CLASS DIAGRAM :
USER

SYSTEM
Email id : String
password : String
First name : String
Last Name : String
Street Address : String
ZipCode : Integer
City : String
State : String
Country : String
Phone : String
HTTP
CUSTOMER
Number of Item : Integer
cusid : Integer
Shipnname : String
Company : String
Address : String
Login()
Registration()
Logout()
Payment()
CartAddition()
Cancellation()
SELLER
Item name : String
Item id : Integer
Discount : Integer
Categoty : Integer
CartAddition
Creidtno : String
Description : String
ItemId : String
Amount : Integer
Category : String
CANCELLATION
cusno : Integer
Item id : Integer
amount : Integer
retrive()
update()
Get_to_cart()
Check_out()
CREDIT CARD HOLDER

cardno
issuedate
expirydate
verifydtls()
perform_transaction()
Payment System
custno
custid
custname
creditcardno
BillingAddress
TRANSACTION
transid
pnrno
transdate
amt
VeiwOrder()
PaymentDetails()
commit()
rollback()
Fig 8.1 Class diagram for Online Shopping System

RGIT, MUMBAI.
Page 29
Department of MCA.

SYSTEM
9.Implementation Diagram.
9.1 Component Diagram :
Component diagrams are different in terms of nature and behavior. Component diagrams
are used to model physical aspects of a system.
Physical aspects are the elements like executables, libraries, files, documents etc that
resides in a node. So component diagrams are used to visualize the organization and
relationships among components in a system. These diagrams are also used to make executable
systems.
Description of the component diagram for online shopping system is as follows :
Data base server contains all the database tables. It contains Administrator, Registered
Customer, Seller, Item and Payment.
Application server contains Access classes package and Business classes package and view
layer classes, i.e. view classes package.
Clients are the nodes having no processing capabilities. Only browser is there on this node
to send a request
RGIT, MUMBAI.
Page 30
Department of MCA.

SYSTEM
Component Diagram :
View Classes
Home Page
Registration
Form
Login
Form
Updation
Form
Searching
Form
Ordering
Form
Payment
form
Business Classes
Registered
Customer
Seller
Payment
Administrator
Access Classes
Access
Database
RGIT, MUMBAI.
Page 31
Department of MCA.

SYSTEM
9.2 Deployment Diagram :

Deployment diagrams are used to visualize the topology of the physical components
of a system where the software components are deployed.
So deployment diagrams are used to describe the static deployment view of a system.
Deployment diagrams consist of nodes and their relationships.
Client
<<Private Network>>
Data Base
Server
Oracle Server
<<LAN>>
Application
Server
Client
<<Private Network>>
Application Server.exe
<<Private Network>>
Client
Fig 9..2 Deployment diagram for Online Shopping System.
RGIT, MUMBAI.
Page 32
Department of MCA.

Contents: Page No

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Contents: Page No

Hochgeladen von

Copyright:

Verfügbare Formate

Object Oriented Modeling and Design

ONLINE SHOPPING CART

5. USE CASE DIAGRAM

7. STATE CHART DIAGRAM

9.1 COMPONENT DIAGRAM

9.2 DEPLOYMENT DIAGRAM

Object Oriented Modeling and Design

ONLINE SHOPPING CART

Object Oriented Modeling and Design

ONLINE SHOPPING CART

2 Software Requirement Specification:

Object Oriented Modeling and Design

ONLINE SHOPPING CART

Context Level / Level 0

Object Oriented Modeling and Design

ONLINE SHOPPING CART

Product Product Product

Fig 3.2 Data Flow Diagram for Product Listing

Object Oriented Modeling and Design

ONLINE SHOPPING CART

Fig : 3.3Data Flow Diagram for Administrator.

Object Oriented Modeling and Design

ONLINE SHOPPING CART

Payment made through credit

Final calculate amount displayed on

Gives the Payment

Fig: Data Flow Diagram for Secure Gateway Provider.

Object Oriented Modeling and Design

ONLINE SHOPPING CART

Action States and Activity States

Action states are atomic and cannot be decomposed

Activity represents the performance of some behavior in the work flow.

Object Oriented Modeling and Design

ONLINE SHOPPING CART

A flow of control has to start and end at some place

The transition from a decision point contain a guard condition.

Object Oriented Modeling and Design

ONLINE SHOPPING CART

Object Oriented Modeling and Design

ONLINE SHOPPING CART

Fig 4.1 Activity Diagram :

product avilable in india?

item get added

do you want to cancel the product?

want to fill feedback?

Object Oriented Modeling and Design

ONLINE SHOPPING CART

Used during requirements elicitation to represent external behavior

Object Oriented Modeling and Design

ONLINE SHOPPING CART

<<extend>> relationships represent exceptional or seldom invoked cases.

The <<include>> Relationship

Add shipping address

Select shipping address

Select credit card

Add Credit card type

Add Credit card number

Add Expiration date

Fig :5.1 Use Case Diagram

Object Oriented Modeling and Design

ONLINE SHOPPING CART

Fig 5.2 Use case Diagram

Object Oriented Modeling and Design