Computer Science 78
Project G.
There are no lectures during the last two weeks of the course.
During that time you will be working in
teams programming N810s. These are embedded Linux devices that have a
bunch of wireless interfaces and sensors (GPS for example).
The Webpage for last year's project including teams, news, announcements, resources, description can be found here.
Important Project Milestones
Lecture 20 kickoffs the project by announding the project teams.
Also, we will release the project description at the end of class.
Projects really get started when the last programming is handed in on Sunday May 17; we then
give a could of tuorials:
Lecture 22 Monday
Project and tutorial I on N810s
(Cory)
Lecture 23 Wednesday
Project and tutorial II on
N810s (Cory)
The
following set of deadlines are important for the progress of the
project. Please note that you need to provide documentation for the
design/code reviews and the final project submission.
Notice
that we will use git for code management for the project. All code
needs to be signed as part of the submission. In addition, the final
report has to be written using latex and the source and a pdf submitted
in the project git directory.
The
following set of deadlines are important for the progress of the
project. Please note that you need to provide documentation for the
design and code reviews and the final project submission.
We will use git for code management for the project. All
code needs to be signed as part of the submission. In addition, the
final report has to be written using latex and the source and a pdf
submitted in the project cvs directory.
4-7 PM Friday May 22 design review. The
project review should include requirements, Design Spec
(inputs/outputs, data flow, data structures, pseudo-code) and
functional decomposition; How the project implementation breaks down
who is doing what. The project review material is due 12 PM day before
review Send tarball documentation to cs78@cs.dartmouth.edu
4-7 PM Friday May 29 code review. The
code review should include the Implementation Spec, unit tests and
whatever code is written up until the review point. The code review
material is due 12 PM day before review. Send tarball documentation and
source tree to cs78@cs.dartmouth.edu
6-9 PM Tuesday June 2 demo or die day. Project presentation (design overview, lessons learnt, etc) and demo of project.
12 AM Wednesday June 3 project reports due.
The report (max 10 pages) written in latex and include:
1) Thread design of client
2) Design Specs
3) Implementation Specs
4) GUI screen dump
5) Lesson learnt
You can send the tarball of the client side code and report to cs78@ by midnight Wed.
project.tar.gz should include:
/project/code (make, scripts, source)
/project/report (includes report.tex and report.pdf)