FA2 mind map

FA2 mind map

1. task requirements

   • constraints & limitations
     • time
       • 8 weeks (due wk 8)
     • skills
       • lack the required coding skills / knowledge
     • coding environment
       • at home cant ask for help from teacher
       • can only get help from teacher at school
   • prescribed criteria
     • PC2. Ensure data entered by the user is validated before it is added to the database
       • data entered by user is validated
         • then added to the database
       • pc1 req
     • PC1. Requires a successful login before retrieving and displaying the users personal account information
       • requires a successful login
         • then retrieves and displayers users personal account information
       • pc1 requirement
     • self determined criteria
       • sdc1 description
         • sdc1 req
         • sdc1 req
     • PC3. Meet all Data Requirements
     • PC4. Meet all User Interface Requirements
   • existing solutions
     • solution 1
       • pro
       • cons

2. developer problem

   • user interface
     • features
       • login
       • sign up
       • landing
       • members
     • usability principles
       • safety
         • Safety is making the user interface so that crucial mistakes cant happen, and if they do happen its possible to recover.
       • learnability
         • easy to learn, using familiar controls like wasd or right click to shoot for example
       • accessibility
       • effectiveness
       • utility
     • user interface components
       • buttons
       • drop down menus
       • images
       • links
   • coding environment
     • key algorithm
       • sign up
       • log in
       • member
     • development tools
       • thonny
       • SQLite
       • flask
   • data
     • data storage and retrieval
       • SQLite database
         • user database (user.db)
           • store user log in credentials
             • username
             • password (encrypted)
           • users data
         • credit card info database (card.db)
           • stores users card info for quicker payments
             • card number
             • cardholders first name
             • cardholders lastname
             • expiry date
             • CVC
         • stores users purchase history
     • create table statement used
     • required data
       • log in data
         • username
           • varchar
             • 255
               • primary key
         • password
           • varchar
             • 255
               • not null
       • sign up data
         • email
           • varchar
             • 255
               • unique
         • username
           • varchar
             • 255
               • primary key
         • password
           • varchar
             • 255
               • not null
       • card data
         • cardnumber
           • integer
             • 12
               • not null
         • cardholders firstname
           • varchar
             • 255
               • not null
         • cardholders lastname
           • varchar
             • 255
               • not null
         • expiry data
           • data
             • NA
               • not null
         • cvc
           • integer
             • 3
               • not null
     • data source options
       • option 1
         • pro
         • con
       • option 2
         • pro
         • con

3. impacts

   • social
   • personal
   • economic
     • not too complex
       • wont have to hire a coder and can save 80k from salary

4. user problem

   • user persona
     • user persona 1
       • needs
         • interface that saves credit card info + saves purchase history for items
       • details
         • Miguel, 49, pharmacist, Mexican
       • wants