We should build a user journey with the goal of capturing reading fluency. The following metrics could be useful:
Syllables/min at different points of the recording.
Words/min at different points of the recording.
The metrics should be compared to a baseline (recording from an ideal reading) and to their past recordings.
We want to leverage the whisper capability of returning timestamps for the words. Possibly some sort of dict with words- timestamps-pairs
Goals for next meeting:
Show what output is produced from the input the customer provided (using meaningful diagrams). Input: audio from student reading. Output: metrics.
Abgrenzung: no need to show the actual user journey in the app, we can show a powerpoint/figma (visualization suffices) with a potential/proposed user journey
To achieve these goals, the following questions should be translated to implementation requirements in ticket(s):
[ ] #18 @Bruno-val-bus
What does the new ReadingEvaluator class produce? (It should produce quantifyable metrics that can be assigned to a student or benchmark)
What does the behaviour of the ReadingEvaluator class have to be?
Where does ReadingEvaluator class fit with the other classes? (e.g. implementing new Interface AudioEvaluator or implementing existing interface TextEvaluator)
Follow-up goals will arise after the meeting, especially regarding the user journey that we are going to build around the brains that we build from the last requirements. The following questions will be relevant for the tickets requirements:
[ ] What is the (theoretical, not productive) user journey?
We should build a user journey with the goal of capturing reading fluency. The following metrics could be useful:
Goals for next meeting:
To achieve these goals, the following questions should be translated to implementation requirements in ticket(s):
Class diagram
Follow-up goals will arise after the meeting, especially regarding the user journey that we are going to build around the brains that we build from the last requirements. The following questions will be relevant for the tickets requirements: