1. Design for efficiency
2. 6.1.1 Improve efficiency of inventory system
   1. 6.2.1 Reduce time spent
      1. Average no. of hours/week the solution saved
         1. More the better
         2. Do not increase time currently spent
      2. Time required to implement the system
         1. More the better
   2. 6.2.2 Identity food info
      1. Time required to obtain information
         1. Less time is better
      2. No. of actions required to obtain information
         1. Fewer actions are better
   3. 6.2.3 Reduce inventory errors
      1. 6.2.3.1 Mitigate human errors
         1. No. of human actions needed
            1. Less is better
         2. Complexity of each task
            1. Less is better
         3. Frequency of checking if inventory data matches real inventory
            1. More frequent the better
      2. 6.2.3.2 Reduce system errors
         1. Complexity of the system
            1. Less complicated the better
         2. Checks and balances
            1. Yes is better
   4. 6.2.7 Maintainability
      1. Complexity of the system
         1. Lower the complexity the better
      2. Mean Time to Maintain
         1. Less the better
3. Design for communication
4. 6.1.2 Increase the capability for volunteers to work with the inventory
   1. 6.2.4 Affordable
      1. Cost to implement
         1. Lower the better
      2. Cost to maintain
         1. Lower the better
   2. 6.2.5 Ease of use
      1. Time it takes to learn how to use
         1. Less the better
      2. Task Complexity Formula
         1. Less the better
   3. 6.2.6 Increase access to info
      1. Number of people who can access the information
         1. More people with credentials that have the access to the information the better.
      2. Number of physical locations information is accessible from
         1. If physical solution: More locations the data can be accessed the better.
         2. If electronic solution: More available the technology used to access the info the better.
5. Design for sustainability
6. 6.1.3 Facilitate current needs and future growth
   1. 6.2.8 Scalability
      1. Time and cost of implementing resources required for each new geographical location
         1. Less the better
      2. No. of adaptations required for installing the system in a new geographical location esearch - resources
         1. Less the better
      3. No. of self-expanding resources (resources that increase their own usage)
         1. Less the better
   2. 6.2.9 Integrability
      1. Complexity of the system
         1. Less the better
      2. No. of components involved in the transfer of information (No.)
         1. Less the better
      3. No. of data types involved (No.)
         1. Less variation of data types the better
   3. 6.2.10 Replicable
      1. . Average Integration Complexity* (Higher the number, more complex the integration)
         1. Less the better
      2. No. of resources required
         1. Less the better
      3. Rarity of resources
         1. Less the better
      4. Total cost of the system (CAD $)
         1. Less the better
      5. High permissiveness
         1. Higher on the list, the better
         2. Should be above rank 3 (exclusive)
      6. To remove any liability For software: Must use either MIT or GNU GPLv3 License
7. Design for equity