Utilizing user stories to breakdown complex systems or features.

user-story.md

ID: TITLE

REFERENCE (DELETE):

• SEE How to Write Good User Stories in Agile Development for a solid description of the initial description of the user story.
• SEE Acceptance Criteria: Given When Then Syntax for a solid description of this approach.

END DELETE

[INTRODUCTION OR DESCRIPTION OF OVERALL FEATURE REQUEST]

Table of Contents

• ID: TITLE
  • FUNCTIONAL DECOMPOSITION
    • User Story Title
  • DESIGN NOTES
  • TEST NOTES
  • REFERENCES

FUNCTIONAL DECOMPOSITION

User Story Title

As a [WHO], I want to [WHAT], so that [WHY].

[FURTHER DESCRIPTION]

Acceptance Criteria:

1. Given: [SOME PRECONDITION] and [SOME OTHER PRECONDITION].

   • When: [ACTION IS TAKEN].
   • Then: [RESULT OF ACTION].
   • But: [ALTERNATE RESULT OF ACTION].

2. Given: [SOME PRECONDITION] and [SOME OTHER PRECONDITION].

   • When: [ACTION IS TAKEN].
   • Then: [RESULT OF ACTION].
   • But: [ALTERNATE RESULT OF ACTION].

DESIGN NOTES

[UML, API EXAMPLES, etc.]

TEST NOTES

[FORMAL TESTS TO RUN, NEW TEST NOTES, CONFIGURATIONS, etc.]

REFERENCES

[ANY OUTSIDE ARTIFACTS RELATED TO THIS]