Use Cases: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
Line 67: Line 67:
Related but not exactly use cases.
Related but not exactly use cases.
http://wiki.laptop.org/go/User_Stories_Testing
http://wiki.laptop.org/go/User_Stories_Testing

== Test Config Notes ==
Not exactly use cases but this is one way to determine exactly what is supposed to work <br>
http://wiki.laptop.org/go/Test_Config_Notes

Revision as of 13:02, 30 June 2008

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

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

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
One laptop opens chat
Chooses share with my neighborhood
All laptops go to neighborhood view
Each XO sees chat icon and clicks on it

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)
- There is a wireless access point in the school and they see several other wireless Aps so there is some RF background.
- 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?)

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

Library

http://wiki.laptop.org/go/Library_use_cases

Book Reader

http://wiki.laptop.org/go/Wiki_as_a_book_reader

Content Management

http://wiki.laptop.org/go/Content_Management/Use_Cases

School Server

http://wiki.laptop.org/go/School_Server_Use_Cases

Archive Backup Use Case

http://wiki.laptop.org/go/Tests/Archive%2C_Backup%2C_Content

Startup and Activation Use Case

http://wiki.laptop.org/go/Tests/Start_up_and_Activation

Test Cases

Related but not exactly use cases. http://wiki.laptop.org/go/User_Stories_Testing

Test Config Notes

Not exactly use cases but this is one way to determine exactly what is supposed to work
http://wiki.laptop.org/go/Test_Config_Notes