Name: Shubham Sharma CSE-C

Roll no.: 2000320100163 Admission No.: 2020B0101082

Experiment -2
Aim: Modelling UML Use case Diagram and Capturing Use Case Scenario.
Theory: Use-case diagrams describe the high-level functions and scope of a system. These
diagrams also identify the interactions between the system and its actors. The use cases and
actors in use-case diagrams describe what the system does and how the actors use it, but not how
the system operates internally.
UML use case diagrams are ideal for:
 Representing the goals of system-user interactions
 Defining and organizing functional requirements in a system
 Specifying the context and requirements of a system
 Modelling the basic flow of events in a use case
When we are planning to draw a use case diagram, we should have the following items
identified.
 Functionalities to be represented as use case
 Actors
 Relationships among the use cases and actors.

Use Case Scenario:

In this use case diagram, there are several actors:
1. Customer: This actor can register, login, browse/search the product catalog, add items to
their cart, checkout, view their order history, and contact customer service.
2. Administrator: This actor can manage the product catalog, view and manage orders, and
manage shipping and logistics.

The use cases in the diagram include:

1. Register: Allows a customer to create a new account with the system.
2. Login: Allows a customer to authenticate and access their account.
3. Browse/Search: Allows a customer to search for and browse through the product catalog.
4. Cart: Allows a customer to add items to their retailing cart and view the contents of their
cart.
5. Checkout: Allows a customer to review their cart, select shipping and payment options,
and complete their purchase.
6. Catalog: Allows an administrator to manage the product catalog, including adding, editing,
and deleting products.
7. Order Management: Allows an administrator to view and manage orders, including
processing returns and refunds.
8. Payment: Allows the system to process payments for purchases made by customers.
9. Shipping and Logistics: Allows an administrator to manage shipping and delivery of
products to customers.
10. Customer Service: Allows a customer to contact customer service for assistance with their
account or orders.
This use case diagram provides a high-level view of the various interactions between actors and
the system in an online retailing system.
Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082

USE CASE DIAGRAM:

Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082
Experiment -3
Aim: ER-Modelling from the Problem Statements.
Theory:
An ER diagram for an online retailing system typically includes the following:
Entities:
1. Customer: Represents the user who browses and purchases products from the online store.
2. Product: Represents the items available for purchase in the online store. The product entity
contains attributes such as product ID, name, description, price, and quantity.
3. Order: Represents a customer's purchase of one or more products.
4. Payment: Represents the transaction between the customer and the online store.
5. Online Retailing Website: Online retailing is a form of electronic commerce that allows
consumers to directly buy goods or services.
6. Category: Represents the classification of products based on their type, brand, or other
criteria.
7. Tracking Details: Tracking numbers are numbers assigned to packages when they are
shipped. Tracking numbers are useful for knowing the location of time-sensitive deliveries.
8. Supplier: A supplier is an individual or a company that provides goods or services to another
entity or organization.
Relationships between these entities, such as:
 A customer can place one or more orders.
 An order can contain one or more products.
 An admin manages one or more online website.
 An online website has more product categories.
 A product can belong to one or more categories.
 An order must be associated with one payment.
 An order must be associated with one shipping.
 A Supplier can supply one or more products.
The cardinality of the relationships between entities, such as:
 A customer can place zero or more orders.
 An order must be associated with exactly one customer.
 A product can belong to zero or more categories.
 An order must be associated with exactly one payment and exactly one shipping.
ER-Diagram:
Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082

ER Diagram for Online Retailing System

 Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082
Experiment - 4
Aim: Modelling Data Flow Diagram.
Theory:-
Level 0 DFD:
This is the Zero Level DFD of the Online Retailing System, where we have elaborated the high-
level process of the Retailing System. It's a basic overview of the whole Online Retailing System
or process being analyzed or modeled. It's designed to be an at-a-glance view of Product,
Delivery, and Confirm Order showing the system as a single high-level process, with it’s
relationship to external entities of Retailing, Retailing Cart, and Order. It should be easily
understood by a wide audience, including Retailing. Order and Product In zero level DFD of the
Online Retailing System, we have described the high-level flow of the Retailing System.

Online
Retailing
System

Level 1 DFD:
First Level DD (1st Level) of Online Retailing System shows how the system is divided into sub-
systems (processes), each of which deals with one or more of the data flows to or from an external
agent, and which together provide all of the functionality of the Online Retailing System as a
whole. It also identifies internal data stores of Confirm Order, Delivery, Product, Payment, and
Order that must be present in order for the Retailing System to do its job, and shows the flow of
data between the various parts of Retailing, Order, Delivery, Confirm Order, Product of the
system. DFD Level 1 provides a more detailed breakout of pieces of the 1st level DD. You will
highlight the main functionalities of the Retailing System.
Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082
Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082

Level 2 DFD:
DFD Level 2 then goes one step deeper into parts of Level 1 of the Retailing System. It may
require more functionalities of the Retailing System to reach the necessary level of detail about
the Retailing System’s functioning. First Level DD (1st Level) of the Online Retailing System
shows how the system is divided into sub-systems (processes). The 2nd Level DD contains more
details of Confirm Order, Delivery, Product, Payment, Order, Retailing Cart, and Retailing.
Functionalities are:
• Admin logins to the system and manage all the functionalities of Online Retailing System
• Admin can add edit, delete and view the records of Retailing, Order, Product, Confirm Order
• Admin can manage all the details of Retailing Cart, Payment, Delivery
• Admin can also generate reports of Retailing. Retailing Cart, Order, Payment, Product,
Delivery
• Admin can search the details of Retailing Cart, Product, Delivery
• Admin can apply diferent level of filters on report of Retailing, Payment, Product
• Admin can tracks the detailed information of Retailing Cart, Order, Payment,, Product
Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082

