Walktober is a yearly fitness challenge at PSU and this project is to design a software platform for it. The platform is modern, responsive, improved design and analytics and simplified configuration. Let's create the best Walktober experience!
As a user I want to be able to calculate the number of steps that I have completed, such that I can know what number of steps to enter for manual recording.
We want to imbed a calculator function in the manual logging view so that users can identify how many steps they have done with some input. This will be done to make it easier for users to know how many steps they have completed with just rough estimations. This will also require a some text to inform ranges of pace etc. Thus, this is somewhat of a subcategory or subtask within the manual logging view. It can be further divided into two tasks, function, and display. Though for this purpose I have grouped them, as they are both small in size and in scope.
Acceptance Criteria:
[ ] Two fields provided for the pace and for the time spent walking
[ ] Example text in the field and some examples for the number of steps pacing, and time. Such as 2.0 – 3.0 mph = walking pace, 2.5 mph for 30 minutes = x steps.
[ ] Calculate button sends the data to function that will return 0 to indicate error else, returns the number of steps.
[ ] On error or incorrect input an error message will appear to inform the user. With detailed account of the error. Such as negative time entered, or negative time etc.
As a user I want to be able to calculate the number of steps that I have completed, such that I can know what number of steps to enter for manual recording.
We want to imbed a calculator function in the manual logging view so that users can identify how many steps they have done with some input. This will be done to make it easier for users to know how many steps they have completed with just rough estimations. This will also require a some text to inform ranges of pace etc. Thus, this is somewhat of a subcategory or subtask within the manual logging view. It can be further divided into two tasks, function, and display. Though for this purpose I have grouped them, as they are both small in size and in scope.
Acceptance Criteria:
[ ] Two fields provided for the pace and for the time spent walking
[ ] Example text in the field and some examples for the number of steps pacing, and time. Such as 2.0 – 3.0 mph = walking pace, 2.5 mph for 30 minutes = x steps.
[ ] Calculate button sends the data to function that will return 0 to indicate error else, returns the number of steps.
[ ] On error or incorrect input an error message will appear to inform the user. With detailed account of the error. Such as negative time entered, or negative time etc.