Development:Quiz UI redesign scenarios - Scenarios index: Difference between revisions
| Line 1: | Line 1: | ||
Back to [[Development:Quiz_UI_redesign]] | Back to [[Development:Quiz_UI_redesign]] | ||
== Scenarios index == | == Scenarios index == | ||
* Creating quizzes/exams: | * Creating quizzes/exams: | ||
| Line 13: | Line 10: | ||
** [[Development:Quiz UI redesign scenarios - Publishing exam|Publishing exam]] | ** [[Development:Quiz UI redesign scenarios - Publishing exam|Publishing exam]] | ||
** [[Development:Quiz UI redesign scenarios - Grading et Feedback|Grading & Feedback]] | ** [[Development:Quiz UI redesign scenarios - Grading et Feedback|Grading & Feedback]] | ||
===Help required with scenarios work: teachers, support, administrators === | |||
I invite everybody to take part in gathering the scenarios and adding their own. The main point is not to realistically portray all kinds of moodle users, but to have all the ways of using different parts of Quiz documented. Discussion will be in Quiz forum, once I announce it, but you may want to make modifications directly here, too - notify me, however if you make any major changes. | |||
If your ways of using Quiz do not seem to fit in with any of the scenarios, you can either fill in details for existing fictional (though representative) personas, or create new ones so that we have all the real usage scenarios covered. Note that the details about the persona do not need to match your case - what is important is the ways quizzes are made and what affects it, matches. | |||
=== Background === | |||
''For each task identified (or major tasks, or particularly special tasks if many tasks are defined), write a description of how that user would accomplish the task independent of how they would complete it within the application.'' | ''For each task identified (or major tasks, or particularly special tasks if many tasks are defined), write a description of how that user would accomplish the task independent of how they would complete it within the application.'' | ||
Revision as of 12:26, 14 June 2008
Back to Development:Quiz_UI_redesign
Scenarios index
- Creating quizzes/exams:
- Personas - Mack Marketing, Ida Informatics, Harvey Historian, Fred, Susan Support, Grace Grader (some of these characters may be merged as we go on)
- Preparing questions
- Organizing questions and adding them into an exam
- Scenarios of further phases:
Help required with scenarios work: teachers, support, administrators
I invite everybody to take part in gathering the scenarios and adding their own. The main point is not to realistically portray all kinds of moodle users, but to have all the ways of using different parts of Quiz documented. Discussion will be in Quiz forum, once I announce it, but you may want to make modifications directly here, too - notify me, however if you make any major changes.
If your ways of using Quiz do not seem to fit in with any of the scenarios, you can either fill in details for existing fictional (though representative) personas, or create new ones so that we have all the real usage scenarios covered. Note that the details about the persona do not need to match your case - what is important is the ways quizzes are made and what affects it, matches.
Background
For each task identified (or major tasks, or particularly special tasks if many tasks are defined), write a description of how that user would accomplish the task independent of how they would complete it within the application.
Preliminary scenario interviews were carried out during May 2008. See also: Development: Quiz UI redesign - what makes a scenarios interview? (unfinished)
Most of the scenario data is, although mostly independent of software, directly applicable to how the interaction with Moodle Quiz should work in different situations.
Also, feel free to comment if you think any of the personas or their scenarios do not seem realistic or you think a persona does not somehow represent an existing prototypical user. In case you are wondering, the slightly playful names of the personas are just to help developers remember the personas in order to refer to them in discussion.
TODO: document, at which stages of a broader context, e.g. usually a course, different stages take place.
