Newest System Architecture Document

Here is the newest System Architecture Document. Please read and post comments on changes to be made. If you have comments on the general format of the document, post them as well or meet me in the library at 11am tomorrow morning:

System Architecture Document

Purpose:
This document entails all system components as well as the class members that are responsible for implementing the component. It also includes a higher level description of the deliverables for each group.

Components:
Graphical User Interface
Group: Ryan Bontreger, Paul Flegel, Sean Cavanaugh, Alex Bussell
This group is responsible for creating a web based user interface and the https login.

Communications
Group: David Marshall, Stephan Wesson, Chris Abbott, (David) Kin Ho, Rob Brenan
This group is responsible for communications between the server and client on the laptops and creating the server.

Nerf Gun / Camera
Group: Jonathan Dinger, Brian Peasley, Chris Cherry
This group is responsible for reverse engineering the Nerf gun, implementing directional and firing commands, and integrating their components with the rest of the system. They are also responsible for capturing an image from the camera, pan/tilt/zoom of the camera, and decoding/encoding the image to/from a JPEG.

Rover
Group: Michael King, Jesse Allan Hoffman, Dustin Evans, Brittany Harris
This group is responsible for basic robot movement functionality.

Sensor
Group: Mary Maier, Keith Schuck, Joshua Hilley
This group is responsible for discovering a solution for sensing the proximity of darts to the robot under fire. They will then have to interface with the communications group in order to relay that the robot has been hit.

Additional Notes:
In the case that all groups have finished assigned tasks and the system is fully integrated before the deadline, optional components will then be investigated.

Sounds good to me....Definitely don't see nothing wrong with it after looking over it a few times...

Some suggestions:

Add something in GUI about having controls that control the robot. Yes, we know it, but assume the readers are stupid/clueless. Also mention that it will interface with the COMM group. Maybe note that we're only planning on testing this in the lab, so they won't get ideas about remote control across the country.

Add more detail to COMM about providing the API for all communications over the wireless, as well as rerouting commands client-side. As such, it will be interfacing with all the other groups. Also, I thought this was just comms, and the server fell under the GUI group?

Mention in both the nerf/camera group and the movement group that they will be interfacing with the COMM group.

Possibly mention that all movements (rover, camera, dart gun, etc) will either be click-and-hold or click-to-start, click-to-stop. That will probably be later though. But if we say something he can't come back later and say no, I wanted you to do it the other way.

Eh, think about it anyway.

Dinger, I think the movement issue should be addressed in the updated System Spec Doc. Here is what I've got for the Sys Arch:

System Architecture Document

Purpose:
This document entails all system components as well as the class members that are responsible for implementing the component. It also includes a higher level description of the deliverables for each group.

Components:
Graphical User Interface
Group: Ryan Bontreger, Paul Flegel, Sean Cavanaugh, Alex Bussell
This group is responsible for creating a web based user interface and the https login. They will have the controls for the robot movement and will interface with the Communications group.

Communications
Group: David Marshall, Stephan Wesson, Chris Abbott, (David) Kin Ho, Rob Brenan
This group is responsible for communications between the server and client on the laptops and creating the server. They will provide the API for all communications over the wireless network as well as rerouting commands on the client side.

Nerf Gun / Camera
Group: Jonathan Dinger, Brian Peasley, Chris Cherry
This group is responsible for reverse engineering the Nerf gun, implementing directional and firing commands, and integrating their components with the rest of the system. They are also responsible for capturing an image from the camera, pan/tilt/zoom of the camera, and decoding/encoding the image to/from a JPEG. They will interface with the communications group.

Rover
Group: Michael King, Jesse Allan Hoffman, Dustin Evans, Brittany Harris
This group is responsible for basic robot movement functionality. They will interface with the communications group.

Sensor
Group: Mary Maier, Keith Schuck, Joshua Hilley
This group is responsible for discovering a solution for sensing the proximity of darts to the robot under fire. They will then have to interface with the communications group in order to relay that the robot has been hit.

Additional Notes:
Testing will only be done in the lab, limiting the range of functional operation of the remote control of the robot to that space. In the case that all groups have finished assigned tasks and the system is fully integrated before the deadline, optional components will then be investigated.