Experiment - 6
Aim: Modelling UML State Chart Diagram and Activity Diagram for Problem statement on
“Online Retailing system”.

State Chart Diagram:

A state chart diagram, also known as a state machine diagram, represents the various states that
an object or system can be in and the transitions between those states based on events and
actions. In an online retailing system, a state chart diagram would typically represent the states
that an order can be in and the transitions between those states.
In an online retailing system, a state chart diagram would typically include the following
elements:
1. States: These represent the various states that an order can be in, such as "Login,"
"Verification," and "Access account".
2. Transitions: These represent the actions that can occur to move an order from one state
to another, such as "place order," "Add to cart," or "cancel the order."
3. Events: These represent the triggers or conditions that cause a transition to occur, such
as a customer placing an order or a shipment being confirmed.
4. Actions: These represent the activities that occur when a transition is made, such as
updating the order status or sending a shipping confirmation email.
5. Guards: These represent the conditions that must be met for a transition to occur, such
as the order being in the "in progress" state before it can be shipped.
The state chart diagram provides a visual representation of the possible states and transitions
of order in the online shopping system It can be used to ensure that the system behaves correctly
under different conditions, and can also be used as a basis for testing and refining the system.
Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082

Activity Diagram:
An activity diagram for an online shopping system represents the activities involved in the
system and the sequence of actions that are taken to complete a transaction or process. It
illustrates the flow of activities from start to finish, including the decision points and conditions
that determine the path of the activity.
In an online retailing system, an activity diagram would typically include the following
elements:
1. Start and end nodes: These represent the beginning and end of the activity diagram.
2. Activities: These represent the actions taken by the customer and the system during the
online shopping process. Activities may include login, browsing products, adding items
to the shopping cart, selecting a payment method, and completing the transaction.
3. Decision points: These represent the points in the process where a decision must be
made based on certain conditions. For example, a decision point may be reached when
the customer selects a payment method, and the system must determine whether the
payment method is valid and can be processed.
4. Fork and join nodes: These are used to represent parallel activities that occur at the
same time, or multiple activities that must be completed before moving to the next step.
5. Swimlanes: These represent the different actors involved in the process, such as the
customer, the system, and the View reports.
6. Arrows: These show the flow of activity from one node to another.
The activity diagram provides a visual representation of the online retailing process, allowing
designers and developers to identify the sequence of activities, decision points, and conditions
that are involved in the process. It can be used as a basis for testing and refining the system, as
well as for training new users on how to use the system.
Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082

Experiment - 7
Aim: Modelling UML Sequence Diagram for Problem statement on “Online
Retailing system”.
Sequence Diagram:
A sequence diagram for an online retailing system represents the interactions
between the various components or objects in the system as a sequence of
messages exchanged between them. It illustrates the sequence of actions taken by
the system and the external actors involved in the process.
In an online retailing system, a sequence diagram would typically include the
following elements:
1. Actors: These represent the external entities involved in the online
shopping process, such as the customer, the system, and the payment
processor.
2. Objects: These represent the components within the system, such as the
shopping cart, the product catalog, and the payment gateway.
3. Messages: These represent the communications between the actors and
objects, such as customizing an item to the shopping cart, the system
retrieving the product details, and the payment processor confirming the
payment.
4. Lifelines: These represent the duration of an object or component within
the system, from the start of the sequence diagram to the end.
5. Activation bars: These represent the time during which an object or
component is active within the system, during which messages can be
exchanged.
6. Return messages: These represent the response or acknowledgment
messages sent from an object or component back to the actor or object that
initiated the message.
The sequence diagram provides a visual representation of the interactions and
communications between the various components and actors in the online
shopping system, allowing designers and developers to identify potential issues
or errors in the process. It can be used to ensure that the system behaves correctly
under different conditions, and can also be used as a basis for testing and refining
the system.
Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082
Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082

Experiment - 8
Aim: Modelling UML Class Diagram for Problem statement on “Online
Retailing system”.
Class Diagram:
A class diagram for an online retailing system represents the different classes of
objects or entities within the system and the relationships between them. It
provides a high-level view of the system architecture and the data structures used
to support the functionality of the system.
In an online retailing system, a class diagram would typically include the
following elements:
1. Classes: These represent the objects or entities within the system, such as
customers, products, orders, and payments.
2. Attributes: These represent the properties or characteristics of the classes,
such as the name, address, and email of a customer, or the price, quantity,
and description of a product.
3. Methods: These represent the actions or operations that can be performed
on the classes, such as adding a product to a retail cart, updating the status
of an order, or processing a payment.
4. Relationships: These represent the associations or dependencies between
the classes, such as a customer having many orders, an order having many
line items, or a product having many reviews.
5. Multiplicity: This represents the number of instances of a class that can be
associated with another class, such as a customer having one or many
orders, or a product having one or many reviews.
The class diagram provides a visual representation of the relationships and
dependencies between the different classes within the online retailing system,
allowing designers and developers to understand the system architecture and the
data structures used to support the functionality of the system. It can be used as a
basis for designing the database schema, developing the system components, and
testing and refining the system.
Name: Shubham Sharma CSE-C
Roll no.: 2000320100163 Admission No.: 2020B0101082