User Stories - Test PR

[mmccool]

• Proposed restructuring of requirements section to include Use Case Categories and User Stories
• Uses two example user stories from TD TF, as discussed in User Stories in Work Item Descriptions wot-thing-description#2053
• Old material is retained, for now. We need to land pending PRs to bring it up to date, then (possibly...) reorganize into user stories.
• I included the "problems" under "details" but I had to reword them so they are not relative to the current state, and I also think they have too much detail for this level of the doc (they need the reader to be familiar with TDs already). So I am inclined to remove this and keep this level of detail in the specs or in supporting documents.

---

Preview | Diff

[egekorkan]

The list of process stakeholders are not copied over?

[mmccool]

The list of process stakeholders are not copied over?

I think we should create another PR for that... suggest the following:

1. Copy over the definitions from Security
2. Merge in the existing list and add definitions
3. Merge in "process stakeholders" and add definitions - possibly with "tags" indicating stakeholder categories (Process, Security, etc - may be multiple for some stakeholders).
4. Update user stories to link to specific stakeholders
5. Going forward, user stories should use one of the existing stakeholders or, only if necessary, propose a new stakeholder

Issue created: #307

[mmccool]

Notes:

• User Story Categories may not belong under Requirements - "share a common requirement." -> "share a common property."
• For feature linking: for WIP, can link back from issue/detailed specification/PRs to user story, but after feature is done can add links from user story TO the assertions defining the feature.
• Details may be for "What" or "Why" - subsections under each of these instead?
• Add a link to an issue for WIP (forward link, so would not necessarily need a back-link) - as separate

[mmccool]

• open question: do we keep links to the originating issues in the document?