[Tinyos-2-commits] CVS: tinyos-2.x/doc/txt tep130.txt,1.1,1.2

[Jan Beutel]

Update of /cvsroot/tinyos/tinyos-2.x/doc/txt
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv13189/doc/txt

Modified Files:
	tep130.txt 
Log Message:
some more changes

Index: tep130.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep130.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** tep130.txt	21 Jun 2007 18:23:44 -0000	1.1
--- tep130.txt	28 Jun 2007 16:41:55 -0000	1.2
***************
*** 53,62 ****
  connected to a central resource for control and logging that are deployed in a 
  physical space (testing area). Typically the central resource is a server with 
! integrated datalogging capability.
  
  MISSING: Difference of a testbed vs. a desktop test (e.g. single nodes with a 
  programmer or a simple usb grid)
  
! Examples of current sensor network testbeds are MoteLab [1_] and the 
  Deployment-Support Network [2_].
  
--- 53,66 ----
  connected to a central resource for control and logging that are deployed in a 
  physical space (testing area). Typically the central resource is a server with 
! integrated datalogging capability. Often a web front end serves as a simple control and 
! visualization resource. For the submission of testing jobs and the analysis of 
! testing results external tools are attached to the central resource using a 
! standardized interface. This document serves as a key specification document for 
! such an interface and its intended usage.
  
  MISSING: Difference of a testbed vs. a desktop test (e.g. single nodes with a 
  programmer or a simple usb grid)
  
! Examples of currently used sensor network testbeds are MoteLab [1_] and the 
  Deployment-Support Network [2_].
  
***************
*** 64,73 ****
  2. Testbed Usage
  ====================================================================
  
  Modes of Operation:
  
! - Single Shot
  
! - Continuous Integration
  
  - Long Term Operation (Profiling)
--- 68,91 ----
  2. Testbed Usage
  ====================================================================
+ A testbed can serve different purposes depending on the development status and 
+ requirements of a specific project. While this document does not target to restrict 
+ such usage it defines a set of mandatory modes of operation that a testbed must 
+ be able to support:
  
  Modes of Operation:
  
! - Single Shot Operation
  
! Execute a testing job consisting of an uploading of a specific code image onto a 
! set of nodes, remote programming of nodes using a testbed resource, the 
! synchronized start of this software, capture of resulting target response, the 
! centralized storage and timestamping of all actions and target response, ending 
! of test execution, notification of a user of the end of test execution, output 
! of all stored data on demand.
! 
! - Repetitive (e.g. using continuous integration or for regression testing)
! 
! A concatenation of single shot testing jobs, that in practice often will be used 
! with the variation of one or more parameters.
  
  - Long Term Operation (Profiling)
***************
*** 79,90 ****
  - Access/Resource Arbitration
  
  
  3. Testbed Services
  ====================================================================
  
  - identification of target devices (presence, type, hw rev)
  - programming of target devices
  - resetting of target devices
! - logging of target response
  - versioning/identification of uploaded software 
  - identification/versioning/archiving of testing jobs
--- 97,112 ----
  - Access/Resource Arbitration
  
+ - Scheduling of testing jobs
+ 
  
  3. Testbed Services
  ====================================================================
+ Required Services:
+ 
  
  - identification of target devices (presence, type, hw rev)
  - programming of target devices
  - resetting of target devices
! - logging of target response (UART mandatory, IRQ optional)
  - versioning/identification of uploaded software 
  - identification/versioning/archiving of testing jobs
***************
*** 92,97 ****
  - testbed status information
  - identification of testbed services
! - authentification
  
  
  4. Implementation
--- 114,123 ----
  - testbed status information
  - identification of testbed services
! - user authentification
  
+ Optional:
+ - power measurements
+ - stimuli
+ - distributed scheduling of actions (at nodes)
  
  4. Implementation