CRUD application

CRUD application

1. User Problem

   • User Persona
     • Cheryl
       • Wants
         • Improve cognitive skills and memory
       • Needs
         • store gaming data simply
       • Details
         • 73 years old, retired, lives in Brisbane

2. Impacts

   • Social
     • Sharing gameplay data in a community
     • competing with gameplay data
     • enhance game community
   • Economic
     • purchasing more games
     • company making profit
     • merchandise sold
   • Personal
     • Can show doctor correct number of hours
     • improve motivation for playing games
     • improve memory and cognitive ability

3. Task Requirements

   • Self-Determined Criteria
     • Aesthetically pleasing
       • use elements and principles of visual communication
       • Make it look similar to the mockup
     • Allow users to record their game and hours played
       • store the inputted data
       • Make input fields for time and text
   • Prescribed Criteria
     • Ensure data entered by the user is validated before it is added to the database
       • Use data constraints in SQL to make sure data is valid
       • Create input fields specific to the user input
       • Ensure there is a database to input data
     • Requires a successful login before retrieving and displaying the users personal account information
       • Create requirements so the user must create a strong password
       • Create input fields for users to input their details and sign up
       • Output the correct account’s information when logged in
     • Constraints and Limitations
       • TIme
         • 8 weeks
       • Skills
         • HTML
         • CSS
         • SQL
         • Python
       • Coding Environment
         • Qlearn resources
         • Internet
         • Mr Stewart
         • Laptop
     • 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
     • Meet all data requirements
       • Database must store user details
       • database must be able tpo be accessed/editted through HTTP requests
       • database must be able to store game library data
   • Existing Solutions
     • Pet Exemplar
       • Pros
         • users can create account and login
         • users can input data about pet name and type
         • users can retrieve inputted data
       • Cons
         • Input is limited to pet name and type
         • The design is too simple

4. Developer Problem

   • Data
     • Required Data
       • login and signup data
       • user input of game
     • Data Storage and Retrieval
       • SQLite Database
       • CREATE TABLE statement used
       • HTML input field
       • GET POST statement used
   • Coding Environment
     • Development Tools
       • Thonny
       • Notepad++
       • SQLite
     • Key Algorithms
       • Log in
       • Signup
       • Store and retrieve data
   • User Interface
     • Features
     • Usability Principles
       • Effectiveness
         • The ability for the solution to satisfy the needs of the users, and the consistency of it
       • Utility
         • How useful the solution is, or how it provides all of the functionality required for the user
       • Accessibility
         • Whether the solution can be used by many different people, who are in different conditions
       • Learnability
         • How easy it is to navigate through the solution
       • Safety
         • Whether users can recover from mistakes, and how easy it is to make the mistakes
     • UI components
       • Links
       • Images
       • Buttons