Syllabus for Spring 2018
A. Tanenbaum, Structured Computer Organization, 6th ed, Prentice Hall, 2012.
Help and Discussion Outside of Lecture
Office Hours and Email
Stephanie and Bruce will both be available to help. If you want to discuss a computer science concept or ask for help regarding an assignment, please do not hesitate to come to our offices.
In addition to coming by our offices for help, you are welcome to send us email with a question. We read our email very frequently and usually respond to such questions as soon as we read them.
Evening TA Help
In order to provide as much help as possible to you as you work on assignments in this course, the CS Dept has hired upper-level CS students to work as TAs in the Davis 102 and 122 lab in the evenings. You are strongly encouraged to take advantage of this resource. The TAs are getting paid to help you, so don't feel guilty about asking them for help. The evening TA hours are: Sunday 4-10pm and Monday 4-6pm and 7-10pm, and Tuesday 4-6pm and 7-10pm.
- 30-Minute Rule: if you have been stuck on a problem, such as a bug, for more than 30 minutes and have made no progress, despite your best efforts, please stop and get help. Email one of us, ask a TA, or consult a peer. If you don't get an answer immediately, do something else for a while. Please do not waste your time on one problem.
- We are always happy to help you with any of your code for your projects. However, the earlier you come to us with questions, the happier we'll be to help you (we usually respond to a last-minute call for major help with the question "Why didn't you start earlier?").
- Please feel free to raise any concerns or complaints about the course directly with either of us. You are also welcome to send us your concerns anonymously. We will gladly respond to them.
Attendance and Participation
For this course to be truly successful, your presence and participation are important. This course covers material that is new enough that the lectures and materials provided by the professor will be the primary resource for the course. Asking questions in class is an important part of learning. When you have a question, ask it. It is highly probable that one of your classmates has the same question. When you have an opportunity to share your opinion or your answer, please speak up. Your professor wants to hear what you have to say. And, of course, to participate in class you must attend class. If you must miss a class, you are responsible for making up the material covered in that lecture.
Class attendance and engagement is part of your participation grade.
Homework assignments must be turned in on time. No late short assignments will be accepted because we will refer to their solutions in class immediate after the deadline.
Projects will generally be due on the Monday after the corresponding lab. Some projects will occur over more than one week. Projects submitted by the specified deadline will receive full credit. Late projects will not receive credit for any extensions, limiting the maximum grade to no more than 26/30.
You may take one extension on a project deadline and hand in the project on Friday instead of Monday for full credit. You cannot request an extension for the final project. To use your extension, email the professor prior to the deadline for the project.
There will be a short quiz on most Fridays during the semester. When computing the final grade, we will drop your lowest quiz grade. You may make up a missed quiz only if you email one of the professors before class to let us know you will not be there and to request a time when you can make up the quiz. It is imperative that you let us know before before class begins.
Collaboration and Academic Honesty
Computer science, both academically and professionally, is a collaborative discipline. In any collaboration, however, all parties are expected to make their own contributions and to generously credit the contributions of others. In our class, therefore, collaboration on homework and programming assignments is encouraged, but you as an individual are responsible for understanding all the material in the assignment and doing your own work. Always strive to do your best, give generous credit to others, start early, and seek help early from both your professors and classmates.
In addition to the ethical implications of dishonesty, you undermine your ability to learn when you cheat. Honesty, integrity, and personal responsibility are cornerstones of a Colby education and provide the foundation for scholarly inquiry, intellectual discourse, and an open and welcoming campus community. These values are articulated in the Colby Affirmation and are central to this course. Students are expected to demonstrate academic honesty in all aspects of this course.
The following rules are intended to help you get the most out of your education and to clarify the line between honest and dishonest work. We reserve the right to ask you to verbally explain the reasoning behind any answer or code that you turn in and to modify your project grade based on your answers. It is vitally important that you turn in work that is your own. We do use automated plagiarism detection software, so please be sure to abide by these, rather minimal, rules. Reports of academic dishonesty are handled by an academic review board and a finding of academic dishonesty may result in significant sanctions. For more details on Colby's Academic Integrity policies and procedures, see colby.edu/academicintegrity.
- If you have had a substantive discussion of any programming project with a classmate, then be sure to cite them in your project report. If you are unsure of what constitutes "substantive", then ask me or err on the side of caution. As one rule of thumb, if you see more than 10 lines of someone else's code, then you should cite them. You will not be penalized for working together.
- You must not copy answers or code from another student either by hand or electronically. Another way to think about it is that you should be using a natural language when takling with one another, not a computer language.
Sexual Misconduct/Title IX Statement
Colby College prohibits and will not tolerate sexual misconduct or gender-based discrimination of any kind. Colby is legally obligated to investigate sexual misconduct (including, but not limited to sexual assault and sexual harassment).
If you wish to speak confidentially about an incident of sexual misconduct, please contact Colby Counseling Services (207-859-4490) or the Director of the Gender and Sexual Diversity Program, Emily Schusterbauer (207-859-4093).
Students should be aware that faculty members are considered responsible employees; as such, if you disclose an incident of sexual misconduct to a faculty member, they have an obligation to report it to Colby's Title IX Coordinator. "Disclosure" may include communication in-person, via email/phone/text, or through class assignments.
To learn more about sexual misconduct or report an incident, visit http://www.colby.edu/sexualviolence/.
Colby College is a community dedicated to learning and committed to the growth and well-being of all its members.
As a community devoted to intellectual growth, we value academic integrity. We agree to take ownership of our academic work, to submit only work that is our own, to fully acknowledge the research and ideas of others in our work, and to abide by the instructions and regulations governing academic work established by the faculty.
As a community built on respect for ourselves, each other, and our physical environment, we recognize the diversity of people who have gathered here and that genuine inclusivity requires active, honest, and compassionate engagement with one another. We agree to respect each other, to honor community expectations, and to comply with College policies.
As a member of this community, I pledge to hold myself and others accountable to these values.
- We respect each other and ourselves.
- We respect our physical spaces on campus.
- We respect our academics and complete work honestly.
Weekly Topics and Readings
||Tanenbaum, Chapter 1, 2.2|
Tanenbaum, Chapter 3.1, 3.2
Combinational Circuits Project
Tandenbaum, Chapter 3.1, 3.2
Combinational Circuits Project II
Tanenbaum, Chapter 3.3
Sequential Circuit Design
Tanenbaum, Chapter 4.1
Programmable Circuit Design
Tanenbaum, Chapter 2
Programmable Circuit Design II
||Tanenbaum, Chapter 2|
Tanenbaum, Chapters 2, 5
Tanenbaum, Chapter 5
Tanenbaum, Chapter 7
Tanenbaum, Chapter 4.4, 4.5
||Tanenbaum, Chapter 6|
||Tanenbaum, Chapter 8|