Online shopping model:

Purpose: Provide top level use cases for a web customer making purchases online.

Summary: Web customer actor uses some web site to make purchases online. Top level use
cases are View Items, Make Purchase and Client Register.

Web Customer actor uses some web site to make purchases online. Top level use cases are
View Items, Make Purchase and Client Register. View Items use case could be used by
customer as top level use case if customer only wants to find and see some products. This use
case could also be used as a part of Make Purchase use case. Client Register use case allows
customer to register on the web site, for example to get some coupons or be invited to private
sales. Except for the Web Customer actor there are several other actors which will be described
below with detailed use cases.

View Items use case is extended by several optional use cases - customer may search for items,
browse catalog, view items recommended for him/her, add items to shopping cart or wish list.
All these use cases are extending use cases because they provide some optional functions
allowing customer to find item.
Customer Authentication use case is included in View Recommended Items and Add to
Wish List because both require the customer to be authenticated. At the same time, item could
be added to the shopping cart without user authentication.

Checkout use case includes several required uses cases. Web customer should be authenticated.
It could be done through user login page, user authentication cookie ("Remember me") or Single
Sign-On (SSO). Web site authentication service is used in all these use cases, while SSO also
requires participation of external identity provider.

Checkout use case also includes Payment use case which could be done either by using credit
card and external credit payment service or with PayPal.
Class Diagram
Here we provide an example of UML class diagram which shows a domain model for online
shopping. The purpose of the diagram is to introduce some common terms, "dictionary" for
online shopping - Customer, Web User, Account, Shopping Cart, Product, Order, Payment, etc.
and relationships between. It could be used as a common ground between business analysts and
software developers.

Each customer has unique id and is linked to exactly one account. Account owns shopping cart
and orders. Customer could register as a web user to be able to buy items online. Customer is not
required to be a web user because purchases could also be made by phone or by ordering from
catalogues. Web user has login name which also serves as unique id. Web user could be in
several states - new, active, temporary blocked, or banned, and be linked to a shopping cart.
Shopping cart belongs to account.
What is an Activity Diagram
The Unified Modeling Language has several subsets of diagrams that it can model, including
structure diagrams, interaction diagrams, and behavior diagrams. Activity diagrams are a subset
of the latter. Along with use case and state machine diagrams, they're used to describe business
activities and software systems' functionality. You'll use a set of specialized symbolsincluding
those for starting, ending, merging, or receiving steps in the flowto build an activity diagram.

Stakeholders have many issues to manage, so it's important to communicate with clarity and
brevity. Activity diagrams help people on the business and development sides of an organization
come together.
Use Cases for Activity Diagram
Activity diagrams have a number of benefits for any organization. Try using an activity diagram
to:

Demonstrate the logic of an algorithm.

Describe the steps performed in a UML use case.
Illustrate a business process or workflow between users and the system.
Simplify and improve any process by clarifying complicated use cases.
Model software architecture elements, such as method, function, and operation.

Activity Diagram Components

To answer the question of "What is an activity diagram in UML?", you should first understand
its makeup. Some of the most common components of an activity diagram include:

Actions - a step in the activity wherein the users or software perform a given task. In
Lucidchart, this is symbolized with a round-edged rectangle.
Decision node - a conditional branch in the flow that is represented with a diamond. It
includes a single input and two or more outputs.
Control flows - this is another name for the connectors that show the flow between steps
in the diagram.
Start node - symbolizes the beginning of the activity. This is represented with a black
circle.
 End node - represents the final step in the activity. It's modeled with an outlined black
circle.

What is a Sequence Diagram

To understand what a sequence diagram is, it's important to know the role of UML. UML, or the
Unified Modeling Language, is a modeling toolkit that guides the creation and notation of many
types of diagrams, including behavior diagrams, interaction diagrams, and structure diagrams.
Sequence diagrams are a kind of interaction diagram, because they describe howand in what
ordera group of objects works together. These diagrams are used by software developers and
business people alike to understand requirements for a new system or to document an existing
process. Sequence diagrams are sometimes known as event diagrams or event scenarios.

Remember that there are two types of sequence diagrams: UML ones and code-based ones. The
latter are sourced from programming code and will not be covered in this guide

Online shopping has become an industry game-changer. Instead of setting up physical stores to
attract customers, companies can reach potential buyers through the web. And customers don't
need to leave the comfort of their homes in order to shop; they make purchases with a single
click and have them delivered to their doors. The convenience of this system is dependent upon
technology, which is why you should have critical UML diagrams on hand. Check out the
example below, which captures major players and steps in the process of online shopping.
Building Blocks of Component Diagrams
Component diagrams range from simple and high-level to detailed and complex. Either way,
you'll want to familiarize yourself with the appropriate UML symbols. These are some shape
types you will commonly encounter when reading and building component diagrams:

Component - an entity required to execute a stereotype function. A component provides and

consumes behavior through interfaces, as well as via other components. Think of components
as a type of class. In UML 1.0, a component is modeled as a rectangular block with two smaller
 rectangles protruding from the side. In UML 2.0, a component is modeled as a rectangular block
with a small image of the old component diagram shape.
Node - nodes are hardware or software objects, which are of a higher level than components.
Boxes represent nodes in Lucidchart.
Interface - show input or materials that a component either receives or provides. Interfaces can
be represented with textual notes or symbolssuch as the the lollipop, socket, and ball-and-
socket shapes.
Port - symbolized with a small square, ports specify a separate interaction point between the
component and the environment.
Package - groups together multiple elements of the system. Packages are represented by file
folders in Lucidchart. Just as file folders group together multiple sheets, packages can be drawn
around several components.
Note - this allows a developer to affix a meta-analysis to the component diagram. Notes look
like sticky notes in Lucidchart.
Dependency - shows that one part of your system depends on another. Dependencies are
represented by dashed lines linking one component (or element) to another.

State chart diagram