Specification document for online shopping system

Description :this describes how customer going to shop online.

Use-case:-search for customer online.
Actors:-telephone agent.
Precondition:-system should be ups and available, items should be present online.
Flow of events:-
1. telephone agent search for customer order and details.
2. Telephone agent will use Oder registry and customer catalogue.
3. Oder placed.
Alternate flows:-
1. Customer can shop as guest without registering
2. Customer phone number is incorrect.
3. System is down, error message get displayed.
4. Customer can cancel the transaction.
5. Telephone agent login is failed.
Post-conditions:-
1. customer will placed the order.
2. Telephone agent uses order registry and customer catalogue to obtain
accesses to an order.
3. Oder consists of Oder item and number and time.
4. Customer complete the payment.
5. Once oder placed sms/email will be generated.
Use-case:-2 Oder registry and customer catalogue
Actors:-Telephone agent
Precondition:-system should be up and available, item should present in online.
Flow of events:-
1. Telephone agent search foe customer order details.
2. Telephone agent will check the order registry.
3. Telephone agent will see all oder details of customer.
4. Telephone agent will send sms/email to customer.
Alternate flows:-
1. Customer will order and again he can cancel the oder.
2. Customer update details incorrectly.
3. Customer want to cancel the oder.
4. Telephone agent not able to find the customer oder details in oder registry.
5. Telephone agent system will hangups while checking the order registry.
Post-condition:-
1. Customer details are registered in online shopping system.
2. Telephone agent search the details in oder registry and customer catalogue.
Use-case:-3 oder placed
Actors:-telephone agent
Precondition:-system should be up and available, item should present in online.
Flow of evnets:-
1. Telephone agent will open online shopping system
2. Telephone agent search for customer oder and details.
3. Telephone agent will check oder no. And time in customer catalogue and
oder registry.
4. Admin will maintain oder registry and customer catalogue with addition,
deletion and modification time to time.
Alternate flows:-
1. Customer will not able to find the product.
2. Customer not able to open the online shopping website because of no
network.
3. If system is down.
4. Customer cancel the selected item.
5. Customer cancel at the transaction page.
Post-condition:-
1. customer is successfully order placed.
2. Telephone agent can easily search for customer details in customer catalogue
and oder registry.
Use-case:-4 payment
Actors:- telephone agent
Precondition:-system should be up and available, item should present in online.
Flow of events:-
1. Telephone agent asks for mode of payment.
2. Customer choose payment type.
3. Telephone agents selects the payment method.
4. Telephone agent makes the payment.
5. Oder placed.
Alternative flows:-
1. Customer choose to pay by combination of 3 methods
2. If customer choose to pay by card but enters the pin wrong.
3. If customer choose to pay by cash but cash is insufficient.
4. If customer enter the password 3 times but card is blocked.
Post-condition:-
1. payment is done.
2. Order is placed.
Use-case:-5 sms/email are generated
Actors:-system clock
Precondition:system should be up and available, item should present in online.
flow of events:-
1. Telephone agent will search for customer details
2. Telephone agent check for oder registering and customer catalogue
3. Oder is placed
Alternative flows:-
1. If system stops working, cant generate sms/email on successful oder
commit/cancel.
Post-conditions:-
1. Oder palced.
2. System will generate sms/email on successful oder commit/cancel.
activity oss.vsd user case -
OSS.vsd
 Activity diagram for online
shopping system

telephone agent access to an order customer visit the site

sms or email genrated by system clock

customer registration

oder registry customer catalogue

select the item

oder number customer name and ph.no

add other item cancel the item

customer oder details

item no, quality and unit price

conformation cancel

total price will show

payment process

order no. and time

 Online shopping system
-End15
oder registry
«uses»
*
-End29
*
search customer
order details «uses»
-End17 -End16
-End18
-End2 customer catalogue -End31
*
* **
*

admin
«uses»
-End6 oder no.
oder registry

*
-End21
-End1 -End5 «uses» customer name -End32 -End30
*-End7 -End22
*
-End9 -End8 * -End26
-End24
-End3
** customer catlogue «uses» *
* *-End11 *
* * customer ph. no **

item no. unit price quantity -End25

telephone agent «uses» «uses»«uses» database
oder no.
-End10 «uses» *
oderplaced -End23
* «uses»
oder time
*
-End4
*

oder cancel/commit

-End12
*

payment

-End13 -End14
sms/email will be
generated
* *

system clock