Scenario taxonomy: Difference between revisions

From OLPC
Jump to navigation Jump to search
Line 9: Line 9:


== Server components ==
== Server components ==

* '''Backup'''
* '''Upgrade and configuration management'''
* Network Gateway
* Caching Proxy
* Authentication
* Authentication
* Content management
* Content management
* Repository
* Repository
* Caching Proxy
* Network Gateway


== Infrastructure constraints ==
== Infrastructure constraints ==

Revision as of 14:52, 24 March 2008

Scenario Taxonomy

Introduction

This taxonomy addresses different scenarios that may occur in implementation of XO laptops and school servers. The taxonomy in its current form is simple and by no means comprehensive. Hopefully, this will change over time.


Use cases

These scenarios can be reinforced with use cases that provide a hypothetical example of use and often help in understanding needs and assessing constraints.


Server components

  • Backup
  • Upgrade and configuration management
  • Network Gateway
  • Caching Proxy
  • Authentication
  • Content management
  • Repository

Infrastructure constraints

Infrastructural constraints are very important and often drive the decision to use a laptop/mobile or desktop/lab environment or some combination thereof. Two major components of the infrastructure are power (grid-based electricity) and backhaul (connectivity to the Internet). In the following table, we have a combination of the two on a granular scale akin to low, medium, and high.


No grid infrastructure Grid infrastructure available, but does not work reliably Reliable grid infrastructure
No backhaul Worst case scenario
Limited backhaul (cellular, satellite, dial-up)
Good backhaul (DSL, Cable, or anything that can be called “high speed”) Best case scenario