Use Cases

From OLPC

Revision as of 04:13, 27 January 2011 by Skierpage (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search
It has been suggested that this article or section be merged with Testing#Testing_areas. (Discuss)


This page is an old idea to have a directory of XO software use cases, scenarios that portray how the laptop should work in some situation. This overlaps with the many test plans and tests that OLPC has accumulated over the years;

You can mention external pages with use cases here. Please include the source of the use case. Real world feedback from end users is preferred. (Pages in the wiki that describe use cases should simply be categorized [[Category:Use cases]] .)

Contents

Under Tree Case

Before starting a use case, ensure that:

  • There is no school server or wireless AP or other infrastructure.
  • There must not be any other XOs turned on and within wireless range


Setup

  • Load build 656 (703 and 708 also cases) on all 10 XOs
  • Up to 10 laptop communicating via mesh
  • Start all 10 laptops
  • Each laptop clicks on mesh circle 6
  • Check that you are connected to mesh 6 by hovering over the circle in the home screen


Chat

  • One laptop opens Chat.
  • Chooses share with my neighborhood.
  • All laptops go to neighborhood view.
  • Each XO sees the Chat icon and clicks on it.

Verify:

  1. All laptops are seen in the neighborhood view.
  2. All laptop chats are seen in each laptop.


Read

  • One laptop opens a document in Read.
  • Chooses share with my neighborhood.
  • All laptops go to the neighborhood view.
  • Each XO sees the Read icon and clicks on it.
  • When document finishes downloading, glance through the document.

Verify:

  1. All laptops are seen in the neighborhood view.
  2. All laptops eventually download the document. Depending on the number of XOs used, this could take a little while due to bandwidth saturation.
  3. All laptops are able to scroll through and view the document.


Write

  • One laptop opens a new Write document.
  • Chooses share with my neighborhood.
  • All laptops go to the neighborhood view.
  • Each XO sees the Write icon and clicks on it.
  • Each XO should try typing something into the document in different locations, with different numbers of XOs typing at the same time.
  • Each XO should try typing something at the same place in the document, with different numbers of XOs typing at the same time.
  • Some or all of the XOs should try stopping the activity (saving it), and then resuming the activity through the Journal.


Verify:

  1. All laptops are seen in the neighborhood view.
  2. All laptops are able to open the document. Any changes made to the document in the interim between when it was started/resumed and when the laptops joined the shared activity should be visible. (No stale copies!)
  3. All laptops are able to contribute to the document, and changes made to the document are visible to the other laptops in a reasonable amount of time (a few seconds).
  4. The Write activity should save properly and display everything that was present when it was saved. (The collaboration will be lost when the activity is stopped, so resuming the activity from the Journal will not rejoin the shared version of the activity which may have new changes. In order to do that, the user must rejoin the activity through the Neighborhood/Mesh view.)

Browse

  • One laptop opens Browse.
  • Chooses share with my neighborhood.
  • All laptops go to the neighborhood view.
  • Each XO sees the Write icon and clicks on it.
  • Each XO starts browsing the web and making bookmarks.
  • Each XO clicks on bookmarks taken by other XOs.

Verify:

  1. All laptops are seen in the neighborhood view.
  2. All laptops are able to see the bookmarks shared by other XOs in the group.
  3. All laptops are able to navigate to the bookmarks shared by other XOs when they are clicked on.


Record

  • One laptop opens Record.
  • Chooses share with my neighborhood.
  • All laptops go to the neighborhood view.
  • Each XO sees the Record icon and clicks on it.
  • Each XO takes a few pictures.
  • Each XO makes a short audio or video recording.
  • Each XO clicks on thumbnails of the recordings and images that the other XOs took.

Verify:

  1. All laptops are seen in the neighborhood view.
  2. All laptops are able to see the thumbnails of the recordings made by the participants.
  3. All laptops are able to view images and recordings made by the participants. May take a little bit if all of the laptops are sending/uploading files at once due to bandwidth saturation.

Collaboration Examples

Uruguay Teacher Example

From http://lists.laptop.org/pipermail/olpc-sur/2008-May/000118.html

- The class has 10 - 25 kids in the second grade each with an XO. There are 100 - 200 Xos in the school. Each class can join a different channel and time share to keep the number of Xos per channel to a minimum.
- One class (10 - 25) connects its Xos to the mesh (they do it by clicking the round mesh icon but they will do whatever works)
- One kid opens write (also want to use paint) sets it to share and starts writing.
- In the neighborhood view the other students see the write icon and join the activity by clicking on it.
- All the children start to write text and add pictures at more or less the same time
- Each kid wants to save the file in their own journal at any time (this is where it crashed when they tried it with write)
- After saving to the journal they want to see the shared document again. Its OK to require them to leave the share to open their own local copy as long as it doesn't "crash" if they do it out of order (what is supposed to happen if you are sharing a document then open a new one too?)

Add to release notes as needed based on test results. - There is a wireless access point in the school and they see several other wireless Aps so there is some RF background.


Collaboration Use Cases from Peru

Write
Use case:
Multiple grades on one room, each grade is working on one document.

Only 2-3 students edit the document at one time (maybe 2); then the teacher makes edits; then the next student makes edits. As many as 30-40 students can read the document.

Record
Use case:
30-40 students can share the same record session for photos.

Etoys
Use case:
2-3 students can edit an Etoys document at one time; 30-40 students can see it (share but not edit at the same time)

Chat
Use case:
30-40 people can chat at one time.

Turtle Art and Scatch
Use case: For these programs they use them as individual instances on individual laptops. They show each other the end result. No need to share files.

Combination of activities
Use case:
The students should be able to use Record, Paint, and Calculate and Write at the same time. Creating pictures in paint as well as taking pictures and adding them to a shared write document.


Sharing work with other teachers and from students to teachers

Use case: Submitting work to teachers, sharing files among teachers They would like a better way to review writing assignments, perhaps an easy way for the student to 'submit' it to the school server and the teacher can read it from there.

Etoys Collaboration Example

From Tim (waveplace): http://lists.laptop.org/pipermail/etoys/2008-August/002538.html

FOR THE TEACHER XO:

1) open up Etoys on one XO, with the project you want to share
2) pause any scripts to make your life easier
3) click the white circle with the black dot in the toolbar
4) choose "make a badge"
5) when all other XOs have joined, you can safely delete the "buddy" holder

FOR EACH OTHER XO:
1) click the neighborhood key (third from top-left)
2) find the shooting star and choose "join" from it
3) Etoys should open, then show a "badge" with the teachers XO name
4) click the "S" button and a a little copy of the teacher screen should appear
5) click "1x1" to make the teacher screen bigger
6) move the pointer to the upper right corner and tell them not to move it (too confusing)

You should now be able to use the teacher XO and have it replicated on the other XOs. In testing, I've found it can take about 15 to 20 seconds for the other XOs to catch up, though this varies based upon how much activity is happening from the teacher XO. Sometimes its instantaneous. In general, pause scripts when you can and plan your movements ... it'll speed things up.

You can either broadcast from one mentor's XO to the other mentors, and assemble the kids around each, or you can try full broadcast. I tested with ten XOs sharing and there was no noticeable slowdown. You might experiment with one XO sharing to four XOs, then those four sharing to five XOs. Might speed things up.

Old (circa 2007) Chat page with some collaboration use cases

Instant messaging challenges#Use_Cases

Other use cases in the wiki

Here are pages in Category:Use cases (including this one):

See also

Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox