Computing Systems Discovered / Nisan
& Schocken / Spring 2002
Students in this course are allowed to submit homework assignments in
PAIRS. At the same time, each pair must work on its own.
In both HDL and Java programming, you should follow Java programming conventions and style (variable names, indentation, etc.). Documentation should be brief and to the point. Messy, unmodular, under-documented, or over-documented works will get points penalties.
Hardware projects: Submit only the *.hdl files that you wrote.
Assembly projects: Sumit both your *.asm and *.prg files.
Software projects: Submit only the *.java files that you wrote. Do not submit any *.class or other project files.
Each project should be submitted in two forms:
Paper version: Printouts of all the source files that make up your project. Put page numbers, staple all the pages at the top left corner, and put the course name and the names of BOTH students on the front page. Don't use envelopes; Don't use plastic bags; Don't use fancy folders; Just staple the pages together.
Electronic: All the source files that make up your project, in one file named proj-id1-id2.zip, where "proj" is the project name, and "id1" and "id2" are the student ID's, where id1<id2. This zip file should be submitted via email, as explained below.
Important: Your paper and electronic submissions should include NOTHING ELSE except for the source files that you wrote, and possibly a readme file, if there's something you want to tell us.
The zip file should be emailed as follows:
DATE/TIME: must be on or before the homework submission deadline
SUBJECT: xxx (=project name)
MESSAGE: The details of the two
participated in the project.
For each student, list student name, ID, and email.
Relax. All the projects in this course are highly modular, with incremental test files. Each hardware project consists of many chip modules (*.hdl programs), and each software project consists of many software modules (methods). It is best to treat each project as a modular "problems set", and try to work out as many problems as you can. You will get partial credit for your work.
It's not the end of the world. Hand in whatever you did, and explain what works and what doesn't. If you want, you can also supply test files that you developed, to demonstrate working and non-working parts of your project. Instead of trying to hide the problem, be explicit and clear about it. You will get partial credit for your work.
"Errors are the portals of discovery" (James Joyce)