XS Community Edition/Features/Audience response system: Difference between revisions
(→Owner) |
|||
| (8 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace --> |
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace --> |
||
'''DRAFT ''' |
|||
== Summary == |
== Summary == |
||
A system that allows presenters (teachers) to survey an |
|||
A system for teachers to quick ask simple questions to a classroom, and get answers in real time |
|||
audience in real time. |
|||
== Owner == |
== Owner == |
||
| Line 21: | Line 22: | ||
== Current status == |
== Current status == |
||
* Targeted release: 0.6 |
* Targeted release: 0.6 |
||
* Last updated: |
* Last updated: November 11, 2013 |
||
* Percentage of completion: 0% |
* Percentage of completion: 0% |
||
== Detailed Description == |
== Detailed Description == |
||
A tool for teachers to create quick questions and ask them to a classrom. |
|||
[http://ripple-core.uoregon.edu/ Ripple] is an interactive audience response system that allows presenters to survey an |
|||
Teachers can also create questions sets prior to class. A suggested existing software tool to provide this feature is [http://ripple-core.uoregon.edu/ Ripple ]. |
|||
audience in real time. Audience members receive and answer questions sent by the |
|||
presenter on their internet/network connected device. Answers are compiled in real |
|||
time on the presenter’s screen for immediate feedback and discussion. |
|||
Audience response session questions can either be created prior or in real time to |
|||
solicit impromptu feedback. |
|||
Ripple is installed with six core question types: True/False, Multiple Choice, Open |
|||
Response, Slider, Numeric, and Word Cloud; however, it also accepts plugins to extend |
|||
it functionality. |
|||
(This description is extracted from the [http://ripple-core.uoregon.edu/docs/ official docs] ) |
|||
== Benefit to XSCE == |
== Benefit to XSCE == |
||
| Line 35: | Line 46: | ||
''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.'' |
''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.'' |
||
XSCE powered classrooms will become more interactive, and the system can be used by XO and non XO hardware, users just need a web browser. |
XSCE powered classrooms will become more interactive, and the system can be used by XO and non XO hardware, users just need a web browser. |
||
Teachers can also design tests to be run using the tool, as the answers are saved and can be downloaded in csv format. |
|||
== Scope == |
== Scope == |
||
| Line 58: | Line 71: | ||
== Dependencies == |
== Dependencies == |
||
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?'' |
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?'' |
||
* openssl-devel |
|||
* gcc+c++ |
|||
* mongodb-server |
|||
* nodejs 0.8.25 |
|||
== Contingency Plan == |
== Contingency Plan == |
||
Latest revision as of 14:55, 3 December 2013
This IIAB XSCE content does not reflect the opinion of OLPC. These pages were created by members of a volunteer community supporting OLPC and deployments.
Summary
A system that allows presenters (teachers) to survey an audience in real time.
Owner
- Name: Santiago Rodriguez
- Email: <at> activitycentral.com
Current status
- Targeted release: 0.6
- Last updated: November 11, 2013
- Percentage of completion: 0%
Detailed Description
Ripple is an interactive audience response system that allows presenters to survey an audience in real time. Audience members receive and answer questions sent by the presenter on their internet/network connected device. Answers are compiled in real time on the presenter’s screen for immediate feedback and discussion.
Audience response session questions can either be created prior or in real time to solicit impromptu feedback.
Ripple is installed with six core question types: True/False, Multiple Choice, Open Response, Slider, Numeric, and Word Cloud; however, it also accepts plugins to extend it functionality.
(This description is extracted from the official docs )
Benefit to XSCE
What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will XSCE become a better platform or project because of this feature?
Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.
XSCE powered classrooms will become more interactive, and the system can be used by XO and non XO hardware, users just need a web browser.
Teachers can also design tests to be run using the tool, as the answers are saved and can be downloaded in csv format.
Scope
What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?
Some changes to current ripple are:
- Identify XO users using xo moodle cooke - Internacionalization / Translation - Change session name generation, as 6 alphanumeric chars may be too much for kids to type.
UI Design
Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.
How To Test
Testing notes go here - Log in with admin default user / password, and create a session
User Experience
If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.
Dependencies
What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?
- openssl-devel
- gcc+c++
- mongodb-server
- nodejs 0.8.25
Contingency Plan
If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.
Documentation
Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.
Release Notes
The XSCE Release Notes inform end-users about what is new in the release. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.