Name:- Ganesh Kumar Vanam

121910314059
3B14 - 59

ONLINE SHOPPING SYSTEM

ONLINE SHOPPING SYSTEM SPECIFICATIONS:-

Objectives:-

The goal of this document is to establish the online

retail system's needs. This specification lists the criteria that
aren't well-represented in the Use case model's use cases.
Together, the additional specifications and the use case model
represent the entire range of system requirements.

Scope:-
The non-functional needs of the system, such as reliability,
usability, performance, and supportability, are defined in the
specification. The use case specifications define the functional
requirements.
References:-
Amazon.com, flipcart.com.

Functionality:-
Multiple users must be able to work at the same
time. The user must be notified when products in the inventory
are out of stock.

Usability:-
The desktop user-interface shall be Windows 95, 98
compliant.

Reliability:-
The system shall be available 24 hrs a day and 7 days a
week.

Performance:-
• The system shall support large number of simultaneous
users against the central database at any time.

• The system shall provide access to catalog database with

no more then ten seconds latency.
• The system must be able to complete 80% of all
transactions within 2 minutes.

Supportability:- None
Brief Description of the Project:- The present project focuses on
online retail system analysis and design. This meets the requirements
of the clients. Customers' available activities in the proposed system
are outlined, including logging on, browsing the store, selecting items,
and making purchases.
PROBLEM STATEMENT FOR ONLINE SHOPPING SYSTEM:- You've been
tasked with designing an internet shopping system as a talented young
student. The system should be competitive enough by offering the
same features and possibilities as well-known systems like
Amazon.com and Flipcart.com. The proposed system should enable
customers to do tasks such as logging in, browsing the store, selecting
things, and making transactions, i.e., customers will be able to browse,
choose, and purchase items online.

To access the store, an internet customer should have a

login. The primary goal is to register the customer with the product. A
customer who has registered can look through the catalogue and make
purchases. The new system should also assist customers in locating
things by allowing them to browse the current product catalogue
online, which should include item details and stock information.

Filtering by product title, author, and k category should be

possible. If a product is not available in the current category, the user
should place an order and request it. Payment is made by credit card,
as well as gift cheques and other methods, and the customer is notified
of the transaction details by e-mail. The customer enters the shipment
specifics, and the delivery is processed using those details.

Modeling steps for Use case Diagram

• Draw the lines around the system and actors lie

outside the system.
Identify the actors which are interacting with the system.
• Separate the generalized and specialized actors.
• Identify the functionality the way of interacting
actors with system and specify the behavior of actor.
• Functionality or behavior of actors is considered as use cases.
• Specify the generalized and specialized use cases.
• Se the relatonship among the use cases and in
between actor and use cases.
Adorn with constraints and notes.
• If necessary, use collaborations to realize use cases.

Modeling steps for Sequence Diagrams

• Set the context for the interactions, system,

subsystem, classes, object or use cases.
• Set the stages for the interactions by identifying
objects which are placed as actions in interaction
diagrams.
• Lay them out along the X-axis by placing the
important object at the left side and others in the next
subsequent.
• Set the lifelines for each and every object by
sending create and destroy messages.
• Start the message which is initiating interactions and
place all other messages in the increasing order of items.
• Specify the time and space constraints.
• Set the pre and post conditioned.

Modeling steps for Collaboration Diagrams

• Set the context for interaction, whether it is system,

subsystem, operation or class or one scenario of use
case or collaboration.
• Identify the objects that play a role in the
interaction. Lay them as vertices in graph, placing
important objects in centre and neighboring objects
to outside.
• Set the initial properties of each of these objects. If
the attributes or tagged values of an object changes
in significant ways over the interaction, place a
duplicate object, update with

these new values and connect them by a message

stereotyped as become or copy.
• Specify the links among these objects. Lay the
association links first represent structural
connection. Lay out other links and adorn with
stereotypes.
• Starting with the message that initiates this
interaction, attach each subsequent message to
appropriate link, setting sequence number as
appropriate.
• Adorn each message with time and space constraints if needed
• Attach pre & post conditions to specify flow of control formally.

Modeling steps for Activity Diagrams

• Select the object that has high level responsibilities.

• These objects may be real or abstract. In either
case, create a swim lane for each important object.
• Identify the precondition of initial state and post
conditions of final state.
• Beginning at initial state, specify the activities and
actions and render them as activity states or action
states.
 • For complicated actions, or for a set of actions that
appear multiple times, collapse these states and
provide separate activity diagram.
• Render the transitions that connect these activities
and action states.
• Start with sequential flows; consider branching, fork and joining.
• Adorn with notes tagged values and so on.

Modeling steps for State chart Diagram

• Choose the context for state machine,whether it is a

class, a use case, or the system as a whole.
• Choose the initial & final states of the objects.
• Decide on the stable states of the object by
considering the conditions in which the object may
exist for some identifiable period of time. Start with
the high-level states of the objects & only then
consider its possible substrates.
• Decide on the meaningful partial ordering of stable
states over the lifetime of the object.

• Decide on the events that may trigger a transition

