CSE E81 532S: Advanced Multi-Paradigm Software Development

Contents

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

Times and Locations

Course Description

Prerequisites

• CSE 332S (Object-Oriented Software Development Laboratory), or graduate standing and proficiency with C++
• CSE 422S (Operating Systems Organization)

Discussions/Studios

Reading materials will be assigned 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

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.

Labs will be performed in teams of 1, 2 or 3 people (but not more than 3): teams may be different for each lab assignment or may remain the same for all labs. 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 the case of extenuating circumstances approved by the professor.

You may discuss your lab projects with other students outside your team only during course meeting times. 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.

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

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

Textbooks and Other Resources

We'll use the required textbook both for class material and as a reference. Revelant portions of the required text will be assigned throughout the semester: please read each assigned section before the course meeting where it will be discussed.

Optional texts:

• [Stroustrup] Bjarne Stroustrup, The C++ Programming Language: Fourth Edition, Addison-Wesley, 2013.
• [LLM] Stanley B. Lippman, Josee Lajoie, and Barbara E. Moo, C++ Primer: Fifth Edition, Addison-Wesley, 2013.
• [C++NPv1] Douglas C. Schmidt and Stephen D. Huston, C++ Network Programming Volume 1 Mastering Complexity with ACE and Patterns, Addison-Wesley, 2002.
• [C++NPv2] Douglas C. Schmidt and Stephen D. Huston, C++ Network Programming Volume 2 Systematic Reuse with ACE and Frameworks, Addison-Wesley, 2003.
• [APG] Stephen D. Huston, James CE Johnson, and Umar Syyid, The ACE Programmer's Guide, Addison-Wesley, 2004.

• If you're looking to brush up on your C++ background or to assess your proficiency, the Spring 2015 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.

• 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

The in-semester exams will be roughly proportioned to cover the material in both of the tracks in the course. The best way to study for the exams is to keep up with the readings, studio exercises, and labs during the semester. The first exam will cover the material up to that point in the course, and the second exam will cover the material after the first exam.

The last grading component is an evaluation of your participation in the class, and an evaluation of your application of the tools and techniques discussed in class and used in the studios 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/lectures, studios, labs, etc.

Completing and submitting the assigned studio exercises by the specified deadlines will constitute a significant baseline for the participation grade.

Academic Integrity

Each studio and lab assigned in this course is expected to be completed collaboratively by up to three people (and not more than that). Student teams may change from assignment to assignment, but the sharing of code between teams without prior permission of the instructor is strictly prohibited, and you must acknowledge and document in detail all contributions that anyone has made to the work.

Exams must be completed individually without assistance from any other person and without reference to materials or devices, except as specifically allowed by the instructor (documentation of what is allowed will be described in class, provided in the corresponding exam review slides, and written on the font page of the exam).

Cheating costs everyone something. Someone who cheats misses out on the intended opportunity to improve through the assigned work, and like anyone helping them cheat is at risk of diminished reputation as well as specific sanctions. Cheating also degrades the value of the degree earned by those who complete their work with integrity. If you have any doubt about whether something is allowed under the academic integrity policy for this course, please ask your instructor first.