CS211 Object Oriented Programming

The Governor's School @ Innovation Park

Spring 2017 Syllabus

Course Information

Course	GMU CS211 G01/G02
GMU Credits	4
Instructor	Jitin Krishnan
Office	175 Discovery Hall, GMU PW Campus
Phone	703-993-7027
Email	jkrishn2 (at) gmu (dot) edu
Office Hours	Tuesdays 3:30 PM – 5:30 PM (GS office) OR Wednesdays 7:30 PM – 9:30PM (online) by appointment
Lecture	Tuesday & Thursday 7:30AM-9:20AM (G01 Jr) Tuesday & Thursday 9:30AM-11:15AM (G02 Sr) Room BR 247
Textbook	Required: Small Java How to Program (6^th Ed) by Deitel Optional: Introduction to Programming Using Java by Eck, Introduction to Programming in Java by Sedgewick & Wayne, Oracle Java Documentation

Course Outcomes

An understanding of basic object-oriented (OO) programming concepts and principles.
An ability to apply basic object-oriented principles and techniques in the development of software systems using a specific programming language.
An ability to effectively develop software systems using both basic command line tools and sophisticated integrated development environments, and to understand the advantages and limitations of each.
An ability to successfully perform debugging operations and techniques.
An ability to perform software development in both individual and team environments.
An understanding of programming-related references/resources available to software developers and the ability to use them effectively both in ongoing projects and in the acquisition of new technical skills.
An understanding of how acquired programming skills facilitate success in upper level CS courses and in various professional environments.

Prerequisites

C or better in CS112

Course Assessments

Readings/homework: Readings from the textbook relevant to each lecture and supplement materials will be posted every week. You will increase your understanding of lectures by reading associated textbook sections ahead of time. Short tasks/homework will be assigned daily based on the lecture and readings.
Labs: In every class, we will dedicate a section for labs where students will work on exercises and get immediate help. During lectures we will discuss programming concepts and instructors will provide demos of programming relevant to assignments.
Programming Assignments: There will be 6 programming assignments during the semester which are significantly more difficult than labs. It will require more planning, and in general no implementation level details will be given: you are free to use your creativity here. Notethat the projects in CS211 are very much concerned about the structure of your solutions, and not just that correct inputs to outputs are achieved. Late Submissions: No late submissions will be accepted for work that is to be submitted online. 10%of total assignment grade penalty per calendar day will apply for up to 7 days or until solutions to the assignment are posted or discussed in class. Any exceptions would be granted at the discretion of the course instructor. Having a laptop die or losing source code is not an excuse for turning in an assignment late — students are responsible for maintaining their own backup copies of code.
Quizzes: There will be short quizzes to ensure you stay up-to-date on course topics during the semester.
Tests: There will be 4 tests during the regularly scheduled lecture time.
Final Exam: At the end of the first semester, a comprehensive and cumulative exam will be given on: May 23, 2017.
Semester Project: Students will be working on a topic of their interest throughout the semester incorporating relevant course contents in their work. At the end of the semester they will present their work to the class.
HONOR CODE: You are free to discuss ideas for the coursework with other students; however, no joint work is permitted for anything exceptlabs, reading/homework, and semester project. Cite your resource or ask your instructor in case of a doubt. Any submitted work must be yours alone. All work will be manually or automatically assessed for cheating. Honor code violation may result in failing the course or referral to the Honor Committee.
- Read the CS Department Honor Code
- Read the University Honor Code

Grade Composition

9-Week Session:

Programming Assignments	30%
Tests	30%
Quizzes	20%
Semester Project	10%
Labs	5%
Homework/Readings	5%

Semester Grade:

1st 9-week	40%
2nd 9-week	40%
Final Exam	20%

Note: Per GMU Computer Science departmental policy, a failing grade on the final exam (<60.0%) will result in a failing grade (F) for the entire course, regardless of performance on other assignments.

Tentative Course Schedule

Week	Date	Topic	Programming Assignments	Homework due before class 7:25AM & Reading
1	Jan 31, Feb 02	Review : Control Structures, Arrays, Array Lists. Command Line Interface and JUnit Testing Basics		ed: Unit 2: 11-13, 17-20 Unit 3: 21-26, 28-30 Unit 5: 1-2 (Due Jan 31 & so on)
2	Feb 07, Feb 09	Review : Classes and Objects	*PA 1* (Due Feb 12 midnight)	ed: Unit 4: 31-35, 17-20 Unit 5: 3-5 *Barron’s* Ch 2
3	Feb 14, Feb 16	Review: Strings, File I/O, Exceptions		ed: *Barron’s* Ch 7
4	Feb 21, Feb 23	Four fundamental OOP concepts, Packages, Auto-boxing	*PA 2* (Due Feb 26 midnight)	*Deitel:* 8.15-8.16, 8.9
5	Feb 28, Mar 02	Inheritance, Polymorphism, Object Class	Test 1 (Mar 02)	ed: Unit 6: 7-10 *Barron’s* Ch 3
6	Mar 07, Mar 09	Inheritance, Polymorphism (continued…)	*PA 3* (Due Mar 14 midnight)	*Deitel:* Chapter 9, 10
7	Mar 14, Mar 16	Interfaces, Enumeration, Number Systems		ed: Unit 6: 11 Unit 2: 14-16 Unit 3: 1011
8	Mar 21, Mar 23	Generics, List<E> Interface, Collections and Iterators	Test 2 (Mar 23)	Generics Tutorial ed: Unit 6: 12
9	Mar 28, Mar 30	Algorithms, Searching, Sorting, and Big O (continued…)		ed: Unit 3: 27 Unit 7 *Barron’s* Ch 8
10	Apr 04, Apr 06	Algorithms, Searching, Sorting, and Big O (continued…), Recursion	*PA 4* (Due Apr 09 midnight)	ed: ed: Unit 4: 36-37 Unit 8 (2D arrays)
11	Apr 18, Apr 20	AP Prep Week	*Test 3:* *AP Preparation Test* (Apr 18, 20)	ed: Unit 5: 6 *Barron’s* Practice Exam Two, Three
12	Apr 25, Apr 27	Program Design and Analysis	*PA 5* (Due Apr 30 midnight)	*Barron’s* Ch 5 ed: Unit 9: Diagnostic Exam
13	May 02, May 04	May 02 - AP Exam Java Doc, Debugger		ed: Unit 9: ALL
14	May 09, May 11	Data Structures
15	May 16, May 18	May 16 REVIEW	*Test 4:* *Lab Exam* (May 18)
16	May 23 May 25	Final Exam (May 23)
17	May 30, June 01	Graphics and Java 2D, Color, Picture Regular Expressions, Lambda expressions, Streams	*PA 6* (Due June 4 midnight)
18	June 06, June 08	Miscellaneous Topics
19	June 13	Miscellaneous Topics	PA7 (Juniors Only) (Due June 14 midnight)

General Policies: (Please read carefully)

Communication: Students will check email (GMU) daily and Blackboard for class announcements, agenda of the week including homework, web-assignments, and class notes.
Make-Up policy: In order to make up work, student must have an excused absence. Student receiving excused absence will be responsible for making an arrangement for make-up work within two days (quiz or test only) after his/her return. Student needs to complete the makeup test in the first class after return. Absences must be excused within the timeframe specified in The Governor's School Student Handbook. * Only notes from doctor’s offices and school counselors are considered as official documents for excused absence in order to make up major tests.
Classroom Behavior and Discipline: Please refer to Student Handbook.