Defining Requirements for Output Transforms

Here is the link to the spreadsheet that was shared during today’s meeting, showing a “living list” of requirements:

For now, the link is read-only, but all should be able to comment. (If anyone needs edit access, just contact me and I’ll be happy to add you.)

However, requirements-to-be-added that require discussion and are likely to spur extensive back-and-forth are probably best discussed here.

Suggestions that were made today during the call were:

  • add a “Type” column - for ranking things either in terms of priority or as required, desirable, optional - or whatever ranking scale we settle on
  • add a “Possible tradeoff(s)” column - in case a particular requirement appears to conflict with another requirement or desired outcome