• Personnel:

	Instructor	TA	TA	TA	TA	TA
Name	Victor Adamchik	Michael Murphy	Waqar Ahmad	Norman Ponte	Sudev R Bohra	Matthew Salim
Email	adamchik	mjmurphy	wahmad	nponte	sbohra	msalim
Office	7719 GHC	Citadel	Citadel	Citadel	Citadel	Citadel
Office hours	Tue, Thu 12 - 1 pm	Wed 4:30 - 6 pm	Thu 4:30 - 6 pm	Tue 4:30 - 6 pm	Mon 4:30 - 6 pm	Sun 4:30 - 6 pm

• Schedule of classes:

	Days	Time	Room
Lectures	MTWRF	10:30 - 11:50am	GHC 4307
Recitations	Tu, Th	03:00 - 04:20pm	GHC 5207 and 5210
Labs	Mon, Wed	03:00 - 04:20pm	GHC 5207 and 5210

• Textbook:

There is no course textbook Lecture notes and other resources will be provided

• Course Environment:

Course Home Page: http://www.cs.cmu.edu/afs/cs/academic/class/15122-n16/www

Course discussion board: Piazza

• Coursework Grade:

  Course Assignments	Weights
  Final test	20%
  2 Midterms	10% + 15%
  6 Quizzes	12%
  8 HWs	43%

• Coursework Grading Scale:

  Grades for the course will be determined by a curve.

  Individual cases, especially those near the cutoff points may then be adjusted upward or downward based on factors such as extra credit and participation in lecture and recitation discussions.

• Assignments:

The homework assignments are critical part of the course. They are designed to test your learning Experience has shown that concepts are best learned by direct engagement---in our case by applying them to example problems or by implementing them in computer programs. Each assignment consists of TWO parts: theory and programming.

• The theory part is to be handed in class. You should type up your solutions or write them neatly by hand. You may use either LaTeX or Word or Mathematica or any other typesetting app. No late submission will be accepted.
• The programming part is to be handed in electronically (via Autolab) by 11:59pm on the specified due date. No late submission will be accepted.

Exceptions to the late policies above will be granted only in exceptional circumstances and must be discussed with and approved by the course instructor in advance.

Programming assignments will be graded based on style (modularity, effective use of data abstraction, readability, commenting, etc.) and functionality (correctness and efficiency of the program on the test inputs.) A working program is not sufficient for full credit. Make sure you do a thorough data validation. Your code should be properly annotated with comments.

• Collaboration:

We do allow collaboration on SOME programming assignments, though it is limited to max 2 students per group. If you work as part of a group, you only submit one copy of the program with both names in it. In addition, please submit in the header of the main file a description of the work each partner has done. Please be specific. We expect that both partners in the group are actively involved in the coding and debugging of all parts in some way. We may ask you to explain the code and how you debugged and tested it.

One possibility is that each person in the group becomes a lead programmer for at least one part. After you have debugged your part, your partner is responsible for testing your part. Having someone who did not write the code test the code is a standard quality assurance approach used in industry. Alternatively you can do pair programming (two people, one computer). Another approach is to divide up the programming into parts, and then do a "code review," where the one who did the programming explains the code to the other, line by line. Code reviews are common in industry, as is pair programming, which is an "extreme programming" practice.

• Cheating:

For homework assignments, students are encouraged to talk to each other, to the course staff, or to anyone else about the assignments. This assistance, though, is limited to the discussion of the problem and perhaps sketching of general approaches to a solution. Each student must develop his or her own solutions to the homework. Consulting another student's solution is prohibited, and submitted solutions may not be copied from any source.

Each programming assignment will be MOSSED for Plagiarism Detection.

The issue of cheating will be taken seriously by the instructor and TAs, and homerwork asignments will be routinely checked for violations, which will be handled in accordance with the University regulations.

Last updated Thursday, June 23, 2016

Victor S. Adamchik,  Computer Science Department,  Carnegie Mellon University, Pittsburgh, PA.