Instructors:

Name:	James J. Maybury	Nelson Padua-Perez
Sections:	040X	010X, 020X, and 030X
E-mail:	jmaybury@umd5.umd.edu	nelsonp@wam.umd.edu
Office:	1119 A.V. Williams 301.405.2672	1129 A.V. Williams 301.405.4539
Office Hours:	Click Here	Click Here

Description:

The topics covered by this course are the following: file I/O, dynamic memory allocation, object-based programming, recursion, searching algorithms, sorting algorithms, and data abstraction. You will learn the essentials of the C++ Programming language required to study the above topics.

Pre/Co requisites:

CMSC 106 (Introduction to C Programming), Corequisite: MATH 141

Text Book(s):

"C++: How to Program", Deitel & Deitel, Third Edition, Prentice Hall

Posting Accounts:

Course materials (e.g., projects, assignments, office hours, etc.) will be made available in the public course posting accounts. Directions for obtaining course materials from the posting accounts will be discussed in class.

Office Hours:

The Instructors' and TAs' office hours will be provided in lecture and available in the class posting accounts.

E-mails:

The Instructors' emails are supplied so you can contact us when necessary in emergency situations, but we regret that we have insufficient resources to debug students' projects via email. If you have any problems with your projects then stop by during the instructors' office hours or the TAs' office hours. Office hours or personal communication during or after class (if time permits), are the preferred means for asking us questions about the course material.

Course Requirements:

Quizzes (approx 6) Programming Projects (7) Midterm Exams (2) Final Exam (comprehensive)

10% 35% 40% 30% (15% each) 25% (12.5% each) 25%

The final course grades may be curved, if necessary, based on each student's total numeric score for all coursework at the end of the semester.

You must provide a working version of your Project #6 in order to pass the course. A working version of a project is one that satisfies the primary output and the project requirements specified' in the project description. ANY STUDENT WITHOUT A WORKING VERSION OF PROJECT #6 WILL RECEIVE AN F IN THE COURSE. For example, if a student has a 100 in every project, exam, and quiz, but does not have a working version of Project #6, then the student will receive an F in the course.

Grading Policies:

All projects will be due at 8:00 am (morning!) on the date indicated on each project assignment. All projects will be graded out of 100 points. After the deadline for a project, you have two extra days to submit a working version of your project. Only the last project submission you provide will be graded; it will supercede any earlier submissions you may have made. For example, if a student has both an on-time as well as a two-day late submission then only the last (two-day late) submission will be graded. The penalties for each day late are as follows:

           1 day late -> -10 points (you can get a maximum of 90 points)
          2 days late -> -20 points (you can get a maximum of 80 points)

