User specification document for stock maintenance

Use case:-1product details:-

Actors:-administrator

Description:-the use case explains about the product details

Precondition:-

1. Active network should available

2. Admin should login to the stock maintenance system to know about the product details

Basic flow:-

1. Admin should have valid user id and password

2. Admin a will login into system

3. Enter the product id

4. Admin will know the product details

Alternate flows:-

1. Admin will enter the wrong password, system should prompt the message

2. Admin enter the wrong product id

3. Product is not exists in the system

Post condition:-

1. Customer will place the order

2. Update modification

Use case:-2purchase details

Actors:-admin

Description:-this use case explains about the product details

Precondition:-

1. Active network should available

2. Admin should login into the system to know about the purchase details

Basic condition:-

1. The system requests that the admin specify the function he/she would like to perform

2. Once the admin provides the required information,one of the sub flow executed

3. If the admin selected delete purchase order then the sub flow executed

Alternate flow:-

1. Purchase Oder details not found

If the change order sub flow, the purchase order with specified id number does-not exist, the
system displayed error message can enter a different number
 1. If the delete purchase order sub flow the admin decided not to delete the purchase order,the
delete is canceled and basic flow is started at beginning

Post condition:-

1. If the use case is successful, the admin makes the purchase order else system is unchanged

2. Update the modifications

Use case:-3 sales details

Actors:- administrator

Description:- the use case describes about sales details

Precondition:-

1. Active network should available

2. Admin should login to system with valid username and password

Basic flow:-

1. The system requests that the admin specify the function he/she would like to perform

2. Once the admin provides the required information,one of the sub flow executed

3. If the admin selected delete purchase order then the sub flow executed

Alternate flow:-

1. Sales details are not found, product id is entered wrong, the system should displayed the
message

2. If the sales of the customer details are deleted, admin not to delete customer details,the
delete option is cancelled and base flow is started at begging

Post condition:-

1. If the use case is successful, the admin makes the sales of customer details else the system is
unchanged

Use case:-4 stock details

Actor:-admin

Description:-the use case describes about the stock details

Precondition:-

1. Active network should be available

2. Admin should login to the system

Basic flow:-

1. The system requests that the admin specify the function he/she would like to perform

2. Once the admin provides the required information,one of the sub flow executed

3. If the admin selected stock details then the sub flow executed

Alternate flow:-

1. Admin not able to see stock details in the system because stock details not entered in the
system
 2. Stock details are incorrect

3. Stock is completed so system should displayed the message

Post condition:-

1. If the use case is successful the admin will see the stock details

2. Update the modifications

sm activity.vdx sm uc.vdx