This page http://www.cs.bu.edu/~jappavoo/webpages/cs210.html will NOT be generally updated. We will typically use the course's piazza site (http://piazza.com/class#fall2012/cs210 for all online information other than grades. For grade information we will use the course's Blackboard site (http://blackboard.bu.edu)
- Instructor & Office Hours
- Teaching Fellow & Office Hours
- Time And Place
- Class Schedule
- Online References
- Academic Honesty
Some of the critical Semester Dates are below:
|1||Sept 4, 6|
|2||Sept 11, 13|
|3||Sept 18, 20|
|4||Sept 25, 27|
|5||Oct 2, 4|
|6||Oct 11||NO CLASS ON TUESDAY|
|7||Oct 16, 18|
|8||Oct 23, 25|
|9||Oct 30, Nov 1|
|10||Nov 6, 8|
|11||Nov 13, 15|
|12||Nov 20||NO CLASS THURSDAY|
|13||Nov 27, 29|
|14||Dec 4, 6|
|15||Dec 11||TUESDAY IS LAST CLASS|
|Midterm 1||Oct 4||TBP|
|Midterm 2||Nov 8||TBP|
|PS 1: 'C' Basics and Data Representation||OUT: Tuesday Sept 11, IN: Tuesday Sept 25, 1:30||ps1.pdf||ps1sol.pdf|
|PS 2: Programming Representation||OUT: Oct 8, IN: Oct 23, 1:30||ps2.pdf||ps2sol.pdf|
|PS 3: Caches & Virtual Memory||OUT: , IN:|
|PS 3: Input Output||OUT: , IN:|
|PA 1: Buffer Lab||OUT: Sept 25, IN: Oct 16, 1:30pm||handout|
|PA 2: Performance Lab||OUT: Oct 22, IN: Nov 13, 1:30pm||handout , resources||---|
|PA 3: 6502 Lab||OUT: Tues Nov 20, IN: Thursday Nov. 29, Dec. 6, Dec. 11 1:30pm||handout , resources||---|
You will be required to submit an electronic copy of your code, in addition to both electronic and hard copies of supporting documentation and any requested written report(s). When explicitly specified, you may have the option to work in teams of two on large programming assignments.
Unless automated and otherwise specified, the program you submit should work correctly and be documented. You should submit an electronic copy of the following:
1. Program: a program listing containing in-line documentation (i.e., comments).
2. Design document: a separate file (a page or so) describing the overall program design, a verbal description of "how it works", and design tradeoffs considered and made. Also describe possible improvements and extensions to your program (and sketch how they might be made).
3. Testing document: a separate file describing how to run your program. Specify the steps that must be followed to successfully run your program. Also, describe the tests you ran on your program to convince yourself that it is indeed correct. Also describe any cases for which your program is known not to work correctly.
It is fine to submit all the above documentation in one README file, given you have clear subtitles. To save trees, you are required to submit a hard copy only of the above supporting documentation and any requested written report(s), but not of your program listing/code.
gsubmit is an electronic file submission engine which will submit files or directories of files to the grader so they can be marked.
Every file submitted by a given student for a given assignment should have a unique file name. If a file is submitted with a duplicate name it will either overwrite the file or generate an error message.
To make it easy for the grader to find the files relating to a specific programming assignment, all files for each assignment should be stored in a subdirectory called pa1, pa2, pa3, etc. and the entire directory should be submitted.
Copy all files necessary for that assignment into the new subdirectory, using the cp command: e.g.,
cp prog1.s pa5
Be sure to copy only the files you need to submit into this subdirectory.
Use gsubmit to submit the entire subdirectory:
gsubmit cs210 -cp pa5
If submission is successful a status message will be printed.
gsubmit cs210 -cp README.txt pa5
gsubmit cs210 -rm pa5/prog1.sThen resubmit it:
gsubmit cs210 -cp prog1.s pa5
gsubmit cs210 -ls
gsubmit cs210 -cat pa5/prog1.sYou can store this in a file foo by typing:
gsubmit cs210 -cat pa5/prog1.s > foo
Assignments must be completed individually. Discussion of issues in computer systems is encouraged, but representing the work of another person as your own is expressly forbidden. This includes "borrowing", "stealing", copying programs/solutions or parts of them from others. We may use an automated plagiarism checker. Cheating will not be tolerated under any circumstances. Handing in your own work a day or two late will affect your grade far less than turning in a copy of someone else's work on time!
See the CAS Academic Conduct Code, in particular regarding plagiarism and cheating on exams. Copies of the CAS Academic Conduct Code are also available in room CAS 105. A student suspected to violate this code will be reported to the Academic Conduct Committee, and if found culpable, the student will receive a grade of "F" for the course.
Any resources, including material from other students (current or past), that are used, beyond the text or that provided by the TF or professor must be clearly acknowledged and attributed. Using such material may at the discretion of the TF or professor result in a lower grade. However, if such material is used and not acknowledged and attributed, it will automatically be considered as possible academic misconduct.