Scribd
Upload
33 views12 pages

Software Lab Da-4 (21BKT0110)

The document discusses sequence diagrams, which visually represent the flow of messages between objects in a system over time. It defines sequence diagrams and explains their purpose is to model interactions between active objects and illustrate how use cases are realized through collaboration. The key components of a sequence diagram like lifelines, messages, activations, actors, and sequence fragments are described. An example online bookstore sequence diagram is provided. Benefits include exploring runtime applications and drawbacks include increased complexity with many elements.

Uploaded by

Lokesh Nuli
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
33 views12 pages

Software Lab Da-4 (21BKT0110)

The document discusses sequence diagrams, which visually represent the flow of messages between objects in a system over time. It defines sequence diagrams and explains their purpose is to model interactions between active objects and illustrate how use cases are realized through collaboration. The key components of a sequence diagram like lifelines, messages, activations, actors, and sequence fragments are described. An example online bookstore sequence diagram is provided. Benefits include exploring runtime applications and drawbacks include increased complexity with many elements.

Uploaded by

Lokesh Nuli
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Software Engineering Lab

BCSE301P

NAME: N. LOKESH
REGISTRATION NUMBER: 21BKT0110
LAB SLOT: L33+34
FACULTY NAME: POORNIMA N
Problem: Cybersecurity Threats in E-commerce Transactions

UML USE CASE DIAGRAM:


In the context of cybersecurity threats in e-commerce transactions, a Use Case Diagram
serves as a visual representation of the dynamic interactions between actors and the
system functionalities. It encapsulates the various use cases, actors involved, and their
relationships, providing a comprehensive overview of the system's behavior concerning
security in e-commerce transactions.

PURPOSE OF USE CASE DIAGRAM:

A use case diagram is a visual representation of the functional requirements of a system


from the perspective of its users (actors) and the various ways they interact with the
system. In the context of
cybersecurity threats in e-commerce transactions, a use case diagram serves several
important purposes:

HOW TO DRAW USE CASE DIAGRAM:

Drawing a Use Case diagram for cybersecurity threats in e-commerce


transactions involves identifying the actors, use cases, and their
relationships, with a focus on security aspects. Here are the steps to create
a Use Case diagram for this scenario.

Actors:

• Customer: Represents the end-user engaging in e-commerce


transactions.
• Merchant: Represents the entity providing goods or services in the e-
commerce platform.
• Administrator: Represents individuals responsible for managing and
maintaining the e-commerce system's security.
Use Cases:

Login/Authentication:

Actor: Customer
• Description: The customer logs in to the e-commerce platform, triggering
authentication processes to ensure secure access.

Transaction Processing:

Actors: Customer, Merchant


• Description: Initiates the secure processing of e-commerce transactions, involving
encryption and secure communication channels.

Payment Authorization:

Actors: Customer, Payment Gateway


• Description: Involves secure payment authorization processes, protecting
financial data during transactions.

Product Search and Listing:

Actor: Customer
• Description: Represents the secure retrieval and display of products, ensuring
data integrity and protection against tampering.

Security Patching:

Actor: Administrator
• Description: Involves applying security patches to the system to address
vulnerabilities and enhance overall security.
Account Management:

Actors: Customer, Administrator

• Description: Covers secure account creation, modification, and


deletion processes, safeguarding customer information.
Relationships:

• Association: Connects actors with relevant use cases, illustrating


their involvement in specific functionalities.
• Inheritance: Represents specialized actors inheriting
common functionalities, such as authentication processes.
System Boundary:

• Defines the boundary encapsulating the e-commerce system,


emphasizing the scope of the depicted functionalities related to
cybersecurity threats.

EXAMPLE OF USE CASE DIAGRAM:

While I can't provide a visual diagram in this text format, I can describe a
simplified textual.
representation of a Use Case Diagram for cybersecurity threats in e-
commerce transactions. Keep in mind that actual diagrams may vary in
complexity based on the specific requirements of the system. Here's a basic
example:
SEQUENCE DIAGRAM:
• Definition:
• A sequence diagram visually represents the dynamic flow of
messages in a system. It showcases the runtime participation of
elements through lifelines and messages, ordered in time sequences.

