• http://www.bloodshed.net/devcpp.html (small size, easy to use but may not install correctly if MinGW is already installed)
• http://www.microsoft.com/express/vc/  (full featured, also easy to use but some workaround required for C only)

Attendance

Attendance is required. Therefore, attendance does not contribute positively to your grade. You must be marked present for at least 90% of the lecture classes in order to qualify for an A.

Grade Sought	Minimum Attendance
A	90% of the lecture classes
B	80% of the lecture classes
C	70% of the lecture classes
D	60% of the lecture classes

Grading Scale

Grade Breakdown

Programs (4)	40%
Labs	20%
Programming Tests (2)	20%
Written Tests (2)	20%

Assignments

• Assignments are due at 11:59 p.m. the day of the due date.
• Late work is not accepted.
• If your assignment is turned in on time, the maximum point value is 95%.
• Extra credit work on an assignment is worth 5 points.
• All assignments turned in a full 24 hours early (to the minute) receive an extra 5 points.
• The first student to turn in an assignment that receives no point deductions is awarded an extra 5 points. The second receives 4 points, the third 3 points, the fourth 2 points, and the fifth 1 point.
• Style of your code contributes to your grade. Here are some coding styles to follow:
  • Use either 3 or 4 spaces for each indentation. Be consistent. Pick a number and stay with it.
  • Do not use tabs to indent because the printer does not have the same tab spacing as the computer. Use the space bar to indent.
  • Every C statement must begin on a separate line.
  • (Optional) If the condition for execution, such as in a while or if statement can be written in the form "( constant == var )" it may not be written in the form "( var == constant )".
  • Any "else" must be followed by a comment giving the condition when the else is executed.
  • A comment must immediately follow every while statement, giving the conditions that are true when the while statement terminates.
  • Comments must be included when they will aid the reader in understanding the program. Do not comment the obvious. Comment what you are doing, not how.
  • Use meaningful variable names. Long names are better than unclear names.
  • Do not use the single letter 'o' or the single letter 'l' for variable names.
  • Use white space (hard returns) to set off logical ideas.

Learning Strategies

You are expected to take an active role in your learning in this course. This includes regular attendance, paying attention in class, reading the textbook, and completing all course requirements. You are encouraged to study with your classmates outside of class. Programming assignments usually require a lot more time than expected, so start early and work some every day.

Academic Integrity

University Policy on academic integrity will be followed for this course. Cheating will be taken very seriously, resulting in harsh penalties. Since the skills required in this class are also required in the next class, cheating in this class will seriously hamper your ability to pass the next class. The academic integrity policy for each class varies. 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 his program, provided the following are true:
  1. You have already completed your program.
  2. You never type or dictate code for the student. You should be helping with minor details, not solving the programming problem for him/her.

Inappropriate Collaboration

• Showing another student (who has not completed the assignment) your code.
• Copying code from another student.
• Providing other students verbally 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 (including online assignments).

Any of these constitutes cheating and will be reported to the academic integrity counsel.

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.

Help Debugging from Instructors

Obviously, you may ask for help debugging from your instructor or TA. However, debugging is a skill that can be developed only by practice. It is important to learn how to struggle through problems on your own. If you are genuinely stuck, we 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 your own resulting problems.

Policies

Code of Student Life (PDF)

UNCW practices a zero-tolerance policy for violence and harassment of any kind.  For emergencies contact UNCW CARE at 962-2273, Campus Police at 962-3184, or Wilmington Police at 911.  For University or community resources visit http://uncw.edu/wrc/crisis.htm

Academic Honor Code

Students with Disabilities

If you have a disability and need reasonable accommodation in this course, you should inform the instructor of this fact in writing within the first week of class or as soon as possible. If you have not already done so, you must register with the Office of Disability Services in Westside Hall (extension 3746) and obtain a copy of your Accommodation Letter. You should then meet with your instructor to make mutually agreeable arrangements based on the recommendations of the Accommodation Letter.

Student Affairs Disability Services - Policies and Procedures 

Instructor Late

If the instructor is late for class, students are expected to wait for 15 minutes after the class period starts before leaving.