use_cases.md

Use Cases

All features come from informally described use cases. This will allow keep clear understanding of possible use scenarios of the app.

Case studies

Some basic understanding of use cases gained by reading following articles:

• Sample Use Case Example
• Use case series: Informal Use Case
• Informal Use Case Template
• Use Case-based Requirements
• System Use Cases: An Agile Introduction

Use case template

New use case should be added as a separate document to the doc/requirements folder. Name of the document should include unique usecase id as a prefix (Example: UC1, UC2 ...). Description should contain all necessary information abour prerequisites, triggers, etc. All use case descriptions should follow template below.

[UC1] Doing something

Description:

Actors:

Basic Flow:

• 1:
• 2:
• 3:

Alternative Flows:

• 1a:
  • 1a1:
  • 1a2:
• 3a:
  • 3a1:
  • 3a2:
• 3b:
  • 3b1: