USE CASE SPECIFICATIONS FOR ADMIN LOGIN IN THE STOCK MAINTENANCE SYSTEM

1 Brief Description
This use case describes how Admin logins in the Stock Maintenance System

2 Actors
2.1 Admin

3 Preconditions
3.1 The Admin must be already a registered member.

4 Basic Flow of Events

1. The use case begins when the Admin selects log in the Stock Maintenance System Use Case:
Login is performed.
2. The system displays Fields to be entered.
3. The Admin enters the login data in the respective fields.
4. The system validates the details entered & displays Login success message.
5. The Use Case ends successfully.

5 Alternative Flows
5.1 If in step 3 in the basic flow the Admin enters incorrect data then the system displays and error
message and the Use Case ends in failure condition.
6 Key Scenarios
6.1 A new Admin has not registered Login Details before after taking charge.

7 Post-conditions
7.1 Successful Completion
The Admin has successfully logged in the Stock Maintenance System & the system displays Login Success
message.

7.2 Failure Condition

The logs have been updated accordingly.

8 Special Requirements

USE CASE SPECIFICATIONS FOR CHECK ADD NEW PRODUCT IN THE STOCK MAINTENANCE SYSTEM

1 Brief Description
This use case describes how Admin adds a new product in the Stock Maintenance System.

2 Actors
2.1 Admin

3 Preconditions
3.1 The Admin has logged in the Stock Maintenance System.
 4 Basic Flow of Events
1. The use case begins when the Admin has successfully logged in the Stock Maintenance System.
2. The system displays various options. See SR-xxx for full list of options.
3. In this Case the Admin always selects Manage Product Details.
4. The system displays various options. See SR-yyy for full list of options.
5. In this Case the Admin always selects Add Product. Use Case Add Product is performed.
6. The system prompts to enter Product Name.
7. The Admin enters the Product Name.
8. The system checks if the Product Name already exists.
9. The system creates a Product ID for the new Product & displays on the screen.
10. Use Case ends successfully.

5 Alternative Flows
5.1
If in the step 8 in the basic flow of events the system finds that the Product Name already exists then it
returns with a message 'Product already exists’ & displays the message & the Use Case ends in failure
condition.
6 Key Scenarios
6.1

7 Post-conditions
7.1 Successful Completion
The Admin has successfully added a new product & the system has created a Product Id & updates the
Database.

7.2 Failure Condition

The logs have been updated accordingly.

8 Special Requirements

USE CASE SPECIFICATIONS FOR EDIT PRODUCT DETAILS BY ADMIN IN THE STOCK MAINTENANCE SYSTEM

1 Brief Description
This use case describes how Edits Products Details in the Stock Maintenance System.

2 Actors
2.1 Admin

3 Preconditions
3.1 A Product Id exists for the Product.

4 Basic Flow of Events

 1. The use case begins when the Admin has successfully logged in the Stock Maintenance
System.
2. The system displays various options. See SR-xxx for full list of options.
3. In this Case the Admin always selects Manage Product Details.
4. The system prompts to enter the Product Id.
5. The Admin enters the Product Id.
6. The system displays various options. See SR-yyy for full list of options.
7. In this Case the Admin always selects Edit Product. Use Case Edit Product is performed.
8. The system displays the following fields to be edited: Edit Name, Edit Price, Edit Opening
Stock.
9. The Admin edits the required fields & selects submit.
10. The system updates the database.
11. Use Case ends successfully.

5 Alternative Flows
5.1

6 Key Scenarios
6.1

7 Post-conditions
7.1 Successful Completion
The Admin has successfully edited the Product Details and the system updates the changes in the
database.

7.2 Failure Condition

The logs have been updated accordingly.

8 Special Requirements

USE CASE SPECIFICATIONS FOR DELETE PRODUCT IN THE STOCK MAINTENANCE SYSTEM

1 Brief Description
This use case describes how Deletes a product in the Stock Maintenance System.

2 Actors
2.1 Admin

3 Preconditions
3.1 A Product Id exists for the Product.

4 Basic Flow of Events

1. The use case begins when the Admin has successfully logged in the Stock Maintenance
System.
 2. The system displays various options. See SR-xxx for full list of options.
3. In this Case the Admin always selects Manage Product Details.
4. The system prompts to enter the Product Id.
5. The Admin enters the Product Id.
6. The system displays various options. See SR-yyy for full list of options.
7. In this Case the Admin always selects Delete Product. Use Case Delete Product is performed.
8. The system displays confirmation Product Deleted.
9. The system updates the database.
10. Use Case ends successfully.

5 Alternative Flows
5.1

6 Key Scenarios
6.1

7 Post-conditions
7.1 Successful Completion
The Admin has successfully deleted the Product and the system updates the changes in the database.

7.2 Failure Condition

The logs have been updated accordingly.

8 Special Requirements

USE CASE SPECIFICATIONS FOR MANAGE PURCHASE DETAILS IN THE STOCK MAINTENANCE SYSTEM

1 Brief Description
This use case describes how Admin manages Purchase details in the Stock Maintenance System

2 Actors
2.1 Admin
2.2 Supplier

3 Preconditions
3.1 The goods supplied by the Supplier are received.
3.2 The Products received should already have a Product Id created.

4 Basic Flow of Events

1. The use case begins when the Admin has successfully logged in the Stock Maintenance
System.
2. The system displays various options. See SR-xxx for full list of options.
3. In this Case the Admin always selects Manage Purchase Details.
4. The system prompts to enter the following fields:
 A) Product Name/ Id
