Scribd
Upload
37 views3 pages

Event Response Table for Product Orders

The document outlines events related to a 'Buy a Product' feature, detailing user authentication, payment confirmation, order shipping, delivery failures, and stock depletion notifications. It includes an event-response table that specifies the source, response, outcome, and exception handling for each event. Additionally, it defines derived functional requirements and business rules associated with these events to ensure system integrity and user experience.

Uploaded by

bismanadeem005
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
37 views3 pages

Event Response Table for Product Orders

The document outlines events related to a 'Buy a Product' feature, detailing user authentication, payment confirmation, order shipping, delivery failures, and stock depletion notifications. It includes an event-response table that specifies the source, response, outcome, and exception handling for each event. Additionally, it defines derived functional requirements and business rules associated with these events to ensure system integrity and user experience.

Uploaded by

bismanadeem005
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

Events for “Buy a Product” Feature

1. User Authentication Success/Failure – triggered when the email


server confirms login credentials.

2. Payment Confirmation Sent – triggered when payment gateway


sends confirmation to the email server.

3. Order Shipped – triggered when the warehouse updates the order


status to shipped.

4. Delivery Failed – triggered when the shipping carrier reports delivery


failure.

Optional / Admin Event


5. Stock Depleted Notification – triggered when an item’s inventory
reaches zero and is reported to the administrator.

Event-Response Table

Event Trigger Source Response Outcom Exception


Name e Handling

User Email External System User can If


Authenticati server Email grants access authenticati
on Success confirms Server access to dashboar on fails, lock
credential the user d account
s account after 5
attempts
and notify
user

User Email External System User Notify user


Authenticati server Email denies cannot of failure;
on Failure rejects Server access and log in suggest
credential logs password
s attempt recovery if
repeated
attempts

Payment Payment External System Order If


Confirmatio gateway Payment updates ready for confirmatio
n Sent sends Gateway order shipment n fails, retry
confirmati status to sending
on “Confirmed email; notify
” admin if
repeated
failure

Order Warehous System / System User Retry


Shipped e updates Warehou sends informed notification
order to se shipment product if fails; log
“Shipped” notification is on the error for
to user way admin

Delivery Carrier External System User Notify


Failed reports Delivery updates notified; support
delivery System order option to team if
failure status to reschedu reschedule
“Delivery le fails
Failed” delivery

Stock Inventory System / Notify Admin Log stock


Depleted reaches Warehou administrat takes depletion
Notification zero se or about action to events;
depleted restock alert if
stock repeated for
same item

Derived Functional Requirements from Events

Event Functional Requirement (FR- Business Rule


ID: Statement)

User FR1.1: The system shall grant Accounts will be


Authentication access to the user account upon locked after 5 failed
Success successful email authentication. login attempts.

User FR1.2: The system shall deny Notify user after


Authentication access and log unsuccessful multiple failed
Failure login attempts. attempts; suggest
password recovery.

Payment FR2.1: The system shall update Payment must be


Confirmation the order status to “Confirmed” verified through
Sent after receiving payment secure payment
confirmation from the gateway. gateway.

Order Shipped FR3.1: The system shall send a Notification must retry
shipment notification to the user if sending fails.
when the order is shipped.

Delivery Failed FR4.1: The system shall update Notify support team if
the order status to “Delivery rescheduling fails.
Failed” and allow rescheduling.

Stock Depleted FR5.1: The system shall notify Admin must take
Notification the administrator when an item’s action to restock;
stock reaches zero. repeated depletion
should be logged.

You might also like