15-214 Principles of Software System Construction Course Policies


Software engineers today are less likely to design data structures and algorithms from scratch and more likely to build systems from library and framework components. In this course, students engage with concepts related to the construction of software systems at scale, building on their understanding of the basic building blocks of data structures, algorithms, program structures, and computer structures. The course covers technical topics in four areas: (1) concepts of design for complex systems, (2) object oriented programming, (3) static and dynamic analysis for programs, and (4) concurrent and distributed software. Student assignments involve engagement with complex software such as distributed massively multi-player game systems and frameworks for graphical user interaction.

After completing this course, students will: Prerequisites:


Evaluation will be based on the following approximate percentages:

Time Management

This is a 12-unit course, and it is my 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 the course staff feedback on how much time the course is taking for you.

Late Work Policy

Each student has 5 late days for the semester which can be used in any assignment, so long as the assignment hand-in is not on the critical path for the following assignment.  When turning in your work, just let the instructor or TA know how many late days you are using.  Work turned in late after the late days are used up will only be accepted under extraordinary circumstances.

Collaboration Policy

We expect that your work on assignments, projects, and exams must 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.

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 and Plagiarism.

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