| Instructors: | Chris Gill |
| Office Hours: Urbauer 214 Wed 1:30-2:30pm, or Jolley 514 by appointment | |
| Phone: (314) 935-7538 E-mail: cdgill@cse.wustl.edu | |
| Ruth Miller | |
| Office Hours: Jolley 510 Mon and Wed 8:45-9:45am, Urbauer 214 Wed 2:30-3:30pm, or by appointment | |
| Phone: (636) 299-0238 E-mail: ruth.miller@seas.wustl.edu | |
| Message Board: | We will also frequently read and respond to postings on the course message board (http://classes.engineering.wustl.edu/cse332/bb). |
http://www.cse.wustl.edu/~cdgill/courses/cse332/
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.
The first class meeting will begin at 10am on Wednesday Aug 29 in Urbauer 218, and the first lab sessions will be that same afternoon in Urbauer 214. Each class meeting, except for the midterm exam for which a different location will be announced, will be held in Urbauer 218.
Except for on the days of the 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).
Lab sessions, during which you will have dedicated time and our assistance for working on your lab assignments, will be held on Wednesdays 1-2:30pm (A) or 2:30-4pm (B), starting on Wednesday August 29.
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 instructors and teaching assistants will read and respond to postings on the course message board (http://classes.engineering.wustl.edu/cse332/bb).
Please do not e-mail technical questions to your instructors 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.
If you have any trouble registering for or accessing the message board, please let us know right away!
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.
| Date | Topic | Reference Material |
|
Wed Aug 29
Lab 1 (assigned Wed Aug 29, due 11:59pm Fri Sep 7) |
Course introduction and syllabus overview (slides in ppt) C++ program structure and development environment (slides in ppt) (studio exercises in pdf) |
Prata 6th Ed. pp. 18-61; Deitel 8th Ed. pp. 17-27, 38-46 |
| Mon Sep 3 | Labor Day Holiday | |
| Wed Sep 5 |
C++ data types, namespaces, input, and output (slides in ppt) (studio exercises in pdf) (code example directory) |
Data types Prata 6th Ed. pp. 65-153; Deitel 8th Ed. pp. 65-95, 267-286, 1005-1006 Namespaces Prata 6th Ed. pp. 482-497; Deitel 8th Ed. pp. 979-982 C++ style strings Prata 6th Ed. pp. 951-968; Deitel 8th Ed. pp. 696-712 STL vectors and lists Prata 6th Ed. pp. 979-992, 1012-1017; Deitel 8th Ed. pp. 307-313, 863-875 Input and output Prata 6th Ed. pp. 1061-1147; Deitel 8th Ed. pp. 595-623, 660-669 |
|
Mon Sep 10
Lab 2 (assigned Wed Sep 12, due 11:59pm Fri Sep 21) |
C++ functions, classes, and templates (slides in ppt) (studio exercises in pdf) (code example directory) |
|
| Wed Sep 12 |
Design Patterns I (Iterator and Factory Method) (slides in ppt) (studio exercises in pdf) |
|
| Mon Sep 17 |
C++ functions and the call stack (slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed. pp. 305-383, 409-412; Deitel 8th Ed. pp. 194-248 |
| Wed Sep 19 |
C++ debugging (slides in ppt) (studio exercises in pdf) (code example directory) |
|
|
Mon Sep 24
Lab 3 (assigned Mon Sep 24, due 11:59pm Sat Oct 13 (note new deadline)) |
C++ exceptions (slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed. pp. 896-920; Deitel 8th Ed. pp. 632-644 |
| Wed Sep 26 |
C++ pointers, arrays, and references (slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed., pp. 153-160, 167-178, 383-401, 408-409; Deitel 8th Edition, pp. 267-364 |
| Mon Oct 1 |
C++ classes
(slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed. pp. 401-405, 505-559, 578-580; Deitel 8th Edition pp. 64-95, 379-408, 414-445 |
| Wed Oct 3 |
C++ subclassing and inheritance polymorphism (slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed. pp. 405-408, 707-830, 877-892, 922-927, 933-946; Deitel 8th Edition pp. 499-529, 534-574 |
| Mon Oct 8 |
Review for Midterm Exam (slides in ppt) (sample questions in pdf: note that this is not intended as a study guide, e.g., some of the material mentioned is being covered AFTER the midterm this semester, but rather as an illustration of the kinds of questions I tend to ask on a midterm exam.) |
|
| Wed Oct 10 |
|
|
|
Mon Oct 15
Lab 4 (assigned Mon Oct 15, due 11:59pm Fri Nov 2) |
Design Patterns II (Adapter, Memento, and Observer) (slides in ppt) (studio exercises in pdf) |
|
| Wed Oct 17 |
C++ memory management (slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed. pp. 160-167, 178-184, 478-482, 920-921, 931-933; Deitel 8th Edition pp. 469-471, 645-650, 749 |
| Mon Oct 22 |
Memory management for C++ classes (slides in ppt) (studio exercises in pdf) (code example directory) |
|
| Wed Oct 24 |
More on C++ memory models and memory management idioms (slides in ppt) (studio exercises in pdf) (copy trick code example directory) (shared_ptr code example directory for Visual Studio 2010) |
|
| Mon Oct 29 |
C++ function and operator overloading
(slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed. pp. 412-418, 564-578, 581-621; Deitel 8th Edition pp. 234-236, 451-491 |
| Wed Oct 31 |
Design Patterns III (Singleton, Prototype, and Visitor) (slides in ppt) (studio exercises in pdf) |
|
|
Mon Nov 5
Lab 5 (assigned Mon Nov 5, due 11:59pm Fri Nov 30) |
Generic programming techniques in C++ (slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed. pp. 992 Deitel 8th Edition pp. 851-852 |
| Wed Nov 7 |
Interface polymorphism with C++ templates (slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed. pp. 419-442, 830-866, 892-896 Deitel 8th Edition pp. 236-239, 579-593 |
| Mon Nov 12 |
More template examples and ideas (slides in ppt) (studio exercises in pdf) (code example directory) |
|
| Wed Nov 14 |
C++ STL containers in depth (slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed. pp. 978-991, 1007-1026, 1270-1286 Deitel 8th Edition pp. 853-856, 863-890 |
|
Mon Nov 19 |
C++ STL iterators in depth (slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed. pp. 992-1007 Deitel 8th Edition pp. 856-861 |
| Wed Nov 21 - Sun Nov 25 |
|
|
|
Mon Nov 26 |
C++ STL algorithms in depth (slides in ppt) (studio exercises in pdf) (code example directory) |
Prata 6th Ed. pp. 1035-1037, 1286-1322 Deitel 8th Edition pp. 861-863, 890-920 |
|
Wed Nov 28 |
C++ STL functors in depth (slides in ppt) (studio exercises in pdf) (functors code example directory) |
Prata 6th Ed. pp. 1026-1035 Deitel 8th Edition pp. 924-927 |
| Mon Dec 3 |
Semester summary and review for Final Exam (slides in ppt) |
|
| Wed Dec 5 | Open Studio Time with Teaching Assistants (optional) | |
| Fri Dec 7 |
Last day to post answers to studio exercises for participation credit, by 11:59pm Last day of Engineering School classes |
|
| Mon Dec 17 |
(on the lower level down the stairs from the main entry level) |
|
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 1-3 are to be completed individually, though on labs 4 and 5 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 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:
In addition to the required textbook, the following texts may be useful and interesting additions to your programming library:
On-line information sources (please feel free to suggest other good ones):
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 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:
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 other message board postings, and attendance and engagement in class, studio, and lab sessions also may be considered if they differ significantly.
| Labs | 50 % Lab 1: 5 % Lab 2: 7 % Lab 3: 8 % Lab 4: 12 % Lab 5: 18 % Midterm Exam |
15 % |
Final Exam |
25 % |
Participation |
10 % |
|
For this course, examples of cheating include but are not limited to:
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.