CRUD app

CRUD app

1. Impacts

   • Social
   • Personal
   • Economic

2. User problem

   • User persona
     • Cheryl
       • Wants
       • Needs
       • Details

3. Task requirements

   • Self-determined criteria
     • Create an aesthetically pleasing website
     • Allow user to record their game and the hours played
   • Prescirbed 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
       • The database must be able to store user details
       • The database must be able to be accessed/edited through HTTP request
       • The databse must be able to store game library data
     • 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
   • Constraints and limitations
   • Existing solutions

4. Developer problem

   • Data
     • Data source options
       • • Pro
         • Con
     • Data storage and retrieval
       • SQLite Database
       • Create table statement used
     • Requred Data
   • User Interface
     • Features
     • Usability Principles
       • Effectiveness
       • Utility
       • Accessbility
       • Learnability
       • Safety
     • User interface components
   • Coding Environment
     • Key algorithms
     • Development Tools