If after the second day late you have not provided a working version of your project (except for Project #6) then you will receive 0 points for the project. Project #6 is the only exception to this rule. We will accept Project #6 submissions after the second day late, and until Dec 11 at 8:00 am. Versions of Project #6 submitted after the second day late and before (or on) Dec 11 at 8:00 am will receive a maximum of 10 points.

Under no circumstances will any emailed project, or a project submitted by any means other than that specified on the assignment be considered.

Any request for reconsideration of the grading on any exam, or quiz must be submitted to your teaching TA in the next lab session following the one where you received the graded material. Regrade requests must be typed on a separate sheet of paper and attached to the material to be regraded. WE WANT TO WARN YOU THAT WE COPY ALL GRADED EXAMS AND QUIZZES BEFORE HANDING THEM BACK TO YOU. IF YOU MODIFY ANY GRADED EXAM OR QUIZ IN ANY WAY YOU WILL BE FACING AN ACADEMIC INTEGRITY SITUATION (more about Academic Integrity can be found at the end of the syllabus).

Project regrades must be submitted to the TA who graded your project. You have one week (except for Project #7 for which you will have 1 day) to submit a written regrade request for a project.

Missed Assignments:

There will be no make-ups for missed hourly exams or quizzes. In the case of a documented medical excuse or documented family or personal emergency the grade for a missed exam/quiz will be calculated by averaging the student's scores for other exams and/or quizzes. Please note that "Verification of Visit" forms from the University Health Center do not constitute a valid excuse. An authorization form to release medical information must be signed for any Health Center documentation to be considered valid (this form is provided by the Health Center.) If it is known in advance that a student will miss an assignment, the student must notify the instructor prior to the due date of the assignment.

Important Dates:

Exams will be held on the dates below unless a change is necessary to accommodate lecture topics. In that case the revised date will be announced in lecture. The final exam date, however, is fixed. IF YOU HAVE A SITUATION THAT PREVENTS YOU FROM TAKING THE FINAL EXAM AT THE SCHEDULED DATE IS YOUR OBLIGATION TO INFORM YOUR INSTRUCTOR DURING THE FIRST TWO WEEKS OF CLASS, IN ORDER TO MAKE THE APPROPRIATE ARRANGEMENTS.

Exam 1: Monday, October 7

Exam 2: Monday, November 4

Final Exam: Tuesday, Dec 17, from 4 to 6 pm.

Submission of Project #6 working version: Wednesday Dec 11 at 8:00 am.

Learning Assistance Service:

If you are experiencing difficulties in keeping up with the academic demands of this course, contact the Learning Assistance Service, 2201 Shoemaker Building, 301-314-7693. Their educational counselors can help with time management, reading, note-taking and exam preparation skills.

Accommodations for Students with Disabilities:

Students with disabilities must inform the instructor of their needs at the beginning of the semester.

Academic Integrity Statement (MAKE SURE YOU READ THIS):

Many students in this course believe that because the size of the class is so large, we will not check that each project has been implemented individually. We want to inform you that we do check. We have software tools that allow us to compare every student project against every project across all the sections of the course. Some students believe that by changing variable names, adding/removing comments, etc., they can transform one program into a different one; this is not true. Even with those modifications we are able to recognize one project as a modified version of another project and we will report this as an academic integrity situation. Our advice to you is to do all your projects by yourself.

Every semester we have taught we have caught students cheating on project assignments. Student's academic careers have been ruined by their decision to cheat.

Please carefully read and consider the Computer Science Department policy regarding the use of computer systems, and the Academic Instructional Technology Services' policy regarding acceptable use of computer accounts provided for instructional use, in the Fall 2002 issue of the departmental newsletter, CS Tid-Bits. Note in particular the penalties for impermissible cooperation on programming projects, which is a violation of the University's Code of Academic Integrity. Any evidence of unacceptable use of computer accounts or unauthorized cooperation on exams or projects will be submitted to the appropriate authorities or to the Student Honor Council, which could result in an XF for the course, suspension, or expulsion from the University.

NOTE SPECIFICALLY that projects are to be done INDIVIDUALLY. For academic honesty purposes, projects are to be considered comparable to an extended take-home exam. That is, any cooperation or exchange of ideas which would be prohibited on an exam is also prohibited on a project assignment. Working IN ANY WAY with another student will be considered a violation and WILL BE REPORTED to the Honor Council. Students may not discuss pseudocode, design of a program or of individual functions, coding of individual functions, or any high--level code with anyone except the instructors and teaching assistants. Should you have difficulty with a programming assignment you should see your instructor or the teaching assistants in office hours, NOT solicit help from anyone else in violation of these rules. Students are welcome to study together or to receive help in learning the course concepts from any others, but quizzes, exams and projects are to be solely and entirely each student's own work.

VIOLATIONS OF ACADEMIC HONESTY INCLUDE:

• failing to do all or any of the work on a project by yourself, other than assistance from the instructional staff.
• using any ideas or any part of another student's project, or copying any other individual's work in any way.
• giving any parts or ideas from your project, including test data, to another student.
• having programs on an open account or on a PC that other students can access.
• transferring any part of a project to or from another student or individual by any means, electronic or otherwise.

IT IS THE RESPONSIBILITY, UNDER THE UNIVERSITY'S HONOR POLICY, OF ANY STUDENT WHO LEARNS OF AN INCIDENT OF ACADEMIC DISHONESTY TO REPORT IT TO THEIR INSTRUCTOR.

Course Topics (subject to change):

This list may vary according to the pace of lecture topics.

	Topics
Week 1 9/2	Introduction, Control Structures,   Functions, Arrays, Structures
Week 2 9/9	Stream I/O, Pointers, Classic Strings, BNF   Project #1 Assigned
Week 3 9/16	Stream I/O (continued), BNF, Files   Quiz #1 Project #1 Due, Project #2 Assigned
Week 4 9/23	Software Design, Dynamic Memory Allocation
Week 5 9/30	Dyn Mem Allocation, Makefiles, Separate Compilation   Quiz #2, Project #2 Due, Project #3 Assigned
Week 6 10/7	String Class (C++ Library), Classes (Constructors / Destructors)   EXAM I
Week 7 10/14	Classes (Copy Constructors, Assignment), More about "const" Separate Compilation   Project #3 Due, Project #4 Assigned
Week 8 10/21	Recursion, Objects within Objects   Quiz #3
Week 9 10/28	More about Objects and Classes, Linked Lists   Quiz #4, Project #4 Due, Project #5 Assigned
Week 10 11/4	Linked Lists   EXAM II
Week 11 11/11	Searching and Sorting   Project #5 Due, Project #6 Assigned
Week 12 11/18	Operator Overloading, Abs/Con Comments   Quiz #5
Week 13 11/25	Operator Overloading, Abs/Con Comments (Continued)   Quiz #6, Project #6 Due, Project #7 Assigned
Week 14 12/2	Proxy Classes, Exception Handling, Other Topics   Project #7 Due
Week 15 12/9	Overloading new, Singleton class, Other Topics   Last Day to Submit working version Project #6

See above for policies concerning email Last Modified: Mon Oct 21 17:11:29 EDT 2002

Web Accessibility