PURPOSE OF A SEQUENCE DESIGN:

• Model high-level interactions among active objects.


• Illustrate collaborations realizing use cases.
• Model both generic interactions and specific instances.

NOTATIONS OF SEQUENCE DIAGRAM

Lifeline:

• Represents individual participants with a vertical bar at the diagram's


top.
Actor:

• Represents a role played by an entity interacting with the subject. It


extends beyond the system's scope, embodying roles involving
human users or external hardware.

•
Activation:

• Shown as a thin rectangle on the lifeline, indicating the time period


during which an operation is performed.’
Messages:

• Arrows depicting interactions between objects. Types include Call


Message, Return Message, Self-Message, Recursive Message,
Create Message, Destroy Message, and Duration Message.

Note:
• Enables the attachment of remarks to elements, offering useful
information for modelers.
Sequence Fragments:

Introduced in UML 2.0, enclosed in a combined fragment box.

• Types include alt (Alternative), opt (Optional), par (Parallel), loop


(Loop), region (Critical region), neg (Negative), ref (Reference),
and sd (Sequence Diagram).
Example of a Sequence Diagram:

Scenario:
A high-level sequence diagram for an online ECOMMERECE, involving
customer actions such as searching the catalog, viewing book details, adding
to the cart, and checkout.
Benefits of a Sequence Diagram:

• Explores real-time application scenarios.


• Depicts the message flow between different objects.
• Facilitates easy maintenance and generation.
• Supports both forward and reverse engineering.
• Easily updated to accommodate system changes.

Drawbacks of a Sequence Diagram:

• Complexity increases with a high number of lifelines.


• Incorrect results may occur if the message flow order changes.
• Different notations for each sequence may complicate the diagram.
• The type of sequence depends on the message type.

Sequence diagrams, a vital component in Unified Modeling Language (UML),


offer a dynamic
perspective on system behavior, capturing the sequence of interactions
among various elements during runtime. This document provides an
extensive overview of sequence diagrams, covering their definition, purpose,
notations, examples, benefits, and drawbacks.

Introduction:
The sequence diagram is a powerful UML tool that visually represents the
order of interactions between objects within a system. This document aims
to elucidate the fundamental aspects of sequence diagrams, shedding light
on their applications, notations, and implications in system modeling.

Definition and Purpose:


Sequence diagrams, often termed event diagrams, elucidate the flow of
messages among elements during runtime. The primary purposes include
modeling high-level interactions among active objects, illustrating
collaborations realizing use cases, and representing both generic and
specific instances of interactions.

Notations:
The notations in a sequence diagram play a crucial role in conveying
information effectively. Lifelines, depicted as vertical bars, represent
individual participants. Actors, extending beyond the system's scope,
portray roles involving users or external entities. Activations, represented
by thin rectangles, indicate the time during which an operation is executed.
Messages, denoted by arrows, come in various types like Call, Return, Self,
Recursive, Create, Destroy, and Duration.

Sequence Fragments:
• UML 2.0 introduced sequence fragments, enclosed in combined
fragment boxes. These fragments, represented by operators like alt,
opt, par, loop, region, neg, ref, and SD, enhance the modelling
capability, allowing for the depiction of complex scenarios and
interactions.

Example of a Sequence Diagram:


A practical application of a high-level sequence diagram is illustrated through
an online bookshop scenario. This example involves customer actions such as
searching the catalog, viewing book details, adding to the cart, and
completing the checkout process.

Benefits and Drawbacks:


Sequence diagrams offer numerous benefits, including the exploration of
real-time applications, clear depiction of message flow, ease of
maintenance and generation, support for both forward and reverse
engineering, and adaptability to system changes. However, they come with
drawbacks such as increased complexity with many lifelines, potential for
incorrect results due to changes in message flow order, and the need for
distinct notations for each sequence.
Interaction Model

Conclusion:
In conclusion, sequence diagrams are invaluable tools in the UML toolkit,
providing a dynamic representation of system behavior. This document serves
as a comprehensive guide, offering insights into the intricacies of sequence
diagrams, from their notations to practical applications.

You might also like