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

Functional requirements

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

Non-functional requirements

NFR #	Description
1	Use the design guidelines from the customer, staying consistent and giving it an SVV identity
2	Access from both computers and phones. This could be realized by implementing it as a website.
3	The resulting system should be easy to maintain and develop since it could continue development after the end of our project. Therefore code should be commented and documented thoroughly.
4	The solution should be scalable for availability and uptime.
5	The solution should be based on renowned standards and technologies that are easy to document and use.
6	The solution should implement already developed architecture/software components where we see fit.
7	The solution should satisfy "Forskrift om universell utforming av IKT-systemer"
8	The solution should have an acceptable responsiveness
9	The solutions should be easily recovered and/or restarted if struck by error
10	The solution should have a uniform technological foundation for all developers involved.
11	The solution should strive for an availability of 99%.

---

Initial requirements now obsolete

Functional requirements

Sprint	User Story #	Description
1	3	As a user, I want to see a color-based map that allows me easily see the condition of a given road segment.
	2	As a user, I want to see the last time a road segment was maintained.
2	8	As a user, I would like to see weather conditions that might influence (or have influenced) the road conditions.
	5	As a user, I want to plot a route to my destination and see information about the road conditions on that route.
	6	As a user, I would like to provide feedback on a given road segment, in order to document shortcomings on my travel path.
	9	As a user, I would like to show and hide feedback from other users.
3	11	As an admin, I would like a dashboard to digest and handle feedback information.
	4	As a user, I want to see what kind of maintenance has been completed on a given road segment.
	14	As a user, I would like to be able to see where I am on the map.
	1	As a user, I would like to be able to register and log in to the system.
4	15	As a user, I would like to be able to favorite roads and routes, so that I can easily access my frequent roads and routes.
	12	As an admin, I would like to be able to moderate crude feedback.
	21	As a user, I want to be able to report crude and inappropriate user feedback.
	17	As a user, I would like to give feedback an importance rating
	7	As a user, I would like to comment on feedback from other users.
5	13	As a user, I would like to view user feedback as a heatmap, to intuitively see where users report that road conditions are consistently poor.
	16	As a user, I would like to get information about my favorite roads as notifications and/or daily digests.
	18	As a user, I would like to adjust the feed of notifications I receive.
	10	As a user I would like to filter roads based on my means of transportation.

Non-functional requirements

NFR #	Description
1	Use the design guidelines from the customer, staying consistent and giving it an SVV identity
2	Access from both computers and phones. This could be realized by implementing it as a website.
3	The resulting system should be easy to maintain and develop since it could continue development after the end of our project. Therefore code should be commented and documented thoroughly.
4	The solution should be scalable for availability and uptime.
5	The solution should be based on renowned standards and technologies that are easy to document and use.
6	The solution should implement already developed architecture/software components where we see fit.
7	The solution should satisfy "Forskrift om universell utforming av IKT-systemer"
8	The solution should have an acceptable responsiveness
9	The solutions should be easily recovered and/or restarted if struck by error
10	The solution should have a uniform technological foundation for all developers involved.
11	The solution should strive for an availability of 99%.