Contents

1. Course Description
2. Prerequisites
3. Times and Locations
4. Message Board  (Click here to go directly to the message board.)
5. Discussion/Studio Sessions
6. Labs
7. Coding Standards
8. Textbooks and Other Resources
9. Grading
10. Cheating

Course Description

All programming in this course will be done in C++, a language in which you can combine the object-oriented, procedural, and generic programming ideas with which you'll gain experience throughout the semester. Since many students enter this course with experience in Java but not C++, the early portion of the syllabus is designed to give you a breadth-first experience of the major capabilities and features of C++ and to assist your progress up the rest of the C++ learning curve. In addition to providing a reasonable coverage of the C++ language overall, this course also will focus on new features recently introduced to C++ and its libraries, particularly those from the C++11 standard.

Prerequisites

• CSE 132 (Computer Science II) or CSE 241 (Algorithms and Data Structures). If you have not taken either of these courses yet you should take at least one of them before taking CSE 332, especially since we will assume you have at least 2 or 3 previous semesters of programming proficiency before enrolling in this course.
• Proficiency with Java (e.g., from CSE 131 and 132), C, C++, or other general-purpose industrial-strength programming language.

Times and Locations

The first class meeting will be on Tuesday January 13 in Urbauer 218. Following a presentation of the course structure and syllabus that day, we will also make sure each student's login works on the Windows machines in Urbauer 218, and address any problems that may occur.

After that introductory meeting, at each 90 minute class meeting on Tuesdays and Thursdays (except for the dates of the midterm and final reviews and exams), discussions will be held in Urbauer 218 and will consist of about 30 minutes of presentation and discussion of the main issues to consider for that day's topic, followed by a hands-on studio session for the remaining time that day in Urbauer 218. The review sessions prior to the midterm and final exams also will be held in Urbauer 218, but will occupy most to all of the session (and there will not be any studio exercises assigned on those days).

The instructors and teaching assistants will read and respond to postings on the course message board (http://bb.wustl.edu/).

Message Board

Please do not e-mail technical questions to your professor or teaching assistants individually: instead, please post on the message board for all to see, consider, and respond.

Please note that the message board is a vital part of your CSE 332 experience. Participation in the message board (i.e., quantity and quality of your posts) may be considered in your participation grade (and your completion and submission of studio exercises will be the baseline from which the participation grade is calculated).

Discussion/Studio Sessions

In addition to class meeting dates and topics, assigned readings in the required textbook will be provided as we go through the semester.

Although the sequence of topics listed is a good guide to the course content overall, it may be adjusted somewhat as the semester progresses to emphasize, de-emphasize, or inter-relate certain topics depending on the progress and interests of the students in the course. If you are finding a given topic very easy or very difficult, please let your instructors know.

Labs

Labs are to be submitted electronically, and will be graded and returned to you electronically as well. Each lab submission requires a separate ReadMe.txt file containing a lab report writeup. Each assigment web page will describe the procedure for submitting the lab, along with the report format and content requirements. Use of this process is required.

Labs 0, 1, and 2 are to be completed individually, though on labs 3 and 4 you will have the option of working in teams of 2 or 3 people. You should please submit your code and a lab report for each lab sufficiently ahead of its advertised due date and time (shown on the lab assignment web page) that normal e-mail delays etc. do not result in your lab being received late (according to the time stamp put on the e-mail by the CEC e-mail server used by the cse332 account).

Labs received within 24 hours after the posted deadline will be accepted with a 10% penalty up front, and labs submitted between 24 and 48 hours after the posted deadline will be accepted with a 20% penalty up front. Labs submitted after that will not be graded, except in the case of documented extenuating circumstances.

Extensions may be granted in advance on a case-by-case basis as long as the circumstances warrant an extension and the request is made sufficiently ahead of the deadline. Extensions will not be granted after the deadline except in very special cases (such as documented medical emergencies).

You may discuss general questions related your projects with other students, the TAs, and your instructors during studio hours. For additional help please contact your TAs or instructors. While you are encouraged to ask for help on particular problems you may encounter during a project, you must design and implement your own solutions, and prepare your own reports. In particular, while discussion of small code fragments related to specific questions is allowed and encouraged, direct sharing, viewing, or other "reuse" of complete code files (especially if done covertly) is strictly forbidden. If you're not sure whether or not sharing a given section of code is ok, please ask your instructors' permission before doing so.

The following labs have been assigned so far in the course:

• Lab 0 (assigned Tue Jan 13, due 11:59pm Tue Jan 27)
• Lab 1 (assigned Tue Jan 27, due 11:59pm Tue Feb 10)
• Lab 2 (assigned Wed Feb 11, due 11:59pm Tue Mar 3)
• Lab 3 (assigned Mon Mar 16, due 11:59pm Sun Apr 5)
• Lab 4 (assigned Mon Apr 6, due 11:59pm Sun Apr 26)

Coding Standards

Textbooks and Other Resources

• [LLM] Stanley B. Lippman, Jose Lajoie, and Barbara E. Moo, C++ Primer, Fifth Edition, ISBN 0321714113 , Prentice Hall, 2012.

In addition to the required textbook, the following texts may be useful and interesting additions to your programming library:

• Austern, Matthew H., Generic Programming and the STL, Addison-Wesley, 1998.
• Beck, Kent, Extreme Programming Explained: Embrace Change, Addison-Wesley, 1999.
• Kernighan and Ritchie, C Programming Language, 2nd Ed., 1988. Addison-Wesley, 2005.
• Bjarne Stroustrup, The C++ Programming Language: Fourth Edition, Addison-Wesley, 2013.

On-line information sources (please feel free to suggest other good ones):

• The C++ Reference page.

Grading

For students taking the course pass/fail, a passing grade will be equivalent to a D or better in the course.

See the Labs section for a discussion of the labs and how they will be graded.

The midterm and final exams will be comprehensive: each potentially may cover any of the material up to that point in the course. The best way to study for the exams is to keep up with the studio exercises and programming assignments, and to ask lots of questions in the studio sessions throughout the semester.

The last grading component is an evaluation of your participation in the class, and of your application of the tools and techniques discussed in class and labs. This component is separated out to:

1. broaden the evaluation criteria,
2. reduce the weight of the exams a bit, and
3. encourage active participation in discussions/studios.

Percentage completion of the studio exercises (including posting answers to them) will be used as the baseline for evaluating participation grades, though other factors such as attendance and engagement in discussion and studio sessions also may be considered if they differ significantly.

Cheating

For this course, examples of cheating include but are not limited to:

• providing or receiving answers or other assistance during an exam,
• accessing unapproved sources of information during an exam,
• submitting program code written outside this course this semester or by another person not on your team, without specific prior approval by the instructors,
• allowing another student not on your team to copy (or helping them reconstruct) essentially the same solution your team has developed for a programming assignment.

This is a very serious matter. Anyone found cheating will at a minimum lose points equal to the assigned value for the assignment in question (for example if an assignment were worth 10% of the course grade then -10% of the course grade would be assigned), or possibly receive an F for the course. Further action may be taken in extreme cases, possibly including referral to the School of Engineering and Applied Science's formal academic integrity review process.

Furthermore, our policy is that we will make the final determination on what constitutes cheating. If you suspect that you may be entering an ambiguous situation, it is your responsibility to clarify it before we detect it. If in doubt, please ask.

To ensure this policy is implemented consistently and fairly, and that any problems are detected and addressed as early as possible, we may make use of automated program similarity checkers to assess uniqueness and independence of submitted program solutions.