CSE E81 532S: Advanced Multi-Paradigm Software Development

Professor:	Chris Gill cdgill@cse.wustl.edu	(314) 935-7538
	Office hours: Jolley 514 (by appointment)
Teaching Assistant:	Justin Wilson wilsonj@cse.wustl.edu	(314) 935-7535
	Office hours: Jolley 515 (by appointment)

Contents

1. Times and Locations
2. Course Description
3. Prerequisites
4. Forum   (Click here to go directly to the CSE532 Messageboard.)
5. Discussions/Lectures
6. Labs
7. Coding Standards
8. Textbooks and Other Resources
9. Grading
10. Cheating

Times and Locations

Course Description

Prerequisites

• CSE 332S (Object-Oriented Software Development Laboratory) or graduate standing and proficiency with C++
• CSE 422S (Operating Systems) or CSE 522S (Advanced Operating Systems)
• Working knowledge of the UNIX programming shell and tools, e-mail, web, etc.

Forum

Please submit ALL questions and concerns of a public nature to the CSE532 Messageboard, which can be found on the web at http://classes.engineering.wustl.edu/cse532/bb/. To use the CSE 532 Messageboard, you should first click on the Register link found on that page, and follow the instructions you are given. You are encouraged answer each other's questions there!

Do not e-mail technical questions to the professor or teaching assistant: instead, please post for all to see, consider, and respond.

Studios

Reading materials will be suggested for many of the topics. It is to your advantage to go over the readings prior to class time, and to ask questions about anything that may be unclear. Supplemental resources including web materials and additional books that may be helpful will also be suggested.

Labs

• Lab 0
  
• Lab 1
  
• Lab 2
  
• Lab 3
  

There will be 4 lab projects this semester. Labs should be turned in via e-mail to the cse532@seas.wustl.edu account, and will be graded and returned to you electronically as well. Each lab assigment will contain the procedure for turning in the lab. Labs will increase in length, value, and difficulty throughout the semester. The exact due date will be specified in each lab description.

Each lab will require a ``lab report''. Report format and length and content requirements will be described in each lab assignment. The actual report will be submitted via e-mail, as well, so it must go into a file. An e-mail turn-in process (via make) that submits your files for grading will be provided, though each assignment will have a more detailed description of other acceptable ways to e-mail your solution.

Labs will be performed in teams of 2 or 3: teams may be different for each lab assignment or may remain the same for all labs. Team members may choose one-another and post their chosen teams to the course forum according to the instructions in the lab assignments: people who do not identify a team by the designated cut-off will be assigned to teams arbitrarily.

Each team should submit its solution and lab report for each project. 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 extenuating circumstances.

You may discuss your lab projects with other students outside your team only during lecture or on the course forum. Discussion of lab projects within a team, is encouraged at any time. Each team must design and implement its own solution, and prepare its own report.

Coding Standards

If you'd like to look at some coding standards, the guidelines that the ACE developers use is a good place to start. It's reasonably concise and very relevant to C++ coding activities both when using the CSE 532 ACE builds for Linux or Windows, and in other development contexts.

Textbooks and Other Resources

We'll use the required textbooks both for class material and as references. The lecture schedule will be augmented with references to revelant portions of the required texts. Please read each assigned section before the class meeting where it will be discussed.

Optional texts:

• [APG] Huston, Johnson, and Syyid, The ACE Programmer's Guide, Addison-Wesley, 2000.
• [POSA2] Schmidt, Stal, Rohnert, and Buschmann, Pattern-Oriented Software Architecture, Volume 2: Patterns for Concurrent and Networked Objects, Addison-Wesley, 2000.

• Shubho Sadhu has contributed a useful page of instructions for how to use ACE in both Linux and Windows environments.

• The ACE Doxygen documentation can be very helpful in navigating the ACE libraries (thanks to Justin Luner for posting this link).

• If you are new to the UNIX environment, then you may want to spend a bit of time trying out different commands in a terminal window to understand what they do and how they can help you navigate and perform other tasks. The Basic Linux Commands page provided by Google Code University, and Joshua Glatt's Guide to the Linux Command Line Interface for Students, are but a couple of the many sources of information available for this.

• If you are looking for a basic editor in which to write, modify, and save program files, the GNU nano editor is a good basic one to use, as is the gedit editor for the GNOME desktop.

• If you are looking for a more full-featured editor within which you can run a compiler like g++ and a debugger like gdb, it may be worth the investment of additional effort to learn and use emacs.

• If you are looking for a nice graphical integrated development environment (IDE) to use, Eclipse is installed on the Lopata 400 lab machines, and working through the CSE 532 Eclipse Tutorial can help you get started using it in the lab/studio environment for this course.

• If you're looking to brush up on your C++ background or to assess your proficiency, the CSE 332 course web site is a good place to start. If you are not already at least reasonably familiar with the topics mentioned there, then CSE 532 is probably better taken after you are.

If you're looking to build your library (in order of relevance):

• Matthew H. Austern, Generic Programming and the STL, Addison-Wesley.
• Gamma, Helm, Johnson, and Vlissides, Design Patterns, Addison-Wesley.
  (Often referred to as the "Gang of Four" book)
• Lippman and Lajoie, C++ Primer , 4th Ed., Addison-Wesley.
• Stroustrup, The C++ Language, 3rd. Ed.
• Czarnecki and Eisenecker, Generative Programming, Addison-Wesley.
• Alexandrescu, Advanced C++, Addison-Wesley.
• Coplien, Advanced C++: Programming Styles and Idioms, 1992.
• Beck, Kent, Extreme Programming Explained: Embrace Change, Addison-Wesley, 1999.
• Kernighan and Ritchie, C Programming Language, 2nd Ed., 1988.
• Meyers, Effective C++.
• Meyers, More Effective C++.
• Stevens, Advanced Programming in the UNIX Environment.
• Stevens, UNIX Network Programming (vols. 1 and 2).

Grading