Date: Mon, 11 Nov 1996 17:15:24 GMT Server: NCSA/1.5 Content-type: text/html Last-modified: Fri, 06 Sep 1996 04:25:02 GMT Content-length: 10803 General Course Information - CS 302 - Section 4

CS 302 Fall 1996 - Section 4

Algebraic Language Programming in C++

Instructor: Milo M. Martin (milo@cs.wisc.edu)



General Course Information



Objectives

The main objectives of this class are that students develop problem solving and C++ programming skills. These programming skills are practical for the non-major student and for the computer science major serves as a solid foundation upon which further classes will be built. Thus, this classes is a general introduction to computer programming, and the first step toward a computer science major.

Expectations

Learning is an active process. To get the most out of this course, I expect you to:

Textbook

Problem Solving with C++ - The Object of Programming by Walter Savitch
Addison-Wesley Publishing Company, 1996.

Contacting Me

The best way to contact me is to visit my office during office hours or any other time by appointment. In addition to my instructing duties, I also must attend to my own class work and research. For this reason, I will not always be available when requested. In general it should be no problem to setup an appointment with me to discuss whatever class concerns or questions you might have. I would also like to encourage you raise your questions in class. Odds are if you have a question, someone else also needed clarification In addition questions from the class can often generate further class discussion or lead into the topic of the day.

The next best way to contact me is through e-mail. I will do my best to answer your questions or other concerns promptly. However, to avoid being swamped by e-mail, I will follow this e-mail reply policy:

Grading Percentages

Your grade is determined by programming assignments, quizzes, and three exams. The exact number of programming assignments and quizzes has not yet been determined. Individual assignments and exams will not be assigned letter grades. Letter grades are assigned only at the end of the semester.

Summary:
        3 Exams (20% each)      60%
        Quizzes                 10%
        Programs                30%
        ----------------------------
        Total                  100%

Grading Standards

Grading of programming assignments is based upon three criteria: correctness, technique, and readability.

Correctness is by far the most important criterion. A program which does not correctly fulfill the requirements of the assignment is subject to a grade reduction of as much as 50% or more.

The technique used in a program is the means in which that particular problem was solved. A solution which is correct but clumsy or awkward is subject to a grade reduction of as much as 25%. Sometimes there will be very little leeway in this area; other times there might be several correct solutions.

The readability of a program refers to the ease with which a human reader (such as the grader) can read and understand the source code. Readability does not affect the execution of the program; however, poor readability can result in programming errors which make the program incorrect. Poor readability can result in a grade reduction of as much as 25%. The readability of a program includes:

Late Policy

Honor

Students are encouraged to discuss course issues, including those issues raised by class discussions and assignments. However, the solutions to programming assignments should be individual original work. The phrase used to concisely summarize the policy is: "Do not share code in any form: oral, written, or computerized."

If you have any questions about this policy, or question if a specific action is allowed, please don't hesitate to come and talk to me about these issues. In addition please read the document linked from my main CS302 page, "Academic Misconduct Policy".

Computer Logistics

Other Educational Concerns


This document was constructed using similar documents from various current and past CS302 instructors as reference.
Milo M. Martin (milo@cs.wisc.edu)