Changes between Version 3 and Version 4 of Software_Design

Show
Ignore:
Author:
lyncas (IP: 70.114.157.27)
Timestamp:
10/07/06 10:42:31 (3 years ago)
Comment:

added Proposed Software Design

Legend:

Unmodified
Added
Removed
Modified

  • Software_Design

    v3 v4  
     1 
    12The software is broken into three components: the [wiki:FrontEnd], the [wiki:Body], and the [wiki:Backend].  These components are separated by abstract interface.  The [wiki:Frontend_Interface] is for communication between the Frontend and the Body.  The [wiki:Backend_Interface] is for communication between the Backend and the body. 
    23 
    1415The backend primarily consists of device drivers.  However, since we implement an abstract interface between the Backend and the Body, we have added flexibility.  Drivers can be in a single process or more than once process (as long as they implement the protocol described in the [wiki:Backend_Interface]).  The drivers can also be replaced by a simulator, that mimics the protocol, but simulates the data.  Other processes can also use the Backend Interface.  For example, a monitor process can silently receive all the packets that go across the backend interface and display the data.  Or we can log all the data for postprocessing playback.   
    1516 
    16  
    1717---- 
    1818source for this image is at [source:trunk/sw_design.ppt] 
    1919[source:trunk/doc/sw_design.png] 
     20 
     21---- 
     22== Proposed Changes to Software Design == 
     23 * Tasks to be completed  
     24   * '''2 minute Drill by Oct. 15th''', run DPRG relative waypoint code with only 2 minute software setup time 
     25     * This could include converting over drivers to C++ 
     26       * ChrisDerichs - Converting IMU Python Driver and C++ driver to send same packets 
     27       * KevinBaker - Converting GPS Python Driver into something cleaner,  
     28       * AndrewLynch - Converting S12 driver for C++, with possible expansion of software  
     29      
     30