Finishing Up

1
Finishing Up

• Grading components

2
Step 1 Stability

• Your system must be error free when running, and
  error free when compiling.
• A stable system that might lack features is
  more valuable than s feature-rich but buggy
  system.
• Emphasize STABILITY.

3
Step 2 Reconstruction

• Someone must be able to EASILY re-build your
  system from scratch.
• All compilation files and instructions in one
  place.
• Schematics, hook-up, assembly drawings.
• Detailed parts list, including where-to-purchase.

4
Step 3 Test

• Write a test checklist.
• Provide a test report including failures. Test
  failures dont impact your grade.
• For each failure, write a recommendation for
  fixing.

5
Step 4 the API

• We need to enhance your system over the next
  year.
• Major module descriptions.
• Extending the system please provide
  instructions for most likely scenarios.

6
Step 5 Documenting the experience

• Diary and discovery.
• Keep a notebook of the last weeks

7
Step 6 - Demo

• Demo for the class
• Videotape
• Whenever youre ready. Before April 27th.

8
ISSUES
9
Flight Sim

• Changing the motors
• Adapting to new screen resolutions

10
Wheelchair

• Sensors and video
• Total integration
• GUI
• Mounting and assembly

11
Button Builder A

• An AC relay box worthy of your product
• Software integration

12
Button Builder B

• Student info database

13
Community Database

• Interfacing to external data sources
• Hosting
• GUI
• Yellow to white pages

14
Single Switch

• Wide population use
• Many types of input devices

15
Badge Tracking

• Reports

16
Blind Obstacle

• Taming the hardware

17
Last

• Web site contents, if your site is going away
• Your cell phone numbers
• We have to audit the hardware an Incomplete
  grade until that is finished
• No more Mondays
• Where should we have a party?