Mind Map

Mind Map

1. Impacts of storing data in databases for individuals, organisations and governements

   • Social
     • Ethical Considerations
       • Other peoples personal data store locally
       • Data might be considered private
     • Survailnce Risks
       • No survalience risks
       • Used in private spaces
       • Data is stored locally
     • Data ownership
       • Since locally saved its owned by the local user
       • Ethically this is owned by the persons whos details are stored
     • Government Impact
       • No impact since using local services
       • Data is not public
   • Economic
     • Cost of Data storage
       • Small amounts of data stored
       • Cheap to store
         • Local data is stored so its cheaper
     • Monetisation of data
       • Data isnt being sold so no monitisation
       • No need to generate money
       • Free to store data
     • Database locations
       • Local Databases
         • Cheap
         • Easy
       • Clound databases
         • Costly
         • Hard to acess
         • Less Secure
   • Personal
     • User Privacy
       • Hashed Passwords
       • Hashed data
       • Localy store data
     • Control over personal data
       • Only admin can edit it
       • Only 1 admin role
       • User can change their password if they want to

2. Data that is required

   • Data Types
     • Integer
     • Strings
     • Primary and Foriegn Keys needed
   • Data Volume
     • Small to medium volumes
     • Depends on user activity
   • Data Security
     • Passwords are hashed

3. System Requirements

   • System
     • Windows and Mac
     • Brower Support
   • Software Dependancies
     • Flask
     • SQLAlchemy
     • Python
   • Hardware
     • More then 4gb of RAM
     • Small amount of disk space
   • Accesibility
     • Easy to read features
     • Text to speach

4. Programming Requirements

   • Languages
     • Python
     • Javascript
     • Markup Languages
       • HTML
       • CSS
   • Testing
     • User testing
     • Error Handling
   • Frameworks
     • Flask

5. User Requirements

   • User Persona
     • Likes modern websites
     • Organise a team
     • Easy to navigate and read
     • Easy to Interpret
   • Functional requirements
     • Data input fields for an admin
     • Document generation needed for runsheets
     • Members being allocated roles
   • Non functional Requirements
     • The system should respond quickly
     • Error Handling should be present in the app
     • A help page should be present
     • User testing should be conducted

6. Constraints and Limitations

   • Budget
     • No Budget Constraints
     • Free to use and operate
     • Budget needed for a domain
   • Tenchical
     • Software might not support app
     • Hardware might not support app
     • Not all same devices
   • Time
     • Task Length
     • Due Week 7
   • Legal
     • Safe Work Use
     • Data protect laws
     • Saftey With Personal Details
   • Ethical
     • User Consent
     • Data should be private and Hashed

7. Success Criteria

   • Meet all Coded Components & Data Requirements
     • Store and display images
     • Programmed components must differ from exemplar
     • Edit and Delete records
     • Store and display HTML form data in an external database
     • User can enter details that are relevant into a HTML form
     • Incorporate a login and signup feature that allows multiple users
   • Must Be Able to Create PDFs for a Runsheet

8. Scope of the problem

   • Problems
     • Flask Web App Required
     • Mutiple database functions needed
   • Limitations
     • Time
     • Money
     • Resources
   • Objectives
     • Flask Web App
       • CRUD
       • Admin Profiles
       • User Profiles
     • Meets users requirements
       • Passwords
       • Members
       • Document Generation
   • Buisness & Social Context
     • Usability for others
     • Is it intuative?