Course Basics

Instructor:

Graduate Teaching Assistants:

Undergraduate Teaching Assistants:

Prerequisites: CS 112 (C or better) and access to a Java-capable computer
Format: Lecture plus weekly lab
Lectures:

Labs:

Textbooks:

Blackboard: Blackboard will be used for all official announcements, course slides, assignments (including submissions), and grades.

Piazza: Piazza will be used for online discussion; any information discussed on Piazza will be assumed to be known to students.

• Course schedule, announcements discussion. GTA/UTA contacts and office hours will be on Piazza too.
• Do not e-mail course staff about programming problems; use the discussion board.
• Use public posts on Piazza to discuss programming project requirements, labs, and other material related to the course.
• When prompted by a TA, use private posts on Piazza to share portions of your code pertaining to your questions. Don't share your project/excercise code in public posts.
• Email course staff only for logistical issues such as meeting outside of office hours, missing lab/lecture, grading disputes, medical situations, etc. Email addresses are listed on above and on Piazza.

Course Information

Course Description: Thorough treatment of programming according to object-oriented principles. Introduces classes, interfaces, inheritance, polymorphism, and single dispatch as means to decompose problems. Covers intermediate programming techniques including error handling through exceptions, arrangement of source code into packages, and simple data structures. Intermediate debugging techniques and unit testing are covered.

Outcomes

1. An understanding of basic object-oriented programming concepts and principles
2. An ability to apply basic object-oriented principles and techniques in the design and development of software systems using a specific programming language.
3. An ability to effectively use both basic command line tools and sophisticated integrated development environments, and to understand the benefits and limitations of each.
4. An ability to successfully perform debugging operations and techniques.

Coursework

zyBooks: online textbook with practice problems; weekly deadlines for completing the practices are checked automatically.
Programming Assignments:

• Lab Submissions : Programs that should be submitted at the end of weekly recitation sessions.
• Programming Exercises: programming assignments; open resources; collaboration/group work allowed; several days to submit.
• Projects: programming assignments; individual work; possibly more than a week to complete.
  

Grading Procedures

Grade Distribution

Grading Policies

• Grades within a category (i.e. midterms, projects, labs) are weighted equally.
• Students must have Respondus Browser locakdown installed before taking any tests or exams. A working webcam is also required to take the final exam.
• By department policy, the student must pass the final or the weighted average of all 4 tests and the final exam must be a passing grade (≥ 60) in order for a student to pass the course.
• The final exam is cumulative.
• Challenging of any grade must occur within a week of when the graded assignment has been returned.
• Any number of resubmissions are allowed (the most recent is used), however a resubmission turned in after the deadline will be considered a late submission.
• Lab exercise grading is fully automated. Tests and final exam may be hand-graded. Project grading is partially automated. Even when manually graded, code which does not compile will receive a zero in most cases.
• Absences are absorbed by the drop policy - in general, make-ups are not allowed except on exams ( under very special circumstances).
• Assignments are typically due at midnight on the listed due date.
• Late submission policy (up to 48 hours) is as follows: <=24 hours with 10% off, >24 hours &&<=48 hours with 25% off, > 48 hours will receive 0. Submission times are automatically recorded by Blackboard, and there is no distinction between a minute late and a day late. Please plan ahead to make sure that your submission is on time. Taking backups regularly is highly recommended.

Grading Scale

Tips

• Make backups, because the unexpected happens, and cannot be used as an excuse to get an extension.
• Submission times are automatically recorded by Blackboard, and there's no distinction between a tiny bit late and nearly a day late - plan ahead to make sure that your submission is on time.
• To receive a grade, the submission must be gradable. This means submitting .java source rather than compiled .class files or word documents containing the source. It also means that the code must be submitted on Blackboard rather than simply saved.

Honor Code

Unless specific instructions are given to the contrary, programming assignments are an individual effort, no group work is allowed. In addition to code, this includes the sharing of test cases, pseudocode, or approaches, receiving assistance in debugging code, as well as the use of external Internet sites .

Both the GMU Honor Code and the CS Department Honor Code apply in this class. Any use of a direct contribution on any program, homework, quiz, or exam will be reported as a violation of the honor code.

Special Accommodations

Students who have a right to accommodations due to disabilities or other conditions should discuss this with the instructor as soon as possible. Accommodations will follow the recommendations of the University's Office of Disability Services.

Programming Environment

All programs in lab assignments must compile and run in at least Java SE 8 environment. You can compile and run your source code from the command line or you can choose to use any IDE you prefer, for example Eclipse (recommended), NetBeans, DrJava or BlueJ. All of the necessary software can be freely installed on your PC. For any technical questions regarding software installation, lab assignments, Java programming, and development environment, please consult the GTA/UTA first. Programming assignments that cannot be compiled or run will receive zero points.

Schedule