Contents

1. Course Description
2. Prerequisites
3. Times and Locations
4. Assistants
5. Newsgroup  (Click here to go directly to the newsgroup.)
6. Presentations and Discussions
7. Projects
8. Coding Standards
9. Textbooks and Other Resources
10. Grading
11. Cheating

Course Description

Prerequisites

• CSE 332S or graduate standing
• proficiency in Java and C++ software development
• Working knowledge of the UNIX and/or Windows programming environment and tools

Times and Locations

Assistants

• Yuling Liang, yl9@cec.wustl.edu
• Christopher Swope, crs2@cec.wustl.edu

The instructor and TAs will read and respond to postings on the course newsgroup (news://newsreader.wustl.edu/wu.cse.class.432).

Please see the CSE Graders page for more information.

Newsgroup

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

Please note that the newsgroup is a vital part of your CSE 432 experience. Participation in the newsgroup (i.e., quantity and quality of your posts) will count significantly toward your participation grade.

Presentations and Discussions

In addition to class meeting dates and themes, page numbers for reading assignments from the required textbooks (Design Patterns a.k.a. "GoF", and Pattern Hatching a.k.a. "PH") are shown for each meeting. Details about the textbooks are listed in the Textbooks section, below.

Projects

Project documents and code are to be submitted electronically to the course e-mail account cse432@cec.wustl.edu, and will be graded and returned to you electronically as well. The milestone for each week appears in the course Presentations and Discussions section, and will be due at 11:59pm on that Thursday (after you have given your presentation and received feedback on it, on that Monday or Wednesday). Since the midterm and final evaluation and report sessions will each span two weeks, the milestones for those stages will be due on the second of the two Thursdays.

Project milestones submitted on time will be graded and returned by the following Monday. Project milestones submitted within 24 hours after the posted deadline will be accepted with a 15% penalty up front, and project milestones submitted between 24 and 48 hours after the posted deadline will be accepted with a 30% penalty up front. Project milestones submitted after that will not be graded, except in the case of documented extenuating circumstances.

You may freely discuss your projects with members of your team at any time. You may discuss your projects with other students during class times and on the newsgroup. Midterm and final exams will be completed individually and you may not discuss them with anyone else, except for your professor.

You are encouraged to post and ask for help on particular problems you may encounter during your projects, though each team must design and implement its own own solution, and prepare its own report. If during your project you determine it would be useful to incorporate code or documentation from a source outside your team, you will need to first obtain the professor's permission to use it, and you must then make sure to attribute the source appropriately.

Coding Standards

If you'd like to look at a more complete set of coding standards used in a major collaborative (university, government, and industry) development setting, the ACE Software Development Guidelines document, from which a number of the guidelines for this course were drawn, and which the ACE developers use in daily practice, is a good place to start.

Textbooks and Other Resources

• [PH] John Vlissides, Pattern Hatching: Design Patterns Applied, ISBN 0-201-43293-5, Addison-Wesley, 1998.
• [GoF] Gamma, Helm, Johnson, and Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software, ISBN 0-201-63361-2, Addison-Wesley, 1995.

We'll use the required textbooks both as references and for reading assignments. The class meeting schedule contains references to reading assignments in the required texts. Please read them before the class meeting, and use the text as a reference in designing and developing your projects.

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

• Alexandrescu, Andrei, Modern C++ Design: Generic Programming and Design Patterns Applied, Addison-Wesley, 2001.
• Austern, Matthew H., Generic Programming and the STL, Addison-Wesley, 1998.
• Beck, Kent, Extreme Programming Explained: Embrace Change, Addison-Wesley, 1999.
• Booch, Object-Oriented Analysis and Design, 2nd Ed., 1994.
• Budd, Data Structures in C++ Using the STL, 1998.
• Bulka and Mayhew, Efficient C++: Performance Programming Techniques, Addison-Wesley, 1999.
• Buschmann, Meunier, Rohnert, Sommerlad, and Stal, Pattern-Oriented Software Architecture: a System of Patterns, Wiley, 1998.
• Cline and Lomow, C++ FAQ, 1994.
• Coplien and Schmidt, eds., Pattern Languages of Program Design, Addison-Wesley, 1995.
• Coplien, Advanced C++: Programming Styles and Idioms, 1992.
• Edwards, Core Jini, 2nd ed., Sun Microsystems, 2001.
• Gilly, UNIX in a Nutshell, O'Reilly & Associates, 1992.
• Harrison, Foote, and Rohnert, eds., Pattern Languages of Program Design 4, Addison-Wesley, 1999.
• Horstmann and Cornell, Core Java (Volumes I and II), Sun Microsystems, 1999.
• Horstmann, Big Java, Wiley, 2006.
• Kernighan and Pike, The UNIX (R) Programming Environment, Prentice-Hall, 1984.
• Kernighan and Ritchie, C Programming Language, 2nd Ed., 1988.
• Lippman, Lajoie, and Moo,C++ Primer, Fourth Edition, Addison-Wesley, 2005.
• Manolescu, Voelter, and Noble, eds., Pattern Languages of Program Design 5, Addison-Wesley, to be published in 2006.
• Martin, Riehle, and Buschmann, eds., Pattern Languages of Program Design 3, Addison-Wesley, 1998.
• Metseker, Design Patterns in C#, Addison-Wesley, 2004.
• Metseker, Design Patterns Java Workbook, Addison-Wesley, 2002.
• Meyer, Object-Oriented Software Construction, 2nd Ed., 1997.
• Meyers, Effective C++, 1992.
• Meyers, More Effective C++, 1995.
• Moore, Crossing the Chasm, Collins, 2002.
• Pirsig, Zen and the Art of Motorcycle Maintenance, Morrow, 1974.
• Prata, C++ Primer Plus, Fifth Edition, 2005.
• Pree, Design Patterns for Object-Oriented Software Development, Addison-Wesley, 1995.
• Raymond, The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary, O'Reilly, 1999.
• Schmidt, Stal, Rohnert, and Buschmann, Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects, Wiley, 2000.
• Stevens, Advanced Programming in the UNIX Environment.
• Stroustrup, The C++ Language, 3rd. Ed., 1997.
• Vlissides, Coplein, and Kerth, eds., Pattern Languages of Program Design 2, Addison-Wesley, 1996.

Grading

The take-home 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 readings and projects during the semester, and to ask lots of questions in class and on the newsgroup throughout the semester.

Cheating

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

• providing or receiving answers or other assistance on an exam, or
• incorporating other peoples work within your projects without permission or without attribution.

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 the professor or TAs detect it. If in doubt, please ask.