DESIRED OUTCOME
--
As an end-user I want to be able to control the machine from the dashboard, this includes being able to start, stop, clear and reset.
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)
R01
Preconditions
The brewing process is currently running and I am viewing the production page
Test Steps
Click the stop button.
Expected Output
The system comes to a pause at the next convenient moment.
Test Case ID
S4G1_TST_xx
Requirement(s)
R01
Preconditions
The brewing process is currently paused (as a result of pressing the stop button) and I am viewing the production page
Test Steps
Click the start button.
Expected Output
The system continues the brewing process.
Test Case ID
S4G1_TST_xx
Requirement(s)
R01
Preconditions
The brewing process is currently not running and I am viewing the production page
Test Steps
Click the start button.
Expected Output
User is redirected to the new production page.
Test Case ID
S4G1_TST_xx
Requirement(s)
R01
Preconditions
The brewing process is currently running and I am viewing the production page
Test Steps
Click the abort button.
Expected Output
System halts immediately.
Test Case ID
S4G1_TST_xx
Requirement(s)
R01
Preconditions
The brewing process is currently paused (as a result of pressing stop) and I am viewing the production page
Test Steps
Click the clear button and then the start button.
Expected Output
System should be cleared and as a result, the user will be redirected to the new production page.
Test Case ID
S4G1_TST_xx
Requirement(s)
R01
Preconditions
The brewing process is currently running and I am viewing the production page
Test Steps
Click the reset button and then the start button.
Expected Output
The system should start brewing the same production again from scratch.
DEFINITION OF DONE
The Definition of Done describes the different steps to be completed to ensure the product/solution increment is completed.
[x] Acceptance Criteria Defined
[ ] Test(s) Passed
[ ] The story is deployed and demonstrated on development target
SOLUTION DESCRIPTION
The solution description describes how we expect to implement a solution that satisfies the desired outcome of the user story.
In order to implement this story we need the following:
On the dashboard, there should be a button for each command, that sends an HTTP request to the relevant API endpoint.
This request is a PUT HTTP request:
PUT /commands/batch
{
"command": "start",
"batch_id": "some uuid"
}
Where the command is the type of command start, stop, reset and so on. And the batch_id optional, if left out the most recent batch is specified.
The API will then forward this request internally to the OPC-UA client.
REQUIREMENT
--
DESIRED OUTCOME --
As an end-user I want to be able to control the machine from the dashboard, this includes being able to start, stop, clear and reset.
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.
In order to implement this story we need the following: On the dashboard, there should be a button for each command, that sends an HTTP request to the relevant API endpoint.
This request is a PUT HTTP request: PUT /commands/batch
Where the
command
is the type of commandstart
,stop
,reset
and so on. And thebatch_id
optional, if left out the most recent batch is specified.The API will then forward this request internally to the OPC-UA client.