Use Cases

This page is a directory of XO software use cases.

Please add links to any other pages with use cases here. Please include the source of the use case. Real world feedback from end users is preferred.

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:

All laptops are seen in the neighborhood view.
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:

All laptops are seen in the neighborhood view.
All laptops eventually download the document. Depending on the number of XOs used, this could take a little while due to bandwidth saturation.
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.

Verify:

All laptops are seen in the neighborhood view.
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!)
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).

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:

All laptops are seen in the neighborhood view.
All laptops are able to see the bookmarks shared by other XOs in the group.
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:

All laptops are seen in the neighborhood view.
All laptops are able to see the thumbnails of the recordings made by the participants.
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.

Old (circa 2007) design page for Chat including some use cases
http://wiki.laptop.org/go/Instant_messaging_challenges#Use_Cases