from state to state. Model these events as triggers to
transitions that move from one legal ordering of
states to another.
• Attach actions to these transitions and/or to these states.
• Consider ways to simplify your machine by using
substates, branches, forks, joins and history states.
• Check that all states are reachable under some
combination of events.
• Check that no state is a dead from which no
combination of events will transition the object out
of that state.
• Trace through the state machine, either manually or
by using tools, to check it against expected sequence of
events & their responses.

Modeling steps for Class Diagrams

• Identity the things that are interacting with class diagram.

• Set the attributes and operations.
• Set the responsibilities.
• Identify the generalization and specification classes.
• Set the relationship among all the things.
• Adorn with tagged values, constraints and notes.

Modeling steps for Object Diagrams

• Identify the mechanisms which you would like to model.

• Identify the classes, use cases, interface,
 subsystem which are collaborated with
mechanisms.
• Identify the relationship among all objects.
• Walk through the scenario until to reach the
certain point and identify the objects at that
point.
• Render all these classes as objects in diagram.
• Specify the links among all these objects.
• Set the values of attributes and states of objects.

Modeling steps for Component Diagrams

• Identify the component libraries and executable files

which are interacting with the system.
• Represent this executables and libraries as components.
• Show the relationships among all the components.
• Identify the files, tables, documents which are
interacting with the system.

• Represent files,tables,documents as components.

• Show the existing relationships among
them generally dependency.
• Identify the seams in the model.
• Identify the interfaces which are interacting with the system.
• Set attributes and operation signatures for interfaces.
• Use either import or export relationship in b/w
interfaces & components.
• Identify the source code which is interacting with the
system.
• Set the version of the source code as a constraint to
each source code.
• Represent source code as components.
• Show the relationships among components.
• Adorn with nodes, constraints and tag values.

Modeling steps for Deployment Diagram

• Identify the processors which represent client & server.

• Provide the visual cue via stereotype classes.
• Group all the similar clients into one package.
• Provide the links among clients & servers.
• Provide the attributes & operations.
• Specify the components which are living on nodes.
• Adorn with nodes & constraints & draw the deployment diagram.

USE CASE DIAGRAM FOR ONLINE SHOPPING SYSTEM:- USE CASE

The use case model describes the proposed
functionality of the system. A use case represents a discrete unit
of interaction between a user and the system. A use case is a
single unit of meaningful work. Each use case has a description
which describes the functionality that will be built in a proposed
system. A use case may ‘include’ another use case functionality
or ‘extend’ another use case with its own behavior.

ACTORS:-Customer and

seller staff.

USE CASES:
• Registration
• Login
• Create order
• Manage cart and payments
• Order status
• Inventory

CLASS DIAGRAM:-
A Class is a standard UML construct used to detail the
pattern from which objects will be produced at run time. A class
is a specification- an object is an instance of a class. Classes
may be inherited from other classes, have other classes as
attributes, delegate responsibilities to other classes and
implement abstract interfaces.
The class diagram for the proposed system has
several classes. These classes have attributes and operations.
The description for each of them is described clearly.
The classes include
• Seller staff
• products
• Items
• Customer
• Shopping cart
• Order
• Item order
• Shipping address and billing address.

PACKAGE-1: ONLINE SHOPPING

 • This package consists of following classes:
• 1. SELLER staff
• 2. ITEMS
• 3.PRODUCTS
• 4. Items

The class diagram of the online shopping system is

shown to be grouped into three packages.
PACKAGE-2: CUSTOMER
This package consists of following classes:
• Customer
• Address
• Billing Address
• Shipping Address

PACKAGE -3:ONLINE ORDERING

This package consists of following classes:
• Order
• Item Order
• Shopping Cart

CLASS DIAGRAM:-

SEQUENCE DIAGRAM:-

UML provides a graphical means of depicting object

interactions over time in sequence diagrams. These typically
show a user or actor and the objects and components they
 interact with in the execution of a use case.

COLLOBORATION DIAGRAM:-

Collaboration names a society of classes, interfaces and other

elements that work together to provide some cooperative
behavior that is bigger than the sum of all its parts.
Collaboration diagram emphasis is based on structural
organization of the objects that send and receive messages.

STATE CHART DIAGRAM:-

Objects have behaviors and state. The

state of an object depends on its current activity or condition. A
state chart diagram shows the possible states of the object and
the transitions that cause a change in state. The initial state
(black circle) is a dummy to start the action. Final states are also
dummy states that terminate the action.

ACTIVITY DIAGRAM:-

An activity diagram is essentially a fancy flowchart.

Activity diagrams and state chart diagrams are related. While a
state chart diagram focuses attention on an object undergoing a
process (or on a process as an object), an activity diagram
focuses on the flow of activities involved in a single process. The
activity diagram shows the how those activities depend on one
another. Activity diagrams can be divided into object swim lanes
that determine which object is responsible for which activity. A
single transaction comes out of each activity, connecting it to
the next activity.
COMPONENT DIAGRAM:-

A component is a code module. Component

diagrams are physical analogs of class diagram. Each component
belongs on a node. Components are shown as rectangles with
two tabs at the upper left.

DEPLOYMENT DIAGRAM:-
Deployment diagram shows the physical
configurations of software and hardware.

RESULT:

Thus various UML Diagrams were generated for ONLINE SHOPPING and
the corresponding code was generated using Visual Basic.