Meeting: Class Web-Meeting
Time 06/29/05 @ 07:00PM-08:00PM EDT
Attendees: Miyul, Carl, Chang Sun, Ghislaine, Omar, Jeong, Gurmit, Gary
================================

Agenda:
-------
* Discuss OCD template
* Discuss scenarios & document content.


Decisions:
----------

* Item #4 should be removed from assumption list
  - This was intended to be used for eval criteria in
    trade study - not an assumption/constraint for system design.

* Detailed questions such as number of CPUs and software allocation will 
  not go in the OCD, but will be be written in the system & software 
  architecture document.


* The Team will attempt to complete current template with scenarios as 
  best as we are able.
- There isn't time to make many changes, it is more important 
  to complete the content of the document.
  - Rather than debate template changes, the team will work on 
    developing content for their respective sections.
- However, there is risk that the direction of the Document will 
  not be what Sam intended.
- To address this,
   a) Omar will craft an alternative high-level scenario (above 
       the subsystem level.)
   b) Gary will contact Sam and confirm if the latest OCD 
      revision {0.5} is correct.

* We will not schedule another webmeeting to discuss the merged OCD unless 
  Mi Yul finds it neccessary.
- Team will try to communicate revision updates via EMail instead.
- If Mi Yul DOES find it neccessary, we can schedule as needed.
- Due to tight time-constraint, we may allow the OCD schedule to 
  slip one or two days to get the content right, as long as 
  other work begins in parallel.

* Possible scenarios for Environment Sensing
  - Obstacle Detection


Actions:
--------

* Mi Yul - Please remove assumption #4 from the list.

* Omar - propose high-level scenario.

* Gary - Contact SAM for guidance on OCD.

* Team - Submit OCD content to Mi Yul by COB Thus 06/30.

* Mi Yul - collect each teams scenarios & merge into OCD.
         - Send merged OCD draft to team for final review.

Issues:
-------

* Team is not sure of content of OCD
  - This adds risk to being able to correctly complete on time.