COMP 2673 Spring 2002 Course Information and Syllabus Course Calendar Assignments and Solutions

About This Course

In this course we will learn to use the UNIX operating system while we continue our study of C++. We will cover inheritance, templates, exception handling, and using the STL (standard template library). You will also continue to improve your design, programming, and debugging skills. You will continue to increase your level of sophistication in your communication skills, including documenting your programs, listening to and speaking about technical material, and reading texts to learn information independently.

Course Meeting Times

The lecture is held in JGH 316 at 1:00 (Section 1) or 2:00 (Section 3) on Mondays, Wednesdays and Fridays. The lab meets on Tuesdays at 1:00 (Section 1) or 2:00 (Section 3) in the Sun Lab in room 216 of John Greene Hall.

Required and Optional Resources

• Programming textbook: C++ How to Program, 3rd Edition, by Deitel and Deitel
• Unix textbook: Sams Teach Yourself Unix in 24 Hours, 3rd Edition, by Dave Taylor
• Webpage for Deitel and Deitel: http://cwx.prenhall.com/bookbind/pubbooks/deitelcpp/
• You may use the Sun Lab during any of the extensive hours that the building is open and the Sun Lab is available. For information on the Sun Lab schedule, please see http://www.cs.du.edu/support and click on the "About the Sun Lab" link near the bottom of the page. The other links on this page also give good introductory information.
• You may log into the computers in the sun lab remotely from your laptop or home computer, provided you have a modem or DSL line. The recommended way to do this is to download a program called SSH (for "secure shell"). Information on downloading this program is available at //http:www.du.edu/uts/helpdesk/ssh/. Since these computers are multi-user machines, you must stay aware that any misuse of these systems may impact other users. Please carefully read and follow the Sun Lab rules

Grading

You will be evaluated based on your homework, programming projects, quizzes, final exam, and on your performance in the lab, weighted approximately as follows:

• 20% - Homework
• 10% - Quizzes
• 15% - Final Exam
• 45% - Programming projects
• 10% - Lab

Collaboration and Academic Honesty

When you turn in work in this course, you are implicitly agreeing that you have followed the rules for collaboration set forth for that assignment. Copying another person's work on programming assignments, written assignments, exams, quizzes, etc. constitutes plagiarism, a violation of the University of Denver Honor Code. This code forbids plagiarism, cheating, fabrication, and aid of academic dishonesty. Violations of this code in this class will be treated with the utmost of severity, the minimum penalty being a grade of F and a letter describing the incident sent to the dean. For more egregious offenses, the case will be referred to the Academic Conduct Review Board.

Guidelines for homework

In this course, you may collaborate, and in fact are encouraged to collaborate, with others in the class on homework. This includes, for example, discussion of overall strategies or resolution of details. It's good practice to acknowledge your co-worker's contributions (both general and specific) to your final product. When you write up the solutions to the assignments, however, your work must be completely your own. You may not write up homework assignments together, copy other's written work or share your own written work. Homework assignments are due at the beginning of the class period on the due date. Your papers should be organized and neatly written, and should be typed if your handwriting is difficult to read. When you turn in a homework assignment, you are implicitly ackowledging it as your work (see Collaboration and Academic Honesty).

Guidelines for Programming Assignments

Programming assignments are due at the beginning of the class period on the due date. On the programming projects, you may choose to work alone, or you may choose to do the projects in groups of two. In the latter case, you are responsible for dividing the work in an equitable fashion, and each participant is responsible for understanding every part of your final program. Both participants will receive the same grade for the project. Turn in a hard copy of the header files and source code files - your name should be in a comment at the beginning of each file. In addition, you will mail an electronic copy of your work to an address that will be announced. No lines of code in your programming assignment should be copied from another student (see Collaboration and Academic Honesty).

Your program must work correctly to receive credit. A program which does not compile will receive little credit. A program which works partially will receive partial credit. Your score improves if you attach notes documenting the incompleteness or bugs (include details of the circumstances under which they occur), since this shows the degree to which you tested your code.

Comment your code well - write comments that would be useful to someone who would have to maintain or enhance your code. The quality of your comments is included in your grade.

Late Homework

Course Calendar and Assignments

The calendar below contains links to homework assignments, links to programming assignments, as well as important dates for you to keep in mind. Entries in the calendar dated after today's date are subject to change.