• (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
• (h) Recognition of the need for, and an ability to engage in, continuing professional development

1. Solve problems using the procedural programming paradigm.
2. Design, develop, debug, and document computer programs using structured programming techniques. (supports Student Outcome (b)).
3. Select and implement the most appropriate data structure for a solution and justify your selection.
4. Identify common uses of documents found on the Internet and explain why each is, or is not, a breach of copyright law. (supports Student Outcomes (e) and (g)).
5. Identify opportunities for continued growth in the field of computing. (supports Student Outcome (h)).

• Honor Concept of the Brigade of Midshipmen, USNAINST 1610.3H
• Policies Concerning Graded Academic Work, USNAINST 1531.53
• CS Department Policy Concerning Programming Projects, COMPSCIDEPTINST 1531.1C

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, your own code stored on your CS Department home directory, 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 pass this class. You must do your own work in designing, implementing, and testing your projects without assistance from anyone except for your instructor or, if properly documented, the other IC210 instructors for this semester, and (for Project 1) the current IC210 MGSP leaders. 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 (labs & 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 whom they collaborated with or received help from — this includes help received from an instructor in EI or from an MGSP mid.
Note: Although labs are treated as "routine" in this class, so that collaboration is allowed to the same extent as for homework, other courses in the department will treat them differently! So do not assume this is standard!

Any cheating will result in, at a minimum, a zero for the assignment, quiz, or exam in question.

• 30%: Final Exam (20 written, 10 practicum) The final exam will be cumulative, but will emphasize the last 6 Weeks of the course. It will have a written and practicum (hands-on programming) component.
• 32%: Exams 1 and 2 (10 written, 6 practicum for each) Both will have a written and practicum (hands-on programming) component.
• 21%: Projects
• 17%: Homeworks & Labs Expect a small assignment after every class. Assignments will be due at the beginning of the class following the assignment. No late submissions will be accepted without an excused absence. Labs will be demo'd to the professor during the lab session for credit. Any unfinished, required lab items must be finished and submitted as described above.

Mid-semester grades for the 6-Week and 12-Week marking periods will be calculated by applying the above weights to the averages for homework, projects and exams graded up to that point. So, for example, your "Final Exam" grade component at the 12-week point would be taken as the average of the 6 and 12 week exams. Any changes to the grading policy will be announced in class and be reflected by changes in this document.

• calling the section to attention at the beginning and end of class reporting absences to the instructor
• contacting the department office (3-6800, Room 346) if the instructor is more than 10 minutes late for class
• directing the class in productive work if the instructor is absent

• Unless specifically directed to do so, you will not be using your laptops during class. So please do not have them up and and open on your desks.
• Beverages are permitted in classrooms and labs provided they are in closed containers. No food is permitted in classrooms or labs.