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.

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	are neat
	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.