Shivamraj Dhokane 02 SYCSBS

EXPERIMENT NO 2

AIM : to study use case diagram of online shopping system

THEORY :

What is a UML use case diagram?

UML use case diagrams are a type of visual modeling tool that are used to describe the
interactions between a system and its actors (users, systems, or other entities). They are often
used to identify the different use cases (functional requirements) of a system, and the actors
that participate in them. The diagram consists of actors, use cases, and the relationships
between them, and can be used to communicate the functional requirements of the system to
stakeholders. Use case diagrams can also be used to support requirements analysis, system
design, and software testing.

Benefits of use case diagrams in online shopping system

Sure, here are some benefits of use case diagrams in an online shopping system:

- Helps to identify and prioritize the functional requirements of the system

- Enables communication and collaboration between stakeholders such as customers, vendors, and
developers

- Provides a clear understanding of the system's behavior and the interactions between actors and use
cases

- Facilitates the design and development of the software system

- Supports requirements analysis, testing, and maintenance of the system

- Helps to identify potential issues and conflicts early in the development process

- Provides a high-level overview of the system functionality that can be used for documentation
purposes

- Supports the identification of reusable components and modules that can be used in other projects or
systems.
Shivamraj Dhokane 02 SYCSBS

Overall, use case diagrams can be a valuable tool for understanding, designing, and developing an
online shopping system.

Use case diagram shapes and symbols

here are some of the common shapes and symbols used in use case diagrams that
can be used for an online shopping system:

- Actor: Represents the user or external system that interacts with the system being
modeled. Examples of actors in an online shopping system may include customers,
vendors, and payment gateways.

- Use Case: Represents a specific piece of functionality or behavior that the system
provides to its users. Examples of use cases in an online shopping system may
include "Browse Products," "Add to Cart," "Checkout," and "Make Payment."

- System Boundary: Represents the boundary of the system being modeled.

In addition, the following relationships can be used to connect actors and use cases
in the diagram:

- Association: Represents a relationship between an actor and a use case. It shows

that the actor interacts with the use case in some way.
Shivamraj Dhokane 02 SYCSBS

- Extend: Represents a relationship between two use cases where one use case (the
"extension") adds functionality to another use case (the "base"). An example in an
online shopping system might be an "Apply Coupon" use case that extends the
"Checkout" use case.

- Include: Represents a relationship between two use cases where one use case (the
"inclusion") includes another use case (the "base"). An example in an online shopping
system might be a "View Order History" use case that includes the "Login" use case.

You can use these shapes and symbols to create a use case diagram that models the
functionality and behaviour of an online shopping system.

The above diagram represents the use case diagram of online shopping system
Shivamraj Dhokane 02 SYCSBS

Conclusion : In conclusion, a use case diagram for an online shopping system can
help identify the functional requirements and interactions between the different
actors and use cases in the system. By using symbols such as actors, use cases, and
system boundaries, the diagram can represent the different pieces of functionality
that the system provides, such as browsing products, adding to cart, and making
payments. This diagram can be used as a guide for developing the software system
and also serves as a documentation tool for stakeholders. Overall, the use case
diagram can help facilitate communication and collaboration between stakeholders,
support requirements analysis, and provide a high-level overview of the system
functionality.