DESIRED OUTCOME
--
As an end-user I want to be able to have a batch report for each production,
that have happened. The batch report includes:
Graph over temperature
Graph over humidity
Graph over vibration
Graph over state
Amount to produce
Products per minute
Produced
Acceptable products
Rejected products
Overall Equipment Effectiveness
Batch report is a interactive history page
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_DST_xx
Requirement(so)
Rae
Preconditions
The system should have produced some batch reports.
Test Steps
Click to see a specific batch report.
Expected Output
The system should show the batch report from the selected report and show the information mention above
DEFINITION OF DONE
The Definition of Done describes the different steps to be completed to ensure
the product/solution increment is completed.
[ ] Acceptance Criteria Defined
[ ] Test(so) 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.
The batch report will be displayed on the history page on the website.
The data for the history page is fetched from the database using a HTTP GET
request to the relevant API endpoint.
The JSON above is an array of batches that have been produced and stored in the
database. The array is then used to make a list on the history page, from there
you can. Click on one item on the list you want to see.
On click it will then go ahead and fetch data over time with batch_id as
argument for the API endpoint. The batch_id comes from the earlier fetch done
above. GET /data_over_time/{batch_id}
REQUIREMENT
--
DESIRED OUTCOME --
As an end-user I want to be able to have a batch report for each production, that have happened. The batch report includes:
Batch report is a interactive history page
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 will be displayed on the history page on the website. The data for the history page is fetched from the database using a HTTP GET request to the relevant API endpoint.
GET /batches/
will return the following:The JSON above is an array of batches that have been produced and stored in the database. The array is then used to make a list on the history page, from there you can. Click on one item on the list you want to see.
On click it will then go ahead and fetch data over time with
batch_id
as argument for the API endpoint. Thebatch_id
comes from the earlier fetch done above.GET /data_over_time/{batch_id}
The JSON above is an array of "data over time" that have been produced. The data is then used to show a graph over:
There is also other data points that shows it total: