UNIVERSITI TEKNIKAL MALAYSIA MELAKA

DITP3213 SOFTWARE ENGINEERING

FAKULTI TEKNOLOGI MAKLUMAT DAN KOMUNIKASI

(KURSUS : DIT)
(KOD KURSUS : DITP3213)

SOFTWARE REQUIREMENT ANALYSIS

TITLE: ADZ E-COMMERCE PROJECT

Nama No Matrik Seksyen/Kumpulan

NAMA PENSYARAH : MADAM NOR AIZA

1.1 Identification ................................................................................................................................. 2

1.2 Purpose......................................................................................................................................... 2

1.3 Scope............................................................................................................................................. 2

1.4 Use Case Diagram ....................................................................................................................... 2

1.5 Activity Diagram ......................................................................................................................... 4

2.0 USE CASE SPECIFICATION ............................................................................................ 5

2.1 Use case : Browse and Search Product Listings ....................................................................... 5

2.2 Use case : Add to cart ................................................................................................................. 7

2.3 Use case : Payment process......................................................................................................... 9

2.4 Use case : View Shipping and Tracking Details ..................................................................... 11

2.5 Use case : Profile Details ........................................................................................................... 12

APPENDIX A – ACTIVITY DIAGRAM (for each use case) ..................................................... 16

1) Use case : Login ......................................................................................................................... 16

2) Use case : Manage Order.................................................................................................................. 16

1
1.0 INTRODUCTION
1.1 Identification

System Name : ADZ E-Commerce

System Abbreviation : ADZec

1.2 Purpose

By leveraging the identified criteria from the ADZec software requirements analysis, this document aims
to articulate a detailed Use Case that aligns with the specific needs and objectives of the ADZec company,
thereby providing a comprehensive understanding of how the software can be effectively utilized within
their organizational context.

1.3 Scope

The scope of this ADZec document is to describe the various Use Case requirements and activity
diagrams used in the ADZec system. By doing so, it will provide a full overview of system operations and
workflow in a straightforward .

1.4 Use Case Diagram

The ADZec Use Case diagram serves as a visual tool that presents a comprehensive overview of
the various interactions between different actors, such as users or external systems, and the
specific functionalities offered by the ADZec system, offering a holistic understanding of the
system's behavior and the roles played by different entities within its operational context.

2
3
1.5 Activity Diagram

The ADZec activity diagram provides a visual representation of the step-by-step flow of activities,
actions, and decisions within the ADZec system, allowing stakeholders to understand the logical
progression and interdependencies of processes, enabling effective analysis and optimization of the
system's workflow.

Refer to appendix A

4
2.0 USE CASE SPECIFICATION
2.1 Use case : Browse and Search Product Listings

Actor: Customer

Decription: The process of looking through and searching for items on the ADZ E-Commerce platform is
described in this use case.

Pre-condition: The actor search the items needs.

Post-condition: The application show the result searching and actor can add to cart thier items.

Primary Flow:

1. Actors visit the product listing page on the ADZ E-Commerce platform.

2. The actor may browse the product list and examine key details such the product name, price, and
thumbnail image.

3. The actor can select to refine product listings based on certain criteria by using filters or sorting
options. , brand, or category, then click the search button.

4. Based on selected filters or sorting choices, the system refreshes the product listing.

If a client wants to look for a certain product:

a. The actor enters relevant keywords in the search bar.

b. The system does a search in the product database.

c. The system displays a list of goods that meet the search criteria.

5. After finding the item they're looking for, the consumer may click on it to discover more
information about it.

6. The programme will provide information about the product, such as its characteristics, features,
user feedback, similar items, and even costs.

7. Actor can continue to other actions or add more items to their shopping carts.

8. End usage examples.

5
Alternative Flow:

A1: Not found product filter

1. The system shows a message stating that no item is identified and the actor need to click filter
button to manage.

