CRUD APP

CRUD APP

1. User Problem

   • User Persona
     • Geoff
       • Wants
         • Application show achievement and completion rates
       • Needs
         • Simple interface
         • One place to easily store data
       • Details
         • Enjoys beating games 100%
         • Is frustrated with other datastores needing to navigate through many menus to insert data

2. Task Requirements

   • Existing Solutions
     • Instagram
       • Pros
         • Users can create accounts and posts, delete accounts, posts, and comments, read data to login, and update their account information
         • Visually appealing
       • Cons
         • Somewhat difficult to change password
   • Constraints and Limitations
     • Coding Environment
       • This task requires the programmer to use Thonny to develop the CRUD application
     • Skills
       • This task requires the programmer to know the skills of coding languages CSS, HTML, Python, and SQL to be used to create the CRUD application
       • With a restriction on time, the programmer must effectively manage their time with developing the code and completing the folio
     • Time
       • This task has a time limit that restrict how much time it must be completed in
   • Prescribed Criteria
     • PC1- Requires a successful login before retrieving and displaying the users personal account information
       • PC1 R1 - There must be a database that stores user information (id, email, first name, password)
       • PC1 R2 - The login page must allow the user to input their first name and password
       • PC1 R3 - The user input must be sent to the datastore to be checked against the first name and hashed password.
       • PC1 R4 - If the login is successful, the user will be directed to the member’s page
       • PC1 R5 - If the login is unsuccessful, the user will stay on the login page and tell the user their login was invalid.
       • PC2 R3 - The password must be at least 5 characters long
       • PC2 R4 - The rating must be less than or equal to 5
     • PC2 - Ensure data entered by the user is validated before it is added to the database
       • PC2 R1 - The email must include an ‘@’ symbol and ‘.com’
       • PC2 R2 - The completion rate and achievement rate inputs must be integers equal to or less than 100.
     • PC3 - Meet all Data Requirements
       • PC3 R1 - The database must be able to store user details
       • PC3 R2 - The database must be able to be accessed/edited through HTTP requests
       • PC3 R3 - The database must be able to store game library data. E.g. Name, Rating, Purchase Date, Hours Played
     • PC4 - Meet al User Interface Requirements
       • PC4 R1 - The Hero/Landing page must have a Signup and Login button
       • PC4 R2 - The Signup button links to a Signup form
       • PC4 R3 - The Login button links to a Login form
       • PC4 R4 - The Signup and Login form must have validation rules
       • PC4 R5 - Once a successful Signup or Login has been completed, it goes to the User Profile that displays the user information such as a gamer tag, email, etc. and allows to update and delete that information
   • Self Determined Criteria
     • SDC1 - The application design must suit the user persona
       • SDC1 R1 -The website must be primarily blue
       • SDC1 R2 - The website must allow the user to store completion and achievement rates

3. Developer Problem

   • User Interface
     • Features
     • User Interface Components
   • Usability Principles
     • Effectiveness
       • Tests whether the code does what it was created for.
     • Utility
       • How easily the program can be used and how useful it is to users
     • Accessibilty
       • Used to evaluate whether the solution can be used by a variety of people.
     • Learnability
       • How quickly and easily the solution is to understand and learn
     • Safety
       • Evaluates if the solution prevents users from creating errors and how it recovers from errors
   • Data
     • Data Types SQL
       • VARCHAR
         • A variable length string that can contain letter, numbers, and special character, with the maximum size indicated by the size parameter. Example VARCHAR(255)
       • CHAR
         • A fixed length string that can contain letters, numbers, and special characters, with the number of required characters indicated by the size parameter. Example CHAR(10)
       • DATE
         • Used to store a date in the format YYYY-MM-DD, with no size range required. Example 2024-07-11
       • INT/INTEGER
         • Stores whole numbers. Example INT(10)
     • Login/Signup
       • Users Table
         • First_Name - VARCHAR
         • Email - VARCHAR
           • Input type 'email' - must include @ and 'com'
         • Password - VARCHAR
           • Input type 'password' - will hide input on website
           • Minimum 5 - password must be at least 5 characters
       • Games Table
         • Game_Name - VARCHAR
         • Rating - INTEGER
           • Input type ' number' - must be an integer
           • Min 0 Max 5 - Input must be between 0 and 5 to reflect star rating
         • Hours - INTEGER
           • Input type 'number' - must be an integer
         • Comp_rate - INTEGER
           • Input type 'number' - must be an integer
           • Min 0 Max 100 - input must be between 0 and 100 to reflect percentage
         • Ach_rate - INTEGER
           • Input type 'number' - must be an integer
           • Min 0 Max 100 - input must be between 0 and 100 to reflect percentage
     • Data Privacy
       • Hashed password
         • The user input password is hashed when posted to the SQL database using 'sha256'.
           • This improves user safety and privacy as people cannot see their password if they access the database
       • Input type password
         • The HTML password input uses the input type 'password'.
           • This dots the password to improve user safety and privacy, as people cannot see their password on the website screen