0% found this document useful (0 votes)
4 views

EXP4.SE

The document outlines various UML diagrams for the Trendy Threads Online Store, including Use Case, Sequence, Activity, and Collaboration diagrams. Each diagram illustrates the interactions between users and the system, detailing the actions users can perform and the flow of operations. The purpose of these diagrams is to aid in understanding system features, processes, and component interactions for effective implementation.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views

EXP4.SE

The document outlines various UML diagrams for the Trendy Threads Online Store, including Use Case, Sequence, Activity, and Collaboration diagrams. Each diagram illustrates the interactions between users and the system, detailing the actions users can perform and the flow of operations. The purpose of these diagrams is to aid in understanding system features, processes, and component interactions for effective implementation.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

EXPERIMENT-04

1. USE CASE DIAGRAM:

A Use Case Diagram represents the interactions between different users (actors) and
the system. It shows what actions users can perform without detailing how the system
implements them.

Key Components:
 Actors: Represent users or external systems that interact with the system.
 Use Cases: Specific actions or functions the system provides.
 Relationships: Connections between actors and use cases (association, include, extend).

Use Case Diagram for Trendy Threads Online Store:


 Actors:

o Customer (Registers, browses products, adds items to cart, makes a purchase)


o Admin (Manages inventory, views analytics, processes orders)
o Guest User (Can browse products but needs to register for purchase)

 Use Cases:
o Browsing Products
o Searching & Filtering
o Adding to Cart
o Making a Secure Payment
o Managing Orders (Admin)
o Managing Products (Admin)

Purpose: This diagram helps in understanding what features need to be implemented


and how users interact with the system.
2. Sequence Diagram
Definition:

A Sequence Diagram shows the step-by-step flow of interactions between users and
system components over time.

Key Components:

 Actors: Users or systems interacting with the application.


 Objects: The parts of the system involved in processing requests.
 Messages: Arrows that represent communication between actors and
objects.
 Lifelines: Vertical dashed lines representing the lifetime of an object.

Sequence Diagram for Trendy Threads Online Store


(Placing an Order):

1. The Customer selects products and adds them to the cart.


2. The Web Application retrieves product details from the Database.
3. The Customer proceeds to checkout.
4. The Web Application sends a payment request to the Payment Gateway.
5. The Payment Gateway confirms the transaction.
6. The Web Application updates the Database with order details.
7. The Customer receives an order confirmation.

Purpose: Helps developers understand the flow of operations and ensure correct
implementation of order processing.
3. Activity Diagram
Definition:

An Activity Diagram visualizes the flow of activities (processes) within the system,
including decisions and loops.

Key Components:
 Start & End Nodes: Represent the beginning and end of the process.
 Actions: Tasks performed by the system or user.
 Decisions: Conditions that determine different execution paths.
 Loops: Represent repeated actions.

Activity Diagram for Shopping Process:

1. Start
2. Customer browses products
3. Search & filter products
4. View product details
5. Decision: Add to cart?
o Yes → Add to cart and continue shopping or checkout.
o No → Continue browsing.

6. Proceed to checkout
7. Enter payment & shipping details
8. Confirm Order
9. Process Payment
10. Order successfully placed
11. End

Purpose: Helps visualize the decision points and flow of activities in the system

4. Collaboration Diagram
Definition:

A Collaboration Diagram (also called Communication Diagram) shows how


objects in a system interact with each other to accomplish a process.

Key Components:
 Objects: Represent system components.
 Links: Connections between objects.
 Messages: Arrows with numbered labels showing the sequence of communication.
Collaboration Diagram for Order Placement:

1. Customer requests a product.


2. Web Application fetches details from Database.
3. Customer adds the product to the cart.
4. Web Application updates the cart in Database.
5. Customer proceeds to checkout.
6. Web Application sends payment request to Payment Gateway.
7. Payment Gateway confirms the transaction.
8. Web Application updates Database with order details.
9. Web Application sends order confirmation to Customer.
10. Purpose: Helps understand how different system components collaborate to complete a
process.

DONE By:
Anitha .A - BU22CSEN0101001
Hareesa.K - BU22CSEN0100409
Sreekar.K - BU22CSEN0101143

You might also like