SYLLABUS

CSc 2311 – Principles Of Computer Programming II

Fall 2007

Computer Number 80534

Time & Room:    3:00-4:15 pm   MW   GCB 323                                

Instructor:           Saurav Karmakar  

E-Mail:                 saurav@cs.gsu.edu

Webpage:            http://www.cs.gsu.edu/~cscsakx/

Phone:                 404-413-5709

Office Hours:       2:00 p.m. – 3:00 p.m. MW ( or by appointment)

Office Location:   34 Peachtree Street, 14th Floor – Room 1407.

 Disclaimer: "This course syllabus provides a general plan for the course; deviations may be necessary."

 
PREREQUISITES: Reference p.259 2002-03 GSU General Catalog: CSc 2310 or equivalent is enforced.

OBJECTIVES:

  • Continuation of fundamental principles of computer programming.
  • To enable students to know the basic syntax and semantics of C++ and be able to apply it by writing executable programs that adhere to the requirements of the program.
  • So that students will be able to take higher level classes that require programming using C++ without having much difficulties with syntax, etc.
  • To enable students to develop accurate algorithm and then code that algorithm in C++.

 

TEXTS:      (Must Have) Walter Savitch:  Problem Solving with  C++ 6th  edition. Addison Wesley

Software Package: C++ compiler (GNU C ++ compiler, details would be notified later).

CONTENTS:  Students are expected to learn and implement C++ for different problems using the multiple                                                       features of the language covered in the text book.

 Assignments & Tests:

                        There will be two class tests and the final exams for this course. Other than that there will be programming assignments given throughout the semester and pop quiz may be given for extra credit.

                         Test 1 – 20%
                         Test 2 – 20%
                         Final  – 30%--- [Probably on the Wednesday December 12th 2:45 p.m. GCB 323]
                         Assignments/Projects – 30%.

                          Adjustments may be made to assignments in class. If a student is absent, it is his/her responsibility to get such changes. NO excuses will be accepted if the requirements for an assignment is changed or adjusted in class  

PLEASE NOTE:

1. Last day to withdraw and receive a possible “W” is Monday, October 15th, 2007.

2. While in class attendance will not directly affect the grade, any handouts and assignments missed will be the sole responsibility of the student. Spot attendance checks will be performed. Also pop quiz can be given on  any scheduled class day for extra credits.

3. All tests and assignments will be done on an individual basis. Anyone found cheating and/or copying (in the opinion of the instructor) will receive an automatic F for that
assignment or exam. This goes for the person who copies as well as the person who allows their work to be copied.

4. Please refer to the handout on Programming Assignments for complete details on submission requirements. (Details decided per assignment).

5. All assignments are due within 10 minutes of the beginning of class on the due date.

  • Assignments could be programming or writing type. Writing and programming type assignments could be from the course concept or related references.
  •  All programming assignments turned in must be through e-mail consisting of the source code (all .cpp and .h files) and an executable file (.exe). The subject of the email should mention CSC2311 and assignment index. Students must also turn in a print out of the source code (all .cpp and .h files).
  • Any assignment turned in without the executable or the source file will immediately lose 50%.
  • Late assignments will be accepted, but penalized in the following manner:
  • 1 day late (each lecture day is counted as one day) will result in a lost of 10% of points assigned for the assignment.
  • 2 days late (each lecture day is counted as one day) will result in a lost of 20% of points assigned for the assignment.
  • More than two days late will result in 0 point.
  • Generally, all assignments and tests will be graded and returned within ONE-TWO week. If for some reason, I am unable to do so, students will be notified.

6. No make up test will be given. If you will be absent for a test due to sickness, your case may be considered (i.e. you may or may not be given a make up exam) based
    upon a letter from a medical doctor written on that doctor’s letter head, stating that you were unable to attend school (and hence take the exam) on the given day. Absolutely
    no make up or excuse for the final exam. If for some medical reason you cannot take the final exam, then you should consider applying for an Incomplete.

7.     If you are taking more than one class during this semester, make sure that your final exams are not "clustered". That is, you do not have exams close to each other. Notify me before test, if this is your case. Do not wait for the last moment – i.e. 2 or 3 days before the final exam.

Grading:

“It is the policy of the Department of Computer Science that each instructor of record of any 1000-, 2000-, or 3000-level computer science course compute each student’s final course score so that the student’s performance on any/all work done outside of class and submitted for a grade cannot raise the student’s final course score but can lower it.  In this context, the final course score is the numerical percent that is mapped into the letter grade for the course.”

             “The following table shows the tests and assignments and their weights. The course material on which the homework is based will also be thoroughly tested on in class, including, in the case of programming language instruction, programming syntax, documentation, and design.

:

In-class

Homework

Tests

Weights

Assignments/ Projects

Weights

Test #1

Test #2

Final

20%

20%

30%

 

 

Multiple

Assignments are Equally weighted but   Projects might be considered as two assignment weights

Total Weight = 70%

Total Weight = 30%

Each item will receive a percentage score. These scores will be used to compute a Final Course Score (FCS) and a letter grade for the course according to the following four-step procedure. 

Step 1. Compute the Weighted Average of Tests (WAT).

Step 2. Compute the Weighted Average of Tests and Assignments (WATA).

Step 3. Rule: FCS = Minimum of WAT and WATA.

Step 4. Convert the FCS to a letter grade using the following ranges:

A: 100-90, B: 89-80, C: 79-70, D: 69-60, and F: 59-0. 

Examples.

Student X        

Test scores: 75, 70, 80  Assignment scores: 88, 90, 95, 80, 85

Step 1. WAT    = (22*80 + 22*80 + 26*90)/70 = 83.71
Step 2. WATA = (22*80 + 22*80 + 26*90 + 6*80 + 6*80 + 6*80 + 6*45 + 6*60)/100 = 79.3 
Step 3. Rule: FCS = Minimum of 83.71 and 79.3 = 79.3
Step 4. 79.3 is in the range 79-70.  Student X receives a C.
            

         Student Y

Test scores: 50, 75, 80,   Assignment scores: 100, 100, 100, 100, 100

Step 1. WAT    = (22*50 + 22*78 + 26*75)/70 = 68.08 
Step 2. WATA = (22*50 + 22*70 + 26*75 + 6*100 + 6*100 + 6*100 + 6*100 + 6*100)/100 = 75
Step 3. Rule: FCS = Minimum of 68.08 and 75 = 68.08
Step 4. 68.08 is in the range 69-60.  Student Y receives a D.

        Student Z

 Test scores: 85, 93, 83  Assignment scores: 90, 86, 0, 88, 90

 Step 1. WAT    = (22*85 + 22*93 + 26*83)/60 = 86.77
 Step 2. WATA = (22*85 + 22*93 + 26*83 + 6*90 + 6*86 + 0*89 + 6*88 + 6*90)/100 = 81.98
Step 3. Rule: FCS = Minimum of 86.77 and 81.98 = 81.98
Step 4. 81.98 is in the range 89-80.  Student Z receives a B.

Interpretation of the Three Students

 Student X’s performance on tests was tepid, but hot on assignments.  Student Y’s performance on tests was hot, but cold on assignments (didn’t even bother to turn in Program #3!).  Both Student X and Y earned C’s, but Student Z’s performance was just right – hot on both tests and assignments!  Student Z emphasized both tests and assignments, the test scores confirmed the assignment scores, and both were high.  Student Z earned a B.  Follow Student Z’s approach.”