FA2 Technical Proposal

FA2 Technical Proposal

1. Task Requirements

   • Prescribed Criteria
     • PC1. Requires a successful login before retrieving and displaying the users personal account information
     • PC2. Ensure data entered by the user is validated before it is added to the database
     • PC3. Meet all Data Requirements
     • PC4. Meet all User Interface Requirements
       • The Hero/Landing page must have a Signup and Login button
       • The Signup button links to a Signup form
       • The Login button links to a Login form
       • The Signup and Login form must have validation rules
       • Once a successful Signup or Login has been completed it goes to the User Profile that displays the user information such as gamer tag, email, etc and allows to update and delete that information
   • Self-determined Criterisa
     • SDC1. Allows users to keep track of hours played
     • SDC2. Allows users to keep track of achievements
     • SDC3. Allows users to keep track of completion rates

2. Validation rules for input data

   • Minimum characters in password
     • Error message: "Password must have at least 8 characters."
   • Email is a real email
     • Error message: "This email address is invalid ."
   • Amount of numbers in password
     • Error message: "Password must have at least 1 number"
   • At least one upper case and lower case letter in password
   • Allows user to only sign up with a certain username once (make the username unique)

3. Data privacy considerations for data collected from users

   • Verification for sign up and login
   • Hashing password.

4. constraints/limitations

   • time frame
   • skill

5. Data types

   • Date
     • Date for each amount of hours played each day
     • Completion rate: What level user is up to each day
     • Achievement rates: the achievements received each day
   • strings

6. required data for login/signup process

   • password
   • username
   • email address

7. Useability Principles

   • Utility
     • ability of the system to be functional to the user
   • safety
     • ability for users to be able to make errors and recover from them with no consequence
   • Effectiveness
     • ability of the user to be able to use the system to do what they need to do.
   • learnability
     • ability of users to easily learn how to use the system.
   • Accessability
     • ability to be used by a diverse range of people, such as people of old age or disabilities

8. Impacts evaluation

   • social
     • Allows the gaming community to interact so they can look back at it to compare with their friends.
   • Personal
     • Provides users with an easy to access logbook
     • Allows for the users personal growth by recording their latest or highest achievements
   • Economic
     • Allows for profitability for the maker of the application