2. The actor needs to adjust the filter or the customer does not need to use the product filter which
causes the product not to meet the requirements .

3. After that , click search button.

4. The use case continues.

A2: Not found product at search bar

1. The actor need to go back and search

2. The actor need to search for products by using keywords that match more.After that , click search
button.

3. The use case continues.

Exception Flow:

E1: Technical issues of the searching system

1. The actor is advised to refresh the page or try accessing the product listing or search functionality
at a later time.

2. If the issue persists, the customer is encouraged to contact the customer support team for
assistance.

3. The use case ends with the actor either retrying the action later or seeking support for resolution.

E2: The product database is empty or inaccessible

1. The actor is informed that the lack of products and presents a message, such as "Apologies, no
products available for now .

2. The actor may be encouraged to check back later or explore other sections of the platform in the
meantime.

3. The use case ends.

User interface:

6
2.2 Use case : Add to cart

Actor: Customer

Decription: This use case outlines the process of adding a product to the shopping cart in the ADZ E-
Commerce platform.

Pre-condition: The actor logged to thier account and navigated to the search bar or product page of the
item they want to add to the cart.

Post-condition:

1. The selected product is added to the actor 's shopping cart.

2. The cart summary is updated to reflect the changes.

Primary Flow:

1. On the product page, the actor chooses their preferred item.

2. The system shows the item's specifications, such as its cost and availability.

3. Clicking "Add to Cart" is done by the actor.

4. The software checks if the product is indeed available.

5. The computer system includes the chosen item in the c actor 's shopping basket.

6. The total price and the number of goods in the cart are updated in the cart summary by the
system.

7. The product has been successfully added to the cart, according to the confirmation message the
system shows.

8. The use case ends.

Alternative Flow:

A1: Delete product in the cart

1. The actor select the items to delete or remove.

2. The actor drag the item to delete .

3. The actor sees a message from the system stating that the order has been deleted.

4. The use case continues.

7
A2: Update the product into the cart

1. The actor open the cart.

2. The actor selects the product that need to update.

3. The actor can update the specification or the amount of product .

4. The add to cart system will updated the product.

5. The use case continues.

Exception Flow:

E1: Unexpected system error

1 The system will display an error message .

2 The actor click the refresh button and contiunue to add to cart.

3 The use case continues.

User interface:

8
2.3 Use case : Payment process

Actor: Customer

Decription: This use case describes the process of making a payment for a purchase on the ADZ e-
commerce system.

Pre-condition:

1. The actor has added items to the shopping cart.

2. The actor has reviewed the cart and is ready to proceed with the payment.

3. The actor has selected a payment method.

Post-condition:

1. The payment is successfully processed.

2. The order status is updated to "Paid" in the system.

3. An order confirmation is displayed to the actor.

Primary Flow:

1. Actor open their carts and choose the products they want to order.

2. The actor chooses their preferred payment option from the list of possibilities.

3. The actor is forwarded to the secure payment page of the payment gateway by the system.

4. The actor inputs the necessary payment information, including online banking or PayPal login
credentials, debit or credit card information, and billing address.

5. The actor authorises payment.

6. The payment transaction is handled by the payment gateway.

7. The system receives information about the payment transaction's status from the payment
gateway.

8. The order status is changed to "Paid" by the system, and an order confirmation is generated.

9. The system shows the customer the order confirmation, together with the payment information
and order summary.

10. The system will provide updates on the actor 's order, such as when the delivery is complete.

11. The use case ends.

9
Alternative Flow:

A1: Payment method choices

1. The actor select the items to buy.

2. The actor setup the details payment

3. The actor choose the payment method .

4. If using PayPal or online banking actor need to log in thier Paypal account

5. If choose bank card actor need to fill up the card details such as debit or credit.

6. The actor sees a message from the system stating that the choice of payment method has been set.

7. Make the payment.

8. The actor sees a message from the system stating that the payment successfull.

9. The use case continues.

Exception Flow:

