Scribd
Upload
82 views

Sequence To Activity Diagram Example

This document provides three examples of sequences of use cases and their corresponding activity diagram models. Each sequence describes interactions between actors and system classes. The activity diagrams illustrate the workflow for each use case, showing the steps, decisions, and results. Partitions in the diagrams represent objects from class diagrams. The diagrams begin with a start node and end with an end node, with arrows connecting the steps in between.

Uploaded by

hend osama
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
82 views

Sequence To Activity Diagram Example

This document provides three examples of sequences of use cases and their corresponding activity diagram models. Each sequence describes interactions between actors and system classes. The activity diagrams illustrate the workflow for each use case, showing the steps, decisions, and results. Partitions in the diagrams represent objects from class diagrams. The diagrams begin with a start node and end with an end node, with arrows connecting the steps in between.

Uploaded by

hend osama
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Sequence to activity diagram example

1) Sequence of the use case: Place order


The actor "customer" calls an instant from the class order to place an order. The class "order"
calls an instant from the class "inventory" to check the availability of the material, and the
class "inventory" will reply with the materials available. Moreover, the class "order" will call
an instant to itself (self-message) to place the customer order, and the class "order" will reply
with the status of the operation to the customer by placing the order.

The activity diagram model:


Operation: Place order
Actor: Customer
Description of the activity:
This activity diagram illustrates the workflow of a business use case that represents a
customer order. In this case, the partitions represent objects in the class diagram. The black
node represents the start of an activity. Firstly, the customer will enter the desired order
details. Once the customer submits the details of the order, the system will check if there
are available materials or not. If there are enough materials, the customer will submit the
order, and the system will display an order template for the customer. If there are no
enough materials, then the customer will have to re-enter the quantity desired of the
products that he is looking for. Finally, the black node in the end represents the end of an
activity.
2) Sequence of the use cases: Check products available, generate sales order
(generate sales order use case is include to check products available use case)
The sales department actor will call an instant from the class "product" to view the products
available. Moreover, the product class will reply with the product list available. Then, the
sales department actor will call another instant from the class "sales order" to generate
sales orders, and the class will reply with the status of the operation by generating the sales
order.

The activity diagram model:


Operation: check products available, generate sales order, generate
purchase order, confirm purchase order, send purchase order to vendor
Actor: Sales department, Purchasing department
Description of the activity:

This activity diagram illustrates the workflow of a business use case that represents a creation
of a sales order, and a purchase order. In this case, the partition represents an object in the
class diagram. The black node represents the start of an activity. Firstly, the sales department
will check if there are enough products in the warehouse or not. If there are available
products, the sales department will generate a sales order by displaying the sales order format
to enter the details, and ending with displaying the sales order template to be issued. If there
are no available products in the warehouse, the sales department will generate a purchase
order by displaying the purchase order format and entering the order details, ending with
displaying the purchase order template, and sending the purchase order to the vendor vie
email. Finally, the purchasing department will confirm the purchase order. The black node in
the end represents the end of an activity.
Sequence of the use case: Generate barcode sequence, print barcode
The "store keeper" actor will call an instant from the class "barcode" to generate a unit
barcode sequence. The class "barcode" will reply with the status of the operation by
generating a barcode sequence. The "storekeeper" actor will call another instant from the
class "barcode" to print the barcode sequence generated, and the class "barcode" will reply
with the status of the operation by printing the barcode sequence.

The activity diagram model:


Operation: Generate barcode, print barcode
Actor: Store keeper
Description of the activity:
This activity diagram illustrates the workflow of a business use case that represents a
creation of a barcode sequence, and printing a barcode sequence. In this case, the partition
represents an object in the class diagram. The black node represents the start of an activity.
Firstly, the system will display a screen format for the storekeeper that he will enter the
barcode information on. Moreover, the storekeeper will submit the barcode sequence
information by generating the barcode, and then he will print the barcode sequence
submitted. The black node in the end represents the end of an activity.

You might also like