IC210 - Introduction to Computing

Fall 2009

Course Policy


-          Asst Prof Adina Crainiceanu     MI-362, x3-6822,                   adina@usna.edu

-          Visiting Prof Eric Harder,            MI-352,  x3-6807,                  harder@usna.edu

-          LT Keith Labbe,                           MI-323,  x3-6816,                  labbe@usna.edu

-          Asst Prof Luke McDowell,         MI-353, x3-6811,                  lmcdowel@usna.edu (Course Coordinator)

-          Maj (sel) Kasey Miller,                MI-358, x3-6835,                   kmiller@usna.edu

Course Web Page: http://www.usna.edu/Users/cs/lmcdowel/courses/ic210/F09/ will be used to post course reading assignments, supplemental notes, labs, project assignments and other items of interest as they become available.  You are responsible for information posted on this page. Expect material for every lecture!

Required Text: Absolute C++, 4th Edition, Savitch, Addison Wesley, 2010 (3rd edition also okay)

This course contributes to the following ABET program outcomes that you should be able to do upon graduation: 

·          (b) An ability to analyze a problem, and identify and define the computing requirements appropriate to its solution

·          (e) An understanding of professional, ethical, legal, security, and social issues and responsibilities

·          (g) An ability to analyze the local and global impact of computing on individuals, organizations and society.

 Learning Objectives:

1.        Solve problems using the procedural programming paradigm.

2.        Design, develop source code for, debug, and document programs using structured programming techniques in order to solve problems (supports Program Outcome (b)).

3.        Determine an appropriate data structure (such as linked lists, arrays) in order to solve problems.

4.        Understand the impact of the legal, social, and ethical issues on individuals, organizations and society concerning copyrighted information found on the Internet (supports Program Outcomes (e) and (g)).

Honor:  You are required to abide by the USNA and department honor policies at all times, including, but not limited to: The Honor Concept of the Brigade of Midshipmen, the Policies Concerning Graded Academic Work, and the departmental Policy Concerning Programming Projects, found at http://www.usna.edu/CS/academics/honor.htm.  You will have to take and achieve a 100% on a Blackboard quiz covering the material in this policy and the departmental Policy Concerning Programming Projects referenced below. You may take the quiz as often as you need to, but you will receive an F at each marking period until you pass it with 100%.

All assignments are considered “routine” unless your instructor specifically indicates that it is a “project.”  All quizzes and exams must be entirely your own work.  The following summarizes these policies as they apply to this course.  Consult your instructor if you need further clarification.

·         Exams & Quizzes: All written exams and quizzes will be closed book. Practicum exams will be given during a lab period.  You may only use your paper-based notes, the official class notes from the web, or your textbook for the practicum. On all exams, quizzes, and practicums you may not receive help from anyone.

·         Projects: All projects MUST be submitted in order to possibly pass this class. You must do your own work in designing, implementing, and testing your projects without assistance from anyone except for your instructor. The Department Policy Concerning Programming Projects provides detailed guidance. 

·         Labs & Homework: Collaborative conversations with regard to syntax and strategies for accomplishing labs and “routine” out of class programming assignments (homework) other than projects are allowed, however design and implementation must be the work of the individual student handing in the final product. Thus, the actual pencil-to-paper or fingers-to-keyboard work must be your own. Copying a file or parts of a file from anyone is prohibited. Midshipmen must clearly state on their assignment who they collaborated with. For labs done in pairs, partners may and should freely collaborate with each other without restriction.

Any cheating will result in, at a minimum, a zero for the assignment, quiz, or exam in question. All honor offenses will be reported to the Honor Board.

Late Policy: All work not due at the beginning of class is due by close of business (COB) on the due date. Work in your instructor’s mailbox or slid under their office door before he or she arrives in the morning will be considered submitted by COB on the previous working day.

·         Labs: Any lab not completed during the lab period must be submitted (as a screen capture of your working program and paper copy of source code) by COB the next day or will receive a 0. For labs done in pairs, the pair must work together and should turn in a single copy.

·         Homework: All homework will be due at the start of the next class period. Homework, including pre-lab homework, will receive a 0 if submitted late.

·         Projects: Project submissions will consist of two parts: electronic (the program itself), and paper (source code printout, external documentation, screen captures of program runs, etc.) as detailed in the project instructions. Both the electronic and paper parts must be submitted before the project is considered to be submitted, and the electronic & paper versions of programs must agree! Projects are due by COB on the due date. Any late project submitted n working days late (fractional days will be rounded up!) will receive an automatic late penalty of 3n+1 + 1 points. So a project due Monday, but submitted Tuesday at noon would have a penalty of 10 points. If submitted Wednesday, the penalty would be 28 points.

Personalization: All homeworks, labs, and projects must contain your name at the start of the output, e.g., “Welcome to MIDN’s Smith’s Homework #3….”

Section leader: The section leader will call the class to order and record absences and tardiness. If the instructor is absent, do not dismiss class, instead contract the department office and lead the class in productive review.

Extra Instruction:  Extra Instruction (EI) is available and encouraged when your own attempts to understand the material are unsuccessful.  You may just stop by your instructor’s office, but making an appointment in advance will ensure availability. To be most effective, you must be prepared for EI.  Have your notes with you and specific questions in mind. If you miss class, get the notes from the section leader or other classmate.

Absences:  You are responsible for obtaining any material missed due to an absence. You must ensure your work is submitted on time regardless of other commitments, i.e. duty, sick call, MO, etc. Should bona fide emergencies arise, it is your responsibility to coordinate in advance with the instructor (emergency leave, hospitalization, SIR, etc.). Some labs will be done in pairs – therefore you must communicate in advance to the instructor and your partner if you know that you will be absent or late for a lab.  Failure to comply will result in a zero for the lab.

Food/Beverages: Food is not permitted in the classroom or labs.  Beverages in closeable containers are allowed (note that soda cans are NOT closeable).

Course Grade breakdown

6 Week Grade

12 Week Grade 

Final Grade

6 Week Written /  Practicum Exams

25%  /  25%

14%  /  14%

7%  /  7%

12 Week Written  /  Practicum Exams


14%  /  14%

7%  /  7%





Other graded work (labs, homework) as set forth by your instructor




Programming Project Average




Final Written  /  Practicum Exams



14%  /  14%













Asst Prof L. McDowell.

Course Coordinator

Prof. Donald Needham

Department Chair