CRUD Application

CRUD Application

1. Developer Problem

   • User Interface
     • Features
     • Usability Principles
       • Safety
         • verifies through sign up and login
         • validation through error messages
           • "Your email/password is invalid."
           • "You are not logged in."
         • privacy - personalised data by user
       • Effectiveness
         • operable through multiple forms
       • Utility
         • successful in showing game data
       • Accessibility
         • can be used by all
       • Learnability
         • minimalist
     • User Interface Components
       • Links
       • Buttons
       • Images
   • Coding Environment
     • Development Tools
       • Thonny
     • Key Algorithms
       • Login
         • email, password
       • Sign up
         • Username, email, password
       • store data
         • hours played
   • Data
     • Data Storage & Retrieval
       • SQLite Database
       • Create table statement used
     • Data Source Options
       • DSO 1 - save login info and login automatically every time once saved
         • Pros
           • time efficient for user
         • Cons
           • risk of safety for other users
     • Required Data
       • Integer
         • Medicare
         • Data type length
           • Constraint
       • Varchar
         • Data Type Length
           • Constraint
         • Username, email, password

2. Impacts

   • Social
     • engaging
     • quality of life
     • suitable for elderly
   • Personal
     • information security
     • personalised data
   • Economic
     • innovation
     • competition
     • cost efficient

3. User problem

   • User Persona
     • User Persona 1
       • Needs
         • Store gaming data
         • Shows what games and hours played
       • Wants
         • Simple to understand
       • Details
         • Cheryl
         • 73 year old retiree
         • Brisbane, Australia

4. Task Requirements

   • Existing Solutions
     • Steam account
       • Pros
         • shows games and interests
       • Cons
         • generic
   • Constraints & Limitations
     • Coding Environment
     • Skills
     • Time
       • Due date
   • Prescribed Criteria
     • PC1 - Requires a successful login before retrieving and displaying the users personal account information
       • ability for user to enter user/password
       • can login
       • has login button
     • PC2 - Ensure data entered by the user is validated before it is added to the database
       • can re-enter credentials
       • can verify login details that meet its requirements (e.g. character length)
     • PC3 - Meet all Data Requirements
       • database stores user details
       • database can be accessed/edited through HTTP requests
       • database stores game library data
     • PC4 - Meet all User Interface Requirements
       • landing page has signup/login button
       • signup/login links to signup/login form and must have validation rules
       • goes to members page displaying user information
   • Self Determined Criteria
     • SDC1 - CRUD app aligns with user persona
       • displays gaming data
       • easy to understand
       • visually appealing