Contents

1. Course Description
2. Prerequisites
3. Times and Locations
4. Teaching Assistants
5. Message Board  (Click here to go directly to the message board.)
6. Discussions/Sessions
7. Labs
8. Coding Standards
9. Textbooks and Other Resources
10. Grading
11. 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.

Prerequisites

• CSE 132, Computer Science II
• CSE 241, Algorithms and Data Structures
• Proficiency with Java (e.g., from CSE 132), C, C++, or other general-purpose industrial-strength programming language.

Times and Locations

• Lab Section A: 1 to 3 pm
• Lab Section B: 3 to 5 pm

There will not be a lab session on Wednesday August 26, and the first class meeting will be at 10am on Thursday August 27, in Cupples II 217. Following a presentation of the course structure and syllabus that day, you will head upstairs to the Cupples II 300 attic studio space to make sure your login works on the Windows machines there, or to address any problems that may occur.

After that introductory meeting, each 90 minute class meeting on Tuesdays and Thursdays (except on Oct 15 and 20 and Dec 8 when the midterm review, midterm exam, and semester review will be held respectively) will consist of 30 minutes of presentation and discussion (in the Cupples II 217 classroom) of the main issues to consider for that day's topic, followed by a hands-on studio session (in the Cupples II 300 attic studio space) for the remaining 60 minutes that day.

Lab sessions, during which you will have dedicated time and our assistance for working on your lab assignments, will be held on Wednesdays from 1-3pm and 3-5pm in the Cupples II 300 attic studio space.

Teaching Assistants

• David Pilla, dgp3@cec.wustl.edu
• Justin Meden, jem6@cec.wustl.edu

The teaching assistants will be available during the scheduled studio and lab sessions, to answer questions about the programming assignments and to offer advice as you develop and debug your solutions.

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

Message Board

Please do not e-mail technical questions to your professor 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) will count toward your participation grade.

Discussions/Sessions

In addition to class meeting dates and topics, page numbers for reference material in the optional textbooks will be provided as we go through the semester. These are intended as an index to useful material to read at your discretion: while reading all of the page ranges given for both books is possible, skimming them followed by a more focused selection of which to read in-depth based on the ease with which you are able to digest and apply the material is likely a more effective use of your time.

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 professor 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 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, like the studio exercises, will be performed in teams of 2 or 3 people. You should please submit your code and a lab report for each lab by its advertised due date and time shown on the course web page and the lab assignment web page. Labs submitted 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.

You may discuss general questions related your projects with other students in lecture and labs, during lecture and lab hours respectively, and on the message board. While you are encouraged to post and 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 posting 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 professor's permission before doing so.

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

• Lab 1 (Due 11:59pm Tuesday, Sep 15)
• Lab 2 (Due 11:59pm Tuesday, Sep 29)
• Lab 3 (Due 11:59pm Tuesday, October 20)
• Lab 4 (Due 11:59pm Friday, November 13: note new date)
• Lab 5 (Due 11:59pm Tuesday, December 8)

Coding Standards

Textbooks and Other Resources

• [Prata] Stephen Prata, C++ Primer Plus, Fifth Edition, ISBN 0-672-32697-3 , SAMS, 2005.
• [Deitel (6th Ed.)] Deitel and Deitel, C++ How to Program, Sixth Edition, ISBN 0-13-615250-3 , Prentice Hall, 2008.
• [Deitel (7th Ed.)] Deitel and Deitel, C++ How to Program, Seventh Edition, ISBN 0-13-611726-0 , Prentice Hall, 2010.

In addition to the required textbook, the following texts may be useful and interestingadditions 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.
• Cline and Lomow, C++ FAQ, 1994.
• Coplien, Advanced C++: Programming Styles and Idioms, 1992.
• Kernighan and Ritchie, C Programming Language, 2nd Ed., 1988.
• Lippman, Lajoie, and Moo,C++ Primer, Fourth Edition, Addison-Wesley, 2005.
• Meyers, Effective C++, 1992.
• Meyers, More Effective C++, 1995.
• Stroustrup, The C++ Language, 3rd. Ed., 1997.

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

• The C++ Reference page.

Grading

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 will cover 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 during the semester, and to ask lots of questions in classroom, studios, and on the message board throughout the semester.

The final 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/sessions, labs, and on the message board.

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 professor,
• 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.