Rationale: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
Their frequent requirements are: | Their frequent requirements are: | ||
==at element level== | |||
* custom | * possibility to add custom question type matching specific needs | ||
* question predefined value | * question predefined value | ||
* question level validation | * question level validation | ||
* reduce, as much as possible, the range of possible answers | * reduce, as much as possible, the range of possible answers | ||
* mandatory questions | * mandatory questions | ||
* have some typographic option to display elements in different ways | |||
* tools to quickly reuse set a specific questions that never change in each survey | |||
==at survey level== | |||
* conditional branching | |||
* force the user to provide a his/her own answer | * force the user to provide a his/her own answer | ||
* subset of questions available to teachers ONLY | * subset of questions available to teachers ONLY | ||
* a way to allow a set of users to submit the same survey writing it at different times | * a way to allow a set of users to submit the same survey writing it at different times | ||
* use captcha | |||
* save a backup copy of each submitted survey each time it is modified in order to have the History of the record | * save a backup copy of each submitted survey each time it is modified in order to have the History of the record | ||
* speed up form fill as much as it is possible | |||
==at report level== | |||
* custom reports | * custom reports | ||
* | * export of submitted surveys | ||
Revision as of 05:34, 23 May 2013
The idea standing after the development of this module is to provide answers to the more frequent requirements of end users.
Their frequent requirements are:
at element level
- possibility to add custom question type matching specific needs
- question predefined value
- question level validation
- reduce, as much as possible, the range of possible answers
- mandatory questions
- have some typographic option to display elements in different ways
- tools to quickly reuse set a specific questions that never change in each survey
at survey level
- conditional branching
- force the user to provide a his/her own answer
- subset of questions available to teachers ONLY
- a way to allow a set of users to submit the same survey writing it at different times
- use captcha
- save a backup copy of each submitted survey each time it is modified in order to have the History of the record
- speed up form fill as much as it is possible
at report level
- custom reports
- export of submitted surveys
