REQUIREMENT
| ID |
Requirement |
| R03 |
Manage Batches |
DESIRED OUTCOME
As an end-user I want to be able to track the produced batches, and other relevant data, such as inventory status, batch reports, etc.
ACCEPTANCE CRITERIA
A story can cover multiple requirements and aims to describe the desired outcome that meets the expectations of the requirement(s). The acceptance criteria are the agreed measure to prove the story is functionally complete and indirectly proving the requirements are met.
| Test Case ID |
S4G1_TST_xx |
| Requirement(s) |
R03 |
| Preconditions |
Preselect which batch the machine is going to be producing, on the production page. |
| Test Steps |
Click on Recipe and Start |
| Expected Output |
The system starts making the preselected batch if the necessary ingredients are available. |
| Test Case ID |
S4G1_TST_xx |
| Requirement(s) |
R03 |
| Preconditions |
The brewing is stopped, and you are looking at the production page. |
| Test Steps |
Click the View Batches |
| Expected Output |
Batches reports is now showing, and can then be clicked on, for further analysis. |
DEFINITION OF DONE
The Definition of Done describes the different steps to be completed to ensure the product/solution increment is completed.
SOLUTION DESCRIPTION
The solution description describes how we expect to implement a solution that satisfies the desired outcome of the user story.
The batch report history will be displayed on the website. The data is fetched from the database using a HTTP GET
request to the relevant API endpoint.
GET /batches/ will returns.
{
"speed": 189,
"started_dt": "2021-01-17T14:14:48.392470+00:00",
"amount_to_produce": 100,
"recipe_id": "Pilsner",
"finished_dt": "2021-01-17T14:15:20.135025+00:00",
"oee": 29.295000000000005,
"identifier": 7
},
{
"speed": 200,
"started_dt": "2021-01-17T14:04:31.460101+00:00",
"amount_to_produce": 100,
"recipe_id": "Pilsner",
"finished_dt": "2021-01-17T14:12:52.279874+00:00",
"oee": 29.333333333333332,
"identifier": 6
}The array shows the produced and stored batches in the database. With the array, a list can be made so the batch history can then be displayed on the website. The list can then show more about a specific batch if clicked.
REQUIREMENT
DESIRED OUTCOME
As an end-user I want to be able to track the produced batches, and other relevant data, such as inventory status, batch reports, etc.
ACCEPTANCE CRITERIA
A story can cover multiple requirements and aims to describe the desired outcome that meets the expectations of the requirement(s). The acceptance criteria are the agreed measure to prove the story is functionally complete and indirectly proving the requirements are met.
DEFINITION OF DONE
The Definition of Done describes the different steps to be completed to ensure the product/solution increment is completed.
SOLUTION DESCRIPTION
The solution description describes how we expect to implement a solution that satisfies the desired outcome of the user story.
The batch report history will be displayed on the website. The data is fetched from the database using a HTTP GET
request to the relevant API endpoint.
GET /batches/will returns.{ "speed": 189, "started_dt": "2021-01-17T14:14:48.392470+00:00", "amount_to_produce": 100, "recipe_id": "Pilsner", "finished_dt": "2021-01-17T14:15:20.135025+00:00", "oee": 29.295000000000005, "identifier": 7 }, { "speed": 200, "started_dt": "2021-01-17T14:04:31.460101+00:00", "amount_to_produce": 100, "recipe_id": "Pilsner", "finished_dt": "2021-01-17T14:12:52.279874+00:00", "oee": 29.333333333333332, "identifier": 6 }The array shows the produced and stored batches in the database. With the array, a list can be made so the batch history can then be displayed on the website. The list can then show more about a specific batch if clicked.