Difference between revisions of "Requirements definition, Use Cases"
(→Analyizing Focus Group Findings) |
(→Use Cases) |
||
Line 10: | Line 10: | ||
== Use Cases == | == Use Cases == | ||
− | Based on priorities in the findings list above, select and describe use cases, that catch the important functions you want to work on in the future. Describe a small number of use cases which together might represent a usage scenario. | + | :Based on priorities in the findings list above, select and describe use cases, that catch the important functions you want to work on in the future. Describe a small number of use cases which together might represent a usage scenario. |
− | + | :You might also want to update personas and scenarios if needed. | |
− | You might also want to update personas and scenarios if needed. | + | :After this, work will continue on storyboards (and prototypes). |
− | |||
− | After this, work will continue on storyboards (and prototypes). |
Revision as of 06:08, 31 May 2024
Analyizing Focus Group Findings
- Draft a list of findings from the Focus Groups in terms needs, whishes, ideas the participants articulated.
- Check for consistency. Are there any contradicting needs or whishes, any controversies?
- Set priorities according to your own judgement.
Requirements Collection
- Describe requirements based on findings from CI, focus group, and your own intelligent common sense.
- Collect requirements in a list.
- Relate them to the source, and - where possible and appropriate - to personas and scenarios.
Use Cases
- Based on priorities in the findings list above, select and describe use cases, that catch the important functions you want to work on in the future. Describe a small number of use cases which together might represent a usage scenario.
- You might also want to update personas and scenarios if needed.
- After this, work will continue on storyboards (and prototypes).