CSC 331 - FIRST DAY ANNOUNCEMENTS (REVISED 10/8)

FALL 2018

As you know, all UNCW classes were canceled on 9/10/18 starting at 12:00 pm and resumed on 10/8/18.  This resulted in a loss of 600 minutes of instructional minutes for this course.  UNC System Policy 400.1.6 requires 750 instructional minutes (or the equivalent) for each credit-hour of a course.  For example, a 3-credit hour course requires 2250 minutes of instructional time.  To make up for such a large and unprecedented amount of lost time, UNCW Academic Affairs developed a diverse and flexible plan.  This plan contains adjustments to the academic calendar, changes to the daily schedule, and the opportunity to make-up time through outside of class and/or online assignments.  In some cases faculty and students can also decide to hold make-up courses if necessary. This revised syllabus, and the revised course schedule, reflects how this plan impacts our course.

Course Description (as it appears in the UNCW catalog): 

CSC 331 - Object-Oriented Programming and Design

Credits: 3
Prerequisite: CSC 231. Object-oriented programming with a focus on software modeling of objects, classes, methods, inheritance, interfaces, and polymorphism. Completion of a team software project is required. A grade of ‘C’ (2.00) or better is required for taking courses for which CSC 331 is a prerequisite.
Note: A grade of "C" (2.0) or better is required for taking courses for which CSC 331 is a prerequisite. This means that a grade of C- (or below) in this class does not meet the requirement.
  1. Text: The Object-Oriented Thought Process by Matt Weisfeld, Fourth Edition, ISBN-10: 0-321-86127-2, ISBN-13: 978-0-321-86127-6, Publisher: Pearson Copyright: 2017. A Java language reference is optional, but highly recommended.
  2. Class Web site: http://people.uncw.edu/narayans/courses/csc331/csc331.html
  3. Class time: 

    4. Attendance: You are required to attend, and expected to actively participate in every class meeting. Active participation implies coming to class well prepared with your textbook, notes, and pens and pencils and being engaged in classroom activities. You are expected to read the textbook before and after topics are presented in class.

  4. Instructor: 
  1. Academic Integrity
    University Policy on academic integrity will be followed for this course. Cheating will be taken very seriously, resulting in severe penalties.  Please follow the policies below:
     

    Appropriate Collaboration

    • Sharing class notes with another student.
    • Discussing anything that was covered in class.
    • Helping a fellow student locate a bug in their program, provided the following are true:
      1. You never type or dictate code for the student. You may help the student resolve a particular issue. You may not solve large parts of the programming problem for him/her.

    Inappropriate Collaboration

    • Showing another student (who has not completed the assignment) your code.
    • Copying code from another student.
    • Verbally providing other students with the solution to the program. (This would be along the lines of giving them the key to solving the problem when they need to think it through themselves.)
    • Helping other students during a test or quiz.
    • Doing another student's work.
    Any of these constitutes cheating and will be reported to the academic integrity council.

    Honor Code

    It is the responsibility of every student to uphold and maintain the UNCW Academic Honor Code (see Section V of your Student Handbook). You violate the honor code when you represent someone else's work as your own. Programming assignments may be discussed at a conceptual level with other students but details and coding must be your own. Copying and team collaboration is prohibited.

  2. Help Debugging from Instructor 
    Obviously, you may ask for debugging help from your instructor. However, debugging is a skill that can be developed only by practice. It is vital for you to learn how to successfully struggle through problems on your own. If you are genuinely stuck, I will be willing to help you as far as your code matches the techniques described in class. If you write your program with an approach that is a complete departure from the way described in class, you are responsible for fixing any resulting problems.
     
  3. Programming Assignments: 
  1. Tests and Grading: You will have 2 in-class tests with written and programming components on the following dates:

    In general, no make up tests will be given; if you miss a test and have a PREARRANGED reason, your final exam grade may be substituted for it. If you miss a test without a PREARRANGED reason, you will receive a grade of F in the course.

    Note: These are post-Florence revised dates. Friday, December 7 is the last class meeting. You will have a FINAL EXAM on Monday, December 10 from 11:30 am - 2:30 pm, room TBA. If you are passing the course, and if you cannot take the final exam when it is scheduled because of an emergency beyond your control, and if you notify me BEFORE the end of classes, you may possibly receive an ``I'' in the course. Details about the format of the final will be announced later in the semester.

    The upper 30% (except the A range), and lower 30% of all grade ranges will be assigned + and - modifiers, respectively. For instance, an overall score of 93 in the course will result in a grade of A-, or better. The instructor reserves the right to RELAX this grading scheme.

  2. Students with Disabilities:  If you are a person with a disability and anticipate needing accommodations of any type in order to participate in this class, you must notify the Disability Resource Center (#1033 DePaolo Hall, 910-962-7555), provide necessary documentation of the disability and arrange for the appropriate authorized accommodations. Once these accommodations are approved, please identify yourself to me so we can implement these accommodations.