Contents

1. Course Description
2. Prerequisites
3. Times and Locations
4. Discussions/Sessions
5. Labs
6. Textbooks and Other Resources
7. Grading
8. Cheating

Course Description

Although the studio and lab exercises will be completed in C++ (a multi-paradigm programming language), illustrative examples are selected from a variety of programming language paradigms, and comparisons of how different programming languages treat similar features will be an imporant theme in this course. Studio exercises provided in the course are intended allow familiarization with and exploration of the different features, which will then be applied and your mastery of them evaluated in graded lab assignments and exams.

Prerequisites

• CSE 332S (a.k.a., CSE 504N), Object-Oriented Software Development Laboratory, or equivalent background.
• Proficiency with Java (e.g., from CSE 132), C, C++ ((e.g., from CSE 332)), or another general-purpose industrial-strength programming language.

Times and Locations

Each class meeting, except for the midterm exam (which will be held in a location to be announced), will be held in Urbauer 218.

Except for on the days of the initial course introduction, midterm review, midterm exam, and semester review, each class meeting will consist of an initial 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. Studios will be completed in small groups, and especially for more complex topics may require the group to meet outside of class to finish up any studio exercises that could not be completed during class.

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).

Discussions/Sessions

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.

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 cse425 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 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, your team 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 between teams (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 0 (assigned Wed Sep 2, due 11:59pm Tue Sep 15)
• Lab 1 (assigned Wed Sep 16, due 11:59pm Tue Oct 6)
• Lab 2 (assigned Wed Oct 7, due 11:59pm Tue Oct 27)
• Lab 3 (assigned Wed Oct 28, due 11:59pm Fri Dec 4)

Textbooks and Other Resources

• [Scott] Michael L. Scott, Programming Language Pragmatics, Third Edition, ISBN 0123745144 , Morgan Kaufmann, 2009.

If you are looking for references on the C++ language, the following optional textbook may be helpful.

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

The following on-line references may be helpful as well.

• The C++ Reference page.
• The Solarian Programmer C++11 multithreading tutorial pages.
• The Baptiste Wicht C++11 Concurrency Tutorial pages.
• The Just Software Solutions Multithreading in C++0x tutorial pages (thanks to Zheng Luo for pointing these out).

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 the classroom, studios, and on the message board 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/sessions, labs, etc.

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 class, studio, and lab 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 professor,
• allowing or helping another student not on your team to copy (or 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 similarity checkers to assess uniqueness and independence of submitted program solutions and/or exams.