I will be available in my office (OHS 303) from 10:30-11:20 on Mondays, Tuesdays, Thursdays*, and Fridays, as well as by appointment. Or try your luck: just stop by and see whether my door is open. You may send me electronic mail at email@example.com or call me at extension 7466. I'll try to put any updates to my office hours on my web page, so check there if in doubt. (*Exception: on September 20th, the time will be 2:30-3:20.)
Attendance is expected for all lab days. (If you turn in a lab report early, you are excused from the remaining days devoted to that lab.) I will excuse up to two absences per student, for any reason. Use yours wisely. If you exceed this allowance, I may reduce your course grade by one letter grade.
The final deadline for rewrites of homework problems is 9am on October 10th for chapters 1-4 and appendix B, 9am on November 8th for chapters 5 and 6, and 9am on December 14th for chapters 7-9.
Unless I indicate that a particular problem must be done individually, you may work on any problem in a group of two or three students. One copy of the solution produced by the team should be turned in, with all team members' names on it. Write “we all contributed fairly to this solution” and have all team members sign under that statement.
There will be two intra-term tests and a final exam, as shown on the syllabus below. If you have a conflict with a testing time, please contact me as soon as possible to make an alternative arrangement.
Exams will be closed-book and mostly closed-notes. You may, however, use a single 8 1/2 by 11 sheet of paper with hand-written notes for reference. (Both sides of the sheet are OK.)
Any substantive contribution to your solution by another person or taken from a publication should be properly acknowledged in writing. Failure to do so is plagiarism and will necessitate disciplinary action.
The same standards regarding plagiarism apply to team projects as to the work of individuals, except that the author is now the entire team rather than an individual. Anything taken from a source outside the team should be be properly cited.
One additional issue that arises from the team authorship of project reports is that all team members must stand behind all reports bearing their names. All team members have quality assurance responsibility for the entire project. If there is irreconcilable disagreement within the team it is necessary to indicate as much in the reports; this can be in the form of a “minority opinion” or “dissenting opinion” section where appropriate.
You are expected to be familiar with the college academic honesty honor code policy and to comply with that policy. If you have any questions about it, please ask.
If you are too sick to complete an assignment on time, you will not be penalized. Simply write “late due to illness” at the top of the assignment, sign your name and hand it in. Other circumstances will be evaluated on a case-by-case basis.
If you have a learning, psychological, or physical disability for which a reasonable accommodation can be made, I would be happy to refer you to the college's disability services coordinator and to cooperate in the accommodation process. It is generally best if this can be done as soon as possible.
|9/5||1||Computer abstractions and technology|
|9/7||Lab 0: Under the hood|
|9/10||2.7-2.8||Procedures and strings in assembly|
|9/11||2.9-2.11||More on assembly programming|
|9/12||A.1-A.6,A.9||Assembly programming tools|
|9/13||2.13,2.15||Assembly programming examples|
|9/14||Lab 1: Elementary assembly programming|
|9/17||Lab 1 (continued)|
|9/18||2.16-2.18||Yet more on assembly language|
|9/19||No class (finish lab 1?)|
|9/20||No class (watch history video?)|
|9/21||3.1-3.3||Two's complement, addition, and subtraction||Lab 1|
|9/24||Lab 2: More advanced assembly programming|
|9/26||Lab 2 (continued)|
|9/27||3.6||Floating point arithmetic|
|10/1||Lab 2 (continued)|
|10/2||No class (attend Nobel Conference)|
|10/3||No class (attend Nobel Conference)|
|10/5||More on Sequential logic|
|10/9||EPA summary||Energy and performance|
|10/10||Review; catch-up||HW rewrites (1-4, B)|
|10/11||Intra-term test 1|
|10/12||Lab 2 (continued)|
|10/15||5.1-5.3||A simple datapath|
|10/16||5.4-p.314||A single-cycle processor|
|10/17||Lab 2 (continued)|
|10/18||5.4||More on the single-cycle processor|
|10/19||5.5||A multiple-cycle processor||Lab 2|
|10/22||No class (reading day)|
|10/23||No class (reading day)|
|10/24||More on the multiple-cycle processor|
|10/29||6.2||A pipelined datapth|
|11/5||Lab 3: Processor performance|
|11/6||6.8-6.12||Superscalar and advanced pipelining|
|11/7||Lab 3 (continued)|
|11/8||Review; catch-up||HW rewrites (5-6)|
|11/9||Intra-term test 2|
|11/14||Lab 3 (continued)|
|11/16||Lab 3 (continued)|
|11/20||7.6-7.8||Example memory hierarchies|
|11/21||No class (Thanksgiving)|
|11/22||No class (Thanksgiving)|
|11/23||No class (Thanksgiving)|
|11/30||Lab 4: Memory system performance|
|12/3||Lab 4 (continued)|
|12/4||More on networks|
|12/5||Lab 4 (continued)|
|12/7||Lab 4 (continued)|
|12/11||9.1-9.3||Bus-based MIMD architectures||Lab 4|
|12/12||9.4-9.6||Network-based MIMD architectures|
|12/13||9.7-9.10||More on multiprocessors|
|12/14||Review; catch-up; evaluation||HW rewrites (7-9)|
Course web site: http://www.gustavus.edu/+max/courses/F2007/MCS-284/