CRUD Application

CRUD Application

1. Developer Problem

   • User interface
     • Utilibility
       • The system’s ability to provide all the functionality that users need, as well as also measuring how satisfactory the person feels about a particular application
     • Safety
       • The ability for users to make errors and recover from those mistake
     • Effectiveness
       • The system is constant and dependable, allowing for users to use the system to do the work they need to do
     • Learnability
       • To be able to have the user learn it easily
     • Accessibility
       • The ability to be used by many different people, including those with disabilities and can still benefits people with slow internet or on mobile device
   • Application components
     • Sign up
       • Email
       • Username
       • Password
     • Login
       • Username
       • Password
     • Sign up button
     • Login button
     • Landing page
     • Member area
   • Data
     • Data storage
       • SQL
     • Required data
       • Password
         • Varchar
           • asdfasdf2$
     • username
       • varchar
         • hnguy213
     • Email
       • Varchar
         • Hnguy213@eq.edu.au
   • Application component

2. Task requirement

   • Introduction of your proposed prototype application
   • • Identify the user problem your digital solution will address from the User Personas provided
   • • Determine Prescribed and Self-Determined Criteria based on the user needs you identified in your Evaluation Table
   • • Recognise and describe the Useability Principles
   • • Develop a Data Dictionary that is inclusive of all tables, data types, constraints used for the prototype application
   • • Develop a Mind Map exploring the problem including: validation rules for input data and possible error messages, data privacy considerations for data collected from users, constraints/limitations of the project, data types, required data for Login/Signup process
   • • Develop a Data Flow Diagram to show the interrelationship between data and programmed components
   • • Develop Algorithms for the processes in your Data Flow Diagram present them in an IPO chart
   • • Generate Wireframes of the User Interface including annotations identifying User Interface Components and Elements and Principles of Visual Communication

3. create, read, update, delete

4. Impacts

   • Mone