CRUD app

CRUD app

1. task requirements

   • self determined criteria
     • make my website visually appealing
   • constraints and limitations
     • coding environment
       • only python and HTML is used
       • only using specific coding techniques which means more complicated actions cannot be done
     • time
       • 8 weeks
   • existing solutions
     • exemplar
       • pro
         • contains key coding needed to create a CRUD application
       • con
         • not visually appealing
         • does not match the theme
   • predetermined criteria
     • PC1
       • Requires a successful login before retrieving and displaying the users personal account information
     • PC2
       • Ensure data entered by user is validated before it is added to the databases
     • PC3
       • meet all data requirements
         • Database must be able to store data
         • Database must be able to be accessed/edited through HTTP requests
         • Database must be able to store game library data
     • PC4
       • meet all user interface requirements
         • Hero/landing page must have 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
         • 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

2. developer problems

   • data
     • data source options
       • Sqlite
         • pro
           • easy to use
           • minimal setup needed
         • con
           • lacks user management features
     • required data
       • username
         • Varchar
           • 16
             • Not Null
       • password
         • varchar
           • 255
             • not null
       • achievements completed
         • Varchar
           • 225
             • not null
   • coding environment
     • development tools
       • thonny
       • HTML
       • SQlite
       • CSS
       • pseudocode
     • key algorithms
       • login
       • sign up
       • create
       • edit
       • delete
   • user interface
     • features
       • profile customisation
       • dark mode
     • useability principles
       • utility
         • ability to provide functionality needed for the user
       • effectiveness
         • how reliable the system is for users to do the work they need to do
       • accessability
         • can be used by different people such as people with disabilities
       • learnability
         • how easy the system is to learn for users
       • safety
         • ability for users to recover from mistakes or errors
     • user interface components
       • buttons
         • easy to press
       • links
         • send user to different section
       • drop down menu
         • less visual clutter
       • images
         • visual appeal

3. impacts

   • social
     • creates communities centered around achievements in games
   • personal
     • personal information is private from other users
   • economical
     • promote other games for users to buy and add achievements into website

4. user problems

   • user persona
     • user persona 1
       • needs
         • Simple easy to use interface to quickly put data in
       • details
         • wants a website which can store data on his achievements in the games he plays