User Story

As a user, I want to create my password as soon as the account is created.

Acceptance Criteria

• The user is on the Fitnesstrackerchallenge Website in its own account
• The user sees its username, 2 empty password fields and a save button
• Below the password fields the rules for the password are listed
• The user re-enters the password in the second password fields
• Both passwords must be identical before the password is saved

Dependency

#1 #2 #15

User Story

As a user, I want to be able to delete my account to stop participating on the FTC website anymore.

Acceptance Criteria

• The FTC backend get a DELETE request for the account ID
• The FTC backend deletes all API connections for this account ID
• The FTC backend deletes the account related to the ID
• The user connected to the ID is deleted from the top list

Dependency

#1 #2

FTC = FitnessTrackerChallenge

User Story

As a user, I want the fitness data to get updated in a regular rhythm, to keep the top list current.

Acceptance Criteria

• The FTC backend triggers a GET request to gather the fitness data from the fitness tracker API
• The data are assigned to the ID of the user

Dependency

#1 #2 #4

User Story

As a user, I want to see the fitness data from each device to be able to compare them.

Acceptance Criteria

• The user is logged in into the FTC website
• The main website shows all selected fitness tracker and the kind of fitness data saved in cards
• The user selects the kind of fitness tracker
  • The user selects the kind of fitness data to see the data in a line graph from the selected fitness tracker
• The user selects the kind of fitness data
  • The user can change the fitness tracker on the site presenting the last selected fitness tracker
  • The connected fitness trackers are visible, the current one is marked

Dependency

#1 #2 #9 #7

FTC = FitnessTrackerChallenge

User Story

As the administrator, I want the FTC backend to include the step count for the top list from only one connected fitness tracker to avoid incorrect values.

Acceptance Criteria

• Multiple Fitness Tracker (at least 2) are connected
• The step data from the connected fitness tracker with the highest value is considered to create the top list
• Only 1 data set from 1 connected fitness tracker is included in the top list

Dependency

#9 #8

FTC = FitnessTrackerChallenge

User Story

As a user, I want to see in a top list of the step count on which place I am compared to all users of the FTC Website to know my fitness state in comparison.

Acceptance Criteria

• The user is logged in into the FTC website
• The step data from all users are listed from lowest to highest step count
• The step data are related to the username of each person
• The user opening the top list is marked in the list by a lightning bar

Dependency

#1 #2 #4 #5 #7 #16

FTC = FitnessTrackerChallenge

User Story

As a user, I want to connect my fitness tracker on my account on the website.

Acceptance Criteria

• The user is logged in into its account
• The user opens the tab fitness tracker connection
• All tracker brands are loaded
• The user selects its brand
• The user is redirected to the fitnesstracker brand page and forced to log in
• The user must allow the FTC website to gather data by ticking a checkbox
• The FTC backend get a put request to connect to the fitness tracker API to gather the data

Dependency

#1 #2

FTC = FitnessTrackerChallenge

User Story

As the administrator, I want the FTC backend to get the request from activated verification token to create the account.

Acceptance Criteria

• The user must confirm the account by clicking on this link
• The website backend gets the request and creates the account
  • ID
  • Username
  • Name
  • Surname

Dependency

#1 #13 #2

FTC = FitnessTrackerChallenge

User Story

As a user, I want to be able to connect multiple fitness trackers, so that I can participate with each of them.

Acceptance Criteria

• The user can connect multiple fitness trackers
• Multiple fitness trackers are connected to the user ID
• The FTC backend triggers GET requests to each connected fitness tracker API to gather the fitness data

Dependency

#1 #2 #4 #7

FTC = FitnessTrackerChallenge

User Story

As the administrator, I want the FTC backend to gather data from the connected fitness tracker’s API in a regular rhythm to ensure the currency of the top list.

Acceptance Criteria

• The FTC backend triggers a GET request to the connected API every 10 minutes
• The data are saved per user ID in the database
• The data for step count appear in a top list from lowest to highest with the username, the number of steps and the place number

User Story

As the administrator, I want that users create their accounts receive a verification token, to avoid spam data in the database.

Acceptance Criteria

• The user registers with its email address and a username
• The username field must be filled in
• The username must be unique
  • If the username is not unique, the account cannot be created and the user is informed directly by a notification that the username already exists
• The email address must be in the correct format [email protected]
• The email address must be unique
  • If the email address is not unique, the account cannot be created and the user is informed directly by a notification that the email address already exists
• The website backend creates the account with an ID
• The ID must be unique
• A verification token is created
• The verification token and its value are sent to the user via email

Dependency

#1

FTC = FitnessTrackerChallenge

User Story

As the administrator, I want to set clear password rules to increase the security of the account data.

Acceptance Criteria

• A password must consist of at least 8 characters.
• A password can contain 64 characters in maximum length.
• All characters from ASCII are allowed.
• The password must contain:
  • at least 1 number
  • at least 1 capital letter
  • at least 1 special character (e.g. /&%$§"!?...)

User Story

As a user, I want to update my fitness data on the FTC website with each log in to see the current data.

Acceptance Criteria

• The login triggers a GET request on the FTC backend to gather the data from the connected fitnesstracker API
• The fitness data are updated

FTC = FitnessTrackerChallenge

Dependency

#1 #2 #4

User Story

As a user, I want to register to the Reply FitnessTrackerChallenge Website to create my own account.

Acceptance Criteria

• The user registers with its email address and a username
• The username field must be filled in
• The username must be unique
  • If the username is not unique, the account cannot be created and the user is informed directly by a notification that the username already exists
• The email address must be in the correct format [email protected]
• The email address must be unique
  • If the email address is not unique, the account cannot be created and the user is informed directly by a notification that the email address already exists
• The website backend creates the account with an ID
• The ID must be unique
• A verification token is created
• The verification token and its value are sent to the user via email

User Story

As a user, I want to be able to disconnect a fitness tracker, if it is not used anymore.

Acceptance Criteria

• The user disconnects the fitness tracker on the FTC website
• The FTC backend does not trigger any GET requests to the disconnected fitness tracker API anymore
• The FTC backend deletes the connection to this fitness tracker API

Dependency

#1 #2 #4

FTC = FitnessTrackerChallenge

User Story

As a user, I want to see my fitness data on the FTC Website to know my fitness level.

Acceptance Criteria

• The user is logged in into the FTC website
• The main website shows the kind of fitness data saved in cards
• The user selects the kind of fitness data to see the data in a line graph

Dependency

#1 #2 #4

FTC = FitnessTrackerChallenge

User Story

As a user, I want to confirm the account creation, to close the account creation.

Acceptance Criteria

• The user must confirm the account by clicking on the verification token link in the email
• The website backend gets the request and creates the account
• The user is directed to its new account to create its password
• If the verification token is not correct, the user is redirected to an error page

Dependency

#1 #13