6.3

CS 3500: Object-Oriented Design

Syllabus --Spring 2017

Meeting places & times

Course staff & office hours

Instructors

  

Amit Shesh

  

ashesh@ccs

  

310A WVH

  

Mon 10:00–12 noon,
Thurs 3:00–4:30pm,
and by appointment

  

Benjamin Brown

  

brown.benjam@husky

  

WVH 102

  

Sun 2–6pm

  

Jake Dec

  

dec.j@husky

  

WVH 102

  

Fri 4–6pm Tues 4–6pm

  

John Gallagher

  

gallagher.john1@husky

  

WVH 102

  

Tues 6–8pm Sat 4pm–6pm

  

Kevin Liu

  

liu.jianq@husky

  

WVH 102

  

Tues 11am–1pm Wed 12 noon–2pm

  

Bryan Wehner

  

bwehner@ccs

  

WVH 102

  

Fri 11:10am-3:10pm

  

Chenxi Yuan

  

yuan.ch@husky

  

WVH 102

  

Thurs 1–5pm

CCIS Tutors:

  

See here

Amit Shesh
Amit Shesh

Benjamin Brown
Benjamin Brown

Jake Dec
Jake Dec

John Gallagher
John Gallagher

Kevin Liu
Kevin Liu

Bryan Wehner
Bryan Wehner

Chenxi Yuan
Chenxi Yuan


General information

CS 3500 teaches a rigorous approach to object-oriented programming and design, with an emphasis on abstraction, modularity, and code reuse as applied to the building and understanding of large-scale systems. We will explore the basic mechanisms and concepts of object-oriented programming: object, class, message, method, interface, encapsulation, polymorphism, and inheritance. Students will gain hands-on experience with tools and techniques that facilitate the creation and maintenance of applications using the Java programming language.

Prerequisites

This course assumes familiarity with programming in the style of How to Design Programs, and basic knowledge of the Java programming language as introduced in CS 2510.

Exams

We will have two examinations:


Materials

Software

For programming assignments, we will use Java 8. You should download and install the Java SE Development Kit, version 8 from Oracle.

The supported IDE (integrated development environment) for the course is IntelliJ IDEA. This is the IDE that the instructor uses in lecture, and we may occasionally give instructions for how to perform particular tasks in IDEA. You are free to use a different IDE, but we may not be able to help you if you run into trouble. IntelliJ IDEA Community Edition may be downloaded free of charge, and we’ve posted instructions to license the Ultimate Edition on Piazza.

If you are having trouble setting up IntelliJ, we have a video demonstrating how to configure your environment here.

Books

There is no required textbook, but you may find these books useful.

Online resources


Lectures

This table specifies the lecture schedule; topics are tentative.

Date

 

Topics (tentative and approximate)

 

Materials

01/10 T

 

Why object-oriented design?

 

notes

01/13 F

 

The essence of objects

 

notes

01/17 T

 

Java review

 

notes and notes

01/20 F

 

Java safari

 

notes

01/24 T

 

Java safari (part 2)

 

notes

01/27 F

 

Version control with Git

 

Git explanation tutorial and Interactive tutorial

01/31 T

 

Introducing the Model, and the Builder pattern

 

notes

02/03 F

 

Controllers and Mocks;
Class Activity: abstracting I/O

 

notes

02/07 T

 

Design critique: testing, toString, Pile abstractions, I/O

 

02/10 F

 

Encapsulation and Invariants

 

notes

02/14 T

 

Design exercise: Turtles

 

code

02/17 F

 

Inheritance vs. composition

 

notes

02/21 T

 

Intro to Performance

 

notes and notes

02/24 F

 

More performance

 

notes and notes

02/28 T

 

First exam

 

In class

03/03 F

 

Class activity: GUI, MIDI basics

 

MVC code, starter code and code

03/07 T

 

Spring break (no classes)

 

03/10 F

 

Spring break (no classes)

 

03/14 T

 

Design critique: music models

 

Recorded lecture

03/17 T

 

The Adapter pattern

 

notes

03/21 T

 

The strategy and decorator patterns

 

notes

03/24 F

 

Class activity: Strategic FreeCell

 

03/28 T

 

Case study: Interpreters

 

code

03/31 F

 

Case study: Interpreters

 

04/04 T

 

Introduction to JavaScript

 

04/07 F

 

JavaScript inheritance and patterns

 

04/11 T

 

Exam review

 

04/14 W

 

Promises

 

04/18 T

 

Final exam

 

04/21 F

 

Bonus lecture (Android?)

 


Testing

Testing your code is sufficiently important that we’ve devoted an entire page to it. Please read these notes, for each and every assignment you work on.


Homework schedule

