Requirements for Deployment Phase 1

Requirements for Deployment Phase 1

Deployment Date: April 15, 2011

By this due date, the following tasks should be completed or nearing completion. If possible, please lock these milestone requirements in one week before the due date. If a task looks too difficult for you to make for a particular milestone, please edit this milestone document to reflect what you expect to accomplish regarding that task. Edits after the one-week milestone 'lock' will be frowned upon and make us your classmates sad; you wouldn't want us to be sad, would you?

Also, feel free to update this milestone document with tasks you have completed.

Monitor Features

  1. [DONE] Integrated OCUnited and ElectricShephard, renamed to "Monitor"; has "discriminated union" of features (AKA: feature list!)
  2. [DELAYED TO Phase 2] CppUnit testing set up.
  3. [PARTIALLY DONE; finish in Phase 2] "time out" value for inactivity results in node being removed from graph, from the perspective of some designated node.
  4. [DONE AS UI STUB; finish in Phase 2] Options dialog so human user can set parameters: Time-out value, mesh check interval time (aka, refresh rate), physics on/off
  5. [DONE AS UI STUB; finish in Phase] The features will look like the mockup currently here

Middleware Features

  1. [STUBBED OUT TO WORK; finish in Phase 2] Set up Heartbeat script working on computers -- MUST BE DONE BY ALL
  2. [PARTIALLY DONE; finish by 22 Apr] Test heartbeat script to work with BATMAN protocol -- THIS IS A KEY FEATURE TO GET WORKING
  3. [DONE] Design a heartbeat test suite -- RYAN HAS IT WORKING; ALL INSTALL BY 22APR
  4. [DELAYED TO Phase 2] Mesh-independent heartbeat working with a test fixture
  5. [DONE] Be prepared to talk (QA) intelligently with Tim about compiling and deploying on ARM platform, which means a potential "live" deployment on the surrogates and/or bots.

Mesh Features

  1. [DRAFT DONE; finish in Phase 2] On-the-spot MeshKit installation onto the bots/surrogates that Tim brings, given the following requirements by the bot hardware/software platform (low priority)
  2. [DELAYED TO Phase 2] Research PyUnit usage with I/O
  3. [DELAYED TO Phase 2] Set up some form of independent testing.
  4. [DELAYED TO Phase 2] Begin construction of CCrequest.py

iRobot Questions

  1. See question list on agenda.