CRUD application

CRUD application

1. proposed prototype

   • purpose features
     • purpose
       • I wanna make a steam rip off that shows the amount of achievements completed and the hours played
   • overall look
     • login
       • generic login pages that looks like your pet rock website login
       • username and password input in center of page and a do you wanna register at the bottom
     • the home page will have a table in the center containing all the data
   • privacy considerations
     • only collect email as personal data for account recovery
       • no collect any other data other than username and password

2. user problem/solution

   • user
     • needs
       • website needs to be able the track user data on games
     • Geoff
       • needs and expectations
         • Simple easy to use interface to quickly put my data in
       • user problem
         • Store achievements and completion rates
   • solution
     • website that tracks user data and games

3. DFD/Data type/ data organisation

   • DFD
     • game data
       • achievements
         • varchar
       • time played
         • integer
       • username
         • varchar
       • password
         • varchar
       • user reference number
         • integer
         • integer
       • relative game
         • varchar
   • SQL DATA
     • data types
       • varchar
         • and string of data that stores letters and sentences/phrases
       • integer
         • a whole number for user
       • boolean
         • true or false value
     • data needed for processes

4. principles and concepts of web design

   • shape
     • shapes are often use in tandem with other concepts to have a greater effect
   • line
     • line are use to devide the websites into differnt section
   • colour
     • the colour scheme should make the website look nice
     • use colour to divert attention
   • princples
     • utility
       • Utility is the practicality of a product. It is concerned with how practical a product is to use in a real-world context. If a product Has a good utility it means that the product has practical to use in real life context and maybe even how well it does compared to it’s competition. (Nielson, 2012)
     • safety
       • Safety is how well the product can prevent the user from mistakes and ensuring that they can recover form their own mistakes. The safety of a product is determined by how often a user makes a mistake and how easily that mistake can be undone. For example, safety can be colour coding delete buttons red and save buttons green. (Queensland Curriculum & Assessment Authority, 2014)
     • learnability
       • Learnability is the user’s ability to learn how to use a product. Learnability can be improved by using symbols, colours, and have consistent features similar to other applications (Nielson, 2012)
     • effectivess
       • Effectiveness is how well a product does it’s built purpose. If a product is effective, it means that users of the product can do their task quickly without mistake. (Queensland Curriculum & Assessment Authority, 2014)
     • accessability
       • Accessibility is who can use the product. Accessibility is concerned with if Any users with impairments can use the websites like language barriers, deaf, different device, different Operating systems, and device performance (will the computer struggle to load the website