Principles of Software Construction Course Syllabus and Policies

Prerequisites

Evaluation

Evaluation will be based on the following approximate percentages:

Textbooks

Required text: Alan Shalloway and James Trott. Design Patterns Explained: A New Perspective on Object-Oriented Design (2nd Ed.)

Optional references by topic

Time Management

This is a 12-unit course, and it is our intention to manage it so that you spend close to 12 hours a week on the course, on average. In general, 4 hours/week will be spent in class and 8 hours on assignments. Please feel free to give the course staff feedback on how much time the course is taking for you.

Late Work Policy

Each student has five late days for the semester, and you may use up to two late days for each assignment unless the policy for the assignment specifies otherwise. If you run out of late days you may still turn in your work up to two days late, but your work will receive a 10% penalty per day it is late after you run out of late days. Work turned in more than two days late will only be accepted under extraordinary circumstances.

For example, consider a homework assignment due Tuesday night. If you have one late day remaining you may turn in that assignment on Thursday night, which would use your last late day and also receive a 10% penalty. If you have no late days remaining you may still turn in that assignment Thursday night, but it would receive a 20% penalty. Work turned in Friday night (3 days late) would receive no credit regardless of how many late days you have remaining; we only accept work two days late no matter how many late days you have.

A student may use her five late days only for the individual (non-partner-based) assignments in the semester. We will make separate late-day provisions for any partner-based assignments.

Collaboration Policy

We expect that your work on assignments, projects, and exams will be your own work. Thus, you may not copy any part of a solution to a problem that was written by another student, or was developed together with another student, or was copied from another unauthorized source such as the Internet. You may not look at another student's solution, even if you have completed your own, nor may you knowingly give your solution to another student or leave your solution where another student can see it.

Here are some examples of behavior that are inappropriate:

If any of your work contains any statement that was not written by you, you must put it in quotes and cite the source. If you are paraphrasing an idea you read elsewhere, you must acknowledge the source. Using existing material without proper citation is plagiarism, a form of cheating. If there is any question about whether the material is permitted, you must get permission in advance. We will be using automated systems to detect software plagiarism.

It is not considered cheating to clarify vague points in the assignments, lectures, lecture notes, or to give help or receive help in using the computer systems, compilers, debuggers, profilers, or other facilities.

Some assignments are specifically noted as group projects. For these, interpret "you" in the preceeding paragraphs to mean "you and your partner(s)."

Any violation of this policy is cheating. The minimum penalty for cheating (including plagiarism) will be a zero grade for the whole assignment. Cheating incidents will also be reported through University channels, with possible additional disciplinary action. For more information, see the University Policy on Academic Integrity. There is no statute of limitations for violations of the collaboration policy; penalties may be assessed (and referred to the university disciplinary board) after you have completed the course, and some requirements of the collaboration policy (such as restrictions on you posting your solutions) extend beyond your completion of the course.

If you have any question about how this policy applies in a particular situation, ask the instructors or TAs for clarification.