-
Notifications
You must be signed in to change notification settings - Fork 0
Use Cases
dnstremba edited this page Jun 9, 2024
·
5 revisions
- Scope: Recall Enhancer Application
- Level: user goal
- Primary Actor: Recaller
-
Stakeholders and Interests:
- Recaller: Wants to be informed about queued items.
- Preconditions: At least one item must be created.
- Success Guarantee (or Postconditions): Recall for each item is rescheduled.
-
Main Success Scenario (or Basic Flow):
- Recaller starts recall session.
- System represents the current item to be recalled.
- Recaller finishes retaining process and rates the quality of repetition response on a scale.
- System recalculates next inter-repetition interval and logs completed recalls.
System repeats steps 2-4 unless the queue is empty.
-
Extensions (or Alternative Flows):
a*. At any time, Recaller requests display of status of the item. -
Special Requirements:
- Pluggable spaced-repetitions algorithms at step 4.