Homework will usually be due at 8:59 PM; the day of the week varies, so you should check each individual assignment to be sure. General homework policies are here.

This homework schedule is tentative and subject to change at the instructor’s discretion.

Link

  

Assigned

  

Due

Assignment 1: Java finger exercises

  

Fri 01/13

  

Fri 01/20

Assignment 2: The Model

  

Sat 01/21

  

Mon 01/30

Assignment 3: Interface Design & Representation Design

  

Wed 02/01

  

Fri 02/10

Assignment 4: A Freer FreeCell

  

Mon 02/13

  

Tue 02/21

Assignment 5: The Music Creator: First Movement

  

Fri 02/22

  

Fri 03/03

Assignment 6: The Music Editor: Second Movement

  

Sat 03/04

  

Tue 03/21

Assignment 7: The Music Editor: Third Movement

  

Wed 03/22

  

Wed 04/05

Assignment 8: The Music Editor: Coda

  

Thu 04/06

  

Sat 04/15

Assignment 9: The Music Editor++

  

Wed 04/19

  

Mon-Wed 04/24-04/26


Course policies

Collaboration and academic integrity

You may not collaborate with anyone on any of the exams. You may not use any electronic tools, including phones, tablets, netbooks, laptops, desktop computers, etc. If in doubt, ask a member of the course staff.

Some homework assignments will be completed with an assigned partner, and some may involve a larger team (TBD). You must collaborate with your assigned partner or team, as specified, on homework assignments. You may request help from any staff member on homework. (When you are working with a partner, we strongly recommend that you request help with your partner.) You may use the Piazza bulletin board to ask questions regarding assignments, so long as your questions (and answers) do not reveal information regarding solutions. You may not get any help from anyone else on a homework assignment; all material submitted must be your own. If in doubt, ask a member of the course staff.

Providing illicit help to another student is also cheating, and will be punished the same as receiving illicit help. It is your responsibility to safeguard your own work.

A subtler form of cheating, but nevertheless illegal, is self-plagiarism. This is when you copy and submit code that you developed when you took CS 3500 previously for credit again. This is illegal if done for your group assignments, because the code you are attempting to submit has not been written just by you and your partner in the current semester.

Students who cheat will be reported to the university’s office on academic integrity and penalized by the course staff, at our discretion, up to and including failing the course.

If you are unclear on any of these policies, please ask a member of the course staff.

Homework

In general, you should submit your homework according to the instructions on the web page for the individual assignments.

Submitting by email

Homework will ordinarily be submitted to the CS 3500 submission server at https://handins.ccs.neu.edu. However, sometimes (detailed below) it may be necessary to submit by email. In this case, email your instructor with the subject line “HW N submission” (where N is the appropriate homework number). Attach to your email submission the ZIP file exactly as how you would have submitted it to the server.

}

Submission troubles

If you have trouble submitting to the server and you have time before the deadline, please wait few minutes and try again; it may also be worth checking on Piazza to find out whether other students are experiencing similar difficulties. If upon retrying you still cannot submit, email Dr. Shesh (ashesh@ccs). Or if you don’t have time to try again then you should submit by email.

Late days & late work

Each student gets four free, no-questions-asked late days for the term. The purpose of late days is make the extension process fair and transparent by getting the instructors out of the extension-granting business entirely. Instead, when you need an extension, you can take one—provided you have a late day remaining.

To use a late day, log on to the submission server after the deadline has passed. You will see a link to request a late day for the particular homework. The server will keep track of the number of used late days. Conserve your late days carefully.

No more than one late day may be used on any one homework. You may not look at and must avoid gaining knowledge of the self-evaluation questions until you have submitted your late assignment. Late days cannot be divided fractionally, but must be used whole. Late days cannot be transferred to or shared with a partner, so in order to take an extension both you and your partner must have sufficient late days remaining. Choose your partners carefully.

Using a late day to submit your files does not automatically grant you a late day for the self-eval: it will remain due at the normal time.

Grades

Your grade will be based on your performance on the problem sets (60%) and the exams (15%, 25%). Material for examinations will be cumulative.

The grades will computed on an absolute basis: there will be no overall curving. The instructor may choose to curve an individual homework or exam, but please do not bank on such a chance.

The mapping of raw point totals to letter grades is given below. Please note that these grade boundaries may move slightly at the discretion of the instructor, but the grade boundary for A is unlikely to change.

Range

  

Letter grade

93% and above

  

A

90%-92.99%

  

A-

86%-89.99%

  

B+

83%-85.99%

  

B

80%-82.99%

  

B-

76%-79.99%

  

C+

73%-75.99%

  

C

70%-72.99%

  

C-

66%-69.99%

  

D+

63%-65.99%

  

D

60%-62.99%

  

D-

0%-59.99%

  

F