Proposal: Connect Work Items to Use Cases via Requirements

[mmccool]

As discussed in Discovery and Security TFs:

• We need to motivate work items with use cases
• Probably best to do requirements as an intermediate step so that requirements from multiple use cases can be consolidated
• Discovery already has an (old, but still valid) list of requirements: https://github.com/w3c/wot-usecases/blob/main/REQUIREMENTS/discovery.md
• Suggest merging this into the Discovery section under "Requirements" in the Use Cases document, updating, and then linking each requirement to one or more use cases that motivate it, then link work items to the requirements it satisfies.
• Each requirement should be given an id, so it can be linked
• Each work item should then link to the requirement it satisfies

Note: We may have to add some "general" requirements like "Ease of Use", etc. for some work items.

We would do something similar for security, but in this case the "Requirements" would be the Threat the security "feature" would mitigate. Threats are all listed in the security and privacy guidelines document (some need to be updated), but each Security section has a risk followed by a mitigation, so connecting these should be straightforward. Details however can be listed in the S&PG doc, the UC&R doc can just use the titles.

[mmccool]

See also w3c/wot-usecases#103, still open, and maybe w3c/wot-usecases#40