E1: Invalid Payment Method

1. The system will disable online banking,PayPal for while for maintainence..

2. The actor need to choose other payment method and go to payment process..

3. The use case continues.

User interface:

10
2.4 Use case : View Shipping and Tracking Details

Actor: Customer

Decription: This use case describes the process of viewing the shipping and tracking details for a
completed purchase on the ADZ e-commerce system.

Pre-condition:

1. The actor has completed the order and provided shipping details during the checkout process.

2. The order has been shipped and a tracking number has been assigned.

Post-condition:

1. The actor has viewed the shipping and tracking details for the selected order

Primary Flow:

1. The actor goes to the ADZ e-commerce system's account or order history area.

2. A list of the actor 's prior orders is shown by the system.

3. The actor chooses which order they wish to view shipment and tracking information for.

4. The system gathers and shows the recipient's name, address, contact information, and shipment
method together with the shipping data related to the selected purchase.

5. The tracking number issued to the order is also shown by the system.

6. When a actor clicks on the tracking number, they are sent to the website or tracking service of the
shipping company.

7. If connectivity with shipping providers is possible, the system may offer a choice to monitor the
tracking status immediately within the ADZ e-commerce system.

8. Actor reviews shipping and tracking information

9. The use case continues.

Alternative Flow:

A1: No Previous Orders:

1. The actor go to My Order .

2. The actor has no previous orders, it displays a message indicating that there are no orders to view.

3. The actor may need to place an order first.

11
 4. The use case terminates.

A2: No Tracking Number Available:

1. The actor open to the shipping details and get message” Tracking details are not available “.

2. The actor need to call our customer service to get the tracking number..

3. If still dont get the customer can still view the shipping details but will not be able to track.

4. The use case end.

Exception Flow:

E1: Tracking Number Format Error:

1. System identifies that the tracking number associated with the selected order is in an invalid or
unrecognized format.

2. The system displays an error message indicating that the tracking number is invalid.

3. The actor can still view the shipping details but will not be able to track the shipment until a valid
tracking number is available.

4. The use case end

User interface:

2.5 Use case : Profile Details

Actor: Customer

Decription: This use case describes the process of managing and updating profile details for a customer
on the ADZ e-commerce system.

.Pre-condition:

1. The actor has registered an account on the ADZ e-commerce website.

2. The actor is logged into their account.

Post-condition:

1. The actor has viewed profile details are updated and saved in the system.

12
Primary Flow:

1. The actor accesses the account settings or profile area on the ADZ e-commerce website.

2. The system displays the actor'scurrent profile details, which include name, email address, contact
information, and other relevant information.

3. The actor can edit any desired profile field.

4. The system checks the correctness and completeness of the new data.

5. If the validation is successful, the system saves the updated profile information.

6. The system displays a success message informing the user that their profile information has been
updated.

7. The use case continues.

Alternative Flow:

A1: Invalid Profile Information:

1. The actor visits their profile.

2. The actor sees the error notice "Invalid profile information" once the system determines that the
revised profile information is incorrect or incomplete.

3. The actor is asked to update the incorrect fields.

4. The actors must resolve the issue with re-authentication and preserve updated profile information.

5. The use case terminates.

Exception Flow:

E1: Duplicate Email Address:

1. The system recognises that the actor’s changed email address already exists in the system or
is linked to another account.

2. The system indicates that the email address is already in use in an error message.

3. The actor is requested to input a new email address or modify their current one.

4. The use case end

User interface:

13
14
Approved by :

__________________________________________ Date: ___________________

MUHAMMAD HAZIQ BIN FADHLAN FAIZAL

Project Manager

--------------------------------------------------------------------------------------------------------------------

Accepted by :

__________________________________________ Date: ___________________

ALI BIN SARIAH

MHR Classic Manager

15
APPENDIX A – ACTIVITY DIAGRAM (for each use case)

1) Use case : Login

2) Use case : Manage Order

16