B) Supplier Details
C) Quantity Received
D) Price
5. The Admin enters Product Name/Id, Supplier Details, Quantity Received & Purchase Price &
clicks submit.
6. The system validates Product Id.
7. The system updates the database.
8. Use Case ends successfully.

5 Alternative Flows
5.1
If in the step 6 in the basic flow of events the system returns with a message 'Invalid Product Id', the use
case ends in failure condition.

6 Key Scenarios
6.1

7 Post-conditions
7.1 Successful Completion
The Admin has successfully entered the Purchase Details of the new inventory received & system
updates the database.

7.2 Failure Condition

The logs have been updated accordingly.

8 Special Requirements

USE CASE SPECIFICATIONS FOR MANAGE SALES DETAILS IN THE STOCK MAINTENANCE SYSTEM

1 Brief Description
This use case describes how Admin manages Sales details in the Stock Maintenance System

2 Actors
2.1 Admin
2.2 Customer

3 Preconditions
3.1 The goods sold to the Customer.
3.2 The Products should already have a Product Id created.

4 Basic Flow of Events

 1. The use case begins when the Admin has successfully logged in the Stock Maintenance
System.
2. The system displays various options. See SR-xxx for full list of options.
3. In this Case the Admin always selects Manage Sales Details.
4. The system prompts to enter the following fields:
A) Product Name/ Id
B) Customer Details
C) Quantity Sold
D) Sale Price
E) Date
5. The Admin enters Product Name/Id, Customer Details, Quantity Sold, Date of Transaction &
Sale Price & clicks submit.
6. The system validates Product Id.
7. The system updates the database.
8. Use Case ends successfully.

5 Alternative Flows
5.1
If in the step 6 in the basic flow of events the system returns with a message 'Invalid Product Id', the use
case ends in failure condition.

6 Key Scenarios
6.1

7 Post-conditions
7.1 Successful Completion
The Admin has successfully entered the Sales Details of the new transaction performed & system
updates the database.

7.2 Failure Condition

The logs have been updated accordingly.

8 Special Requirements

USE CASE SPECIFICATIONS FOR VIEW CURRENT STOCK DETAILS IN THE STOCK MAINTENANCE SYSTEM

1 Brief Description
This use case describes how Admin views current stock details in the Stock Maintenance System

2 Actors
2.1 Admin

3 Preconditions
3.1 The Product Details, Purchase Details & Sales Details are promptly updated.
3.2 The Products should already have a Product Id created.

4 Basic Flow of Events

1. The use case begins when the Admin has successfully logged in the Stock Maintenance
System.
2. The system displays various options. See SR-xxx for full list of options.
3. In this Case the Admin always selects View Stock Details.
4. The system prompts to enter the Product Name/Id.
5. The system validates Product Id.
6. The system displays various options. See SR-yyy for full list of options.
7. In this case the Admin always selects View Current Stock.
8. The system retrieves Opening Stock Data from the Product Details Database.
9. The system retrieves Quantity Data from the Purchase Details Database.
10. The system retrieves Quantity Data from the Sales Details Database.
11. The system calculates the Current stock.
12. The system displays the Current Stock.
13. The Use Case ends successfully.

5 Alternative Flows
5.1
If in the step 5 in the basic flow of events the system returns with a message 'Invalid Product Id', the use
case ends in failure condition.

6 Key Scenarios
6.1 Any of the databases are not updated.

7 Post-conditions
7.1 Successful Completion
The Admin has successfully viewed the current stock details.

7.2 Failure Condition

The logs have been updated accordingly.

8 Special Requirements

USE CASE SPECIFICATIONS FOR VIEW STOCK DETAILS BETWEEN TWO SPECIFIC DATES IN THE STOCK
MAINTENANCE SYSTEM

1 Brief Description
This use case describes how Admin stock details between two specific dates in the Stock Maintenance
System

2 Actors
2.1 Admin
 3 Preconditions
3.1 The Product Details, Purchase Details & Sales Details are promptly updated.
3.2 The Products should already have a Product Id created.

4 Basic Flow of Events

1. The use case begins when the Admin has successfully logged in the Stock Maintenance
System.
2. The system displays various options. See SR-xxx for full list of options.
3. In this Case the Admin always selects View Stock Details.
4. The system prompts to enter the Product Name/Id.
5. The system validates Product Id.
6. The system displays various options. See SR-yyy for full list of options.
7. In this case the Admin always selects View Stock between two dates.
8. The system prompts to enter ‘From Date’ & ‘To Date’.
9. The Admin enters the ‘From Date’ & ‘To Date’ & clicks submit.
10. The system retrieves Opening Stock Data from the Product Details Database.
11. The system retrieves Quantity Data for transactions between the specified dates from the
Purchase Details Database.
12. The system retrieves Quantity Data for transactions between the specified dates from the
Sales Details Database.
13. The system calculates the stock between the specified dates.
14. The system displays the Stock between the specified dates.
15. The Use Case ends successfully.

5 Alternative Flows
5.1
If in the step 5 in the basic flow of events the system returns with a message 'Invalid Product Id', the use
case ends in failure condition.

6 Key Scenarios
6.1 Any of the databases are not updated.

7 Post-conditions
7.1 Successful Completion
The Admin has successfully viewed the stock details between two specified dates.

7.2 Failure Condition

The logs have been updated accordingly.

8 Special Requirements
ACTIVITY DIAGRAM FOR STOCK MAINTENANCE SYSTEM