use case spesification for sales management add
Post on 18-Nov-2014
111 Views
Preview:
TRANSCRIPT
USE CASE SPESIFICATION
FOR SALES MANAGEMENT
Add Sales
1.1 Brief Description
This use case will be used by administrator to add the sale data.
1.2 Pre-condition
The administrator must have username and password in order can login into the system.
1.3 Characteristic of activation
Execution depends on administrator’s demand.
1.4 Flow of events
1.4.1 Basic Flow (REQ 101) This use case will begin when the administrator clicks the “add sales” button. Then the system displays the interface for the administrator. Here, administrator has to input all of textboxes available. System can continue the process even though administrator let the textbox
empty, because there are types of products; books and stationary.
After the administrator has entered all textboxes regard to detail of sales, the administrator must press the save button. [A-1: Reset]
Next, system gets the data and saved into the database. This use case end when the system displays a page use a table with all
data saved.
1.4.2 Alternative Flow
A-1: Reset (REQ 101) The system shall clear all of the fields.
1.5 Post-condition
Administrator can search, update, delete the sale data and also can view the stock, sale, order and purchasing report entire associate to the detail of sales that have been inserted in the database.
1.6 Limitation
Not Applicable.
Search Sales
1.1 Brief Description
This use case will be used by administrator to search the detail of sale data.
1.2 Pre-condition
The administrator must have username and password in order can login into the system.
1.3 Characteristic of activation
Execution depends on administrator’s demand.
1.4 Flow of events
1.4.1 Basic Flow (REQ 101) This use case will begin when the administrator click the “search sales” button.
Then administrator must input the name of the stock. Next the administrator must press the search button. After that system will check the name of the stock that has been entered
before into the database whether the data is there or not. [E-1: the name of the stock is not in the database]
Finally this use case end by displaying a page which content all of the detail of sales data.
1.4.2 Exceptional Flow E-1: The name of the stock is not in the database The system displays an error message and then administrator must enter
the valid name of stock.
1.5 Post-condition
Administrator can add, update, delete the sale data and also can view the stock, sale, order and purchasing report entire associate to the detail of sales that have been inserted in the database.
1.6 Limitation
Not applicable.
Update Sales
1.1 Brief Description
This use case will be used by administrator to update the sale data.
1.2 Pre-condition
The administrator must have username and password in order can login into the database.
1.3 Characteristic of activation
Execution depends on administrator’s demand.
1.4 Flow of events
1.4.1 Basic Flow (REQ 101) This use case will begin when administrator click the “update sales”
button. Then the system displays a page which used to enter the name of the
stock. Next the administrator must input the name of the stock and then click
the update button. System will check the name of the stock that has been entered before,
whether the data is there or not. [E-1: the name of the stock is not in the database]
After that system displays a page which content all of the detail of sales data.
Administrator need to change the fields that want to be updated. Finally the administrator must click the update button. System will get the detail of sales data that has been edited before and
then saved into the database. This use case end when displays all of the sale data updated use a table.
1.4.2 Exceptional Flow
E-1: The name of the stock is not in the database
The system displays an error message and then the administrator mustenter the valid name of stock.
1.5 Post-condition
Administrator can add, search, delete the sale data and also can view the stock, sale, order and purchasing report all of the detail of sales that have been inserted in the database.
1.6 Limitation
Not applicable.
Delete Sales
1.1 Brief Description
This use case will used by administrator delete the sale data.
1.2 Pre-condition
The administrator must have username and password in order can login into the system.
1.3 Characteristic of activation
Execution depends on administrator’s demand.
1.4 Flow of events
1.4.1 Basic Flow (REQ 101) This use case will begin when the administrator click the “delete sales”
button. Then the system displays a page which used for input the name of the
stock. Administrator must insert the name of the stock here and then click
the delete button. System will check the name of the stock into the database whether the
data is there or not. [E-1: the name of the stock is not in the database]
After that system displays the detail of sales data before deleted. Administrator must press the delete button.
Finally system gets the detail of sales data and removed from database. This use case end when display the detail of sales data that has been
removed from database.
1.4.2 Exceptional Flow
E-1: the name of the stock is not in the databaseThe system displays an error message and then the administrator must
enter the valid name of stock.
1.5 Post-condition
Administrator can add, search, update the sale data and also can view the stock, sale, order and purchasing report entire associate to the detail of sales that have been inserted in the database.
1.6 Limitation Not applicable.
Stock Report
1.1 Brief Description
This use case will be used by administrator to view the stock report.
1.2 Pre-condition
Administrator must have username and password in order can login into the database.
1.3 Characteristic of activation
Execution depends on administrator’s demand.
1.4 Flow of events
1.4.1 Basic Flow (REQ 101)
This use case will begin when the administrator click the “stock report” button.
After pressed the “stock report” button, system gets entire of the stock data into the database.
This use case end when displays a page which content all of the stock report.
1.5 Post-condition
Administrator can add, search, update, delete the sale data and also can view the sale, order and purchasing report entire associate to the detail of sales that have been inserted in the database.
1.6 Limitation
Not applicable.
Sales Report
1.1 Brief Description
This use case will be used by administrator to view the sales report.
1.2 Pre-condition
The administrator must have username and password in order can login into thedatabase.
1.3 Characteristic of activation
Execution depends on administrator’s demand.
1.4 Flow of events
1.4.1 Basic Flow (REQ 101) This use case will begin when the administrator click “sales report”
button. After pressed the “sales report” button, system gets entire of the sale data
into the database. This use case end when displays a page which content all of the sale
report.
1.5 Post-condition
Administrator can add, search, update, delete the sale data and also can view the stock, order and purchasing report entire associate to the detail of sales that have been inserted in the database.
1.6 Limitation
Not applicable.
Order Report
1.7 Brief Description
This use case will be used by administrator to view the order report.
1.8 Pre-condition
The administrator must have username and password in order can login into the
database.1.9 Characteristic of activation
Execution depends on administrator’s demand.
1.10 Flow of events
1.4.1 Basic Flow (REQ 101) This use case will begin when the administrator click “order report”
button. After pressed the “order report” button, system gets entire of the order
data into the database. This use case end when displays a page which content all of the
order report.
1.11 Post-condition
Administrator can add, search, update, delete the sale data and also can view the stock, sale and purchasing report entire associate to the detail of sales that have been inserted in the database.
1.12 Limitation
Not applicable.
Purchasing Order
1.13 Brief Description
This use case will be used by administrator to view the purchasing report.
1.14 Pre-condition
The administrator must have username and password in order can login into thedatabase.
1.15 Characteristic of activation
Execution depends on administrator’s demand.
1.16 Flow of events
1.4.1 Basic Flow (REQ 101) This use case will begin when the administrator click “purchasing report”
button. After pressed the “purchasing report” button, system gets entire of the
purchasing data into the database. This use case end when displays a page which content all of the
purchasing report.
1.17 Post-condition
Administrator can add, search, update, delete the sale data and also can view the stock, sale and order report entire associate to the detail of sales that have been inserted in the database.
1.18 Limitation
Not applicable.
FOR PURCHASING
Add Purchasing
1.1 Brief Description
This use case will used by administrator add the purchasing data.
1.2 Pre-condition
The administrator must have username and password in order can login into the database.
1.3 Characteristic of activation
Execution depends on administrator’s demand.
1.4 Flow of events
1.4.1 Basic Flow (REQ 101) This use case will begin when the administrator click the
“add purchasing” button. Then system displays entire the textboxes that associate to add
purchasing data. Administrator has to input entire textboxes that available. System allow administrator to continue the process if there is still an empty field when the administrator click the save button. After administrator has filled in entire the fields then must press the
save button. [A-1: Reset] Next system saves the purchasing data into the database. Finally this use case end by displaying the detail of purchasing data
that has been inserted.
1.4.2 Alternative Flow
A-1: Reset (REQ 101) The system shall clear all of the fields.
1.5 Post-condition
Administrator can search, delete and update the purchasing data that has been inserted in the database.
1.6 Limitation
Not applicable.
Search Purchasing
1.1 Brief Description
This use case will be used by administrator search the purchasing data.
1.2 Pre-condition
The administrator must have username and password in order can login into the database.
1.3 Characteristic of activation
Execution depends on administrator’s demand.
1.4 Flow of events
1.4.1 Basic Flow (REQ 101)
This use case will begin when the administrator click the “search purchasing” button.
Then system displays a page in which the administrator has to input the credit card number.
Next administrator must press the search button. After that the system will checks the credit card number into the database
whether it is there or not. [E-1: the credit card number is not in the database]
This use case end when the system displays a page which content the detail of purchasing data appropriate with administrator’s request use a table.
1.4.2 Exceptional Flow
E-1: the credit card number is not in the databaseThe system displays an error message and then the administrator mustinput the valid credit card number.
1.5 Post-condition
The administrator can add, delete and update the purchasing data that has been inserted in the database.
1.6 Limitation
Not applicable.
Delete Purchasing
1.1 Brief Description
This use case will be used by administrator delete the purchasing data.
1.2 Pre-condition
The administrator must have username and password in order can login into the database.
1.3 Character of activation
Execution depends on administrator’s demand.
1.4 Flow of events
1.4.1 Basic Flow (REQ 101)
This use case will begin when the administrator click “delete purchasing” button.
Then system displays a page in which the administrator has to enter thecredit card number here.
Next the administrator must press the delete button. System will check the credit card number into the database whether it is there or not. [E-1: the credit card number is not in the database] After that the system displays a page which content the purchasing data will be deleted. The administrator must press the delete button so that the purchasing data
can be removed from the database. This use case end when the system displays the detail of purchasing data
that has been deleted use a table.
1.4.2 Exceptional Flow
E-1: the credit card number is not in the databaseThe system displays an error message and then the administrator mustinput the valid credit card number.
1.5 Post-condition
The administrator can add, search and update the purchasing data that has been inserted in the database.
1.6 Limitation
Not applicable.
Update Purchasing
1.1 Brief Description
This use case will be used by administrator update the purchasing data.
1.2 Pre-condition
The administrator must have username and password in order can login into the database.
1.3 Characteristic of activation
Execution depends on administrator’s demand.
1.4 Flow of events
1.4.1 Basic Flow (REQ 101)
This use case will begin when administrator click the “update purchasing” button.
Then the system displays a page which used to enter the credit card number.
Next the administrator must input the credit card number and then click the search button.
System will check the credit card number that has been entered before, whether it is there or not. [E-1: the credit card number is not in the database]
After that system displays a page which content entire the purchasing data.
Administrator need to change the fields that want to be updated. Finally the administrator must click the update button. System gets the detail of purchasing data that has been edited before and
then saved into the database. This use case end when displays all of the purchasing data updated use a table.
1.4.2 Exceptional Flow
E-1: the credit card number is not in the databaseThe system displays an error message and then the administrator mustinput the valid credit card number.
1.5 Post-condition
The administrator can add, search and delete the purchasing data that has been inserted in the database.
1.6 Limitation
Not applicable.
top related