Functional and non functional requirements

Our solution should fulfill both the functional and non-functional requirements adequately. The functional requirements are in this case the same as the user stories related to our Scrum-process. User stories are also sorted after sprint numbers and importance within the sprint.

Requirements

Due to changes during the project, some user stories are outdated (mentioned below). We did not restard ID-numbers when changing our backlog. Some user stories that continued to be valid kept the ID, while new user stories continued to increase from the highest number.

Functional requirements

Sprint	User Story #	Description
1	-	-
2	28	As a DP I want the API to support production data as input.
3	25	As a DG I want the system to gather, update and segment the road network and store it in the database.
	23	As a user of the system I want the production data to be correctly mapped to a road segment.
	27	As a DG I want to be able to retreive the attributes of a given road segment.
4	24	As a user I want the system to check if new production data belongs to a road with already existing production data
	29	As a DG I want to be able to see a guide and/or documentation for the api.
	31	As a user I want the system to be wrapped in a Docker container so that I easily can set up the project.
5	8	As a DG, I would like to see weather data on a given road segment.
Not included	4	As a DG, I want to specify which data attributes I want to gather from a given road segment.
Not included	26	As a DG I want to gather road segments in a given area.
Not included	30	As a DP, I want a UI to input production data.

Non-functional requirements

NFR #	Description
Testability	Provide tests for testing the product.
Documentation	It should be easy for users to understand and use our API when using our documentation
Extensibility	White-box extensibility, NPRA want the ability to edit the source code for further extensions.

Further development

Non-functional requirements

NFR #	Description
Security	Standard database security and validation.
Performance	The performance needs to be good enough to be usable in the final product.
Usability	Documentation needs to be thorough so developers can learn the system quickly.
Maintainability and Scalability	Should be simple to change data input to comply with new requirements.