Pigeoned Webapp

Pigeoned Webapp

1. Criteria

   • Prescribed Criteria
     • Requires a successful login before retrieving and displaying the users personal account information
     • Ensure data entered by the user is validated before it is added to the database
     • Meet all Data Requirements.
       • Database must be able to store all user details.
         • Username, phone number, email, password
       • The database must be able to be accessed/edited through HTTP requests.
       • Database must be able to store game library data.
         • Hours Played, Completion Rate, Achievements, Game Name
     • Meet all User Interface Requirements.
       • Hero/Landing page must have a Signup and Login button.
       • Signup button links to a Signup form.
       • Login button links to a Login form.
       • Signup and Login form must have validation rules.
         • Signup - Email address required.
       • 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 Criteria
     • Add a Dark Mode feature.
     • Add a way to track Completion Rate.

2. User Personas

   • Geoff
     • Frustrations
       • Forgtetting how much time played on games.
     • Needs & Expectations
       • SImplistic
       • Easy way to store data
   • Cheryl
     • Frustrations
       • Navigating through too many menus.
       • Not having his own datastore.
     • Need & Expectations
       • Store data
       • Simplistic

3. Existing Solutions

   • Steam
   • Epic Games
   • Rockstar Games
   • Riot Games

4. Coding

   • Languages
     • Python (Flask)
     • SQL Database
     • HTML (Not a language)
       • CSS Styling

5. Login/Signup Data

   • Username
   • Phone Number
   • Email
   • Password

6. Data Types

   • Integer
   • Float
   • String - Varchar
   • Constraints
     • Not NULL
     • Primary Key
     • Foreign Key
     • Unique

7. Privacy Considerations

   • Hashed Passwords in HTML code
   • Data encrypted in SQL database
   • Phone number attached to account
   • Passwords are not unique

8. Data Validation Rules

   • Username, email and phone number are unique
   • Email must have an @ (adress)
   • Important aspects are NOT NULL (email and username required)