6.3

CS 3500: Object-Oriented Design

Syllabus – Summer I 2020

Course staff

Instructors

  

Amit Shesh
Amit Shesh
ashesh@ccs
132C Nightingale

  

Clark Freifeld
Clark Freifeld
ccf@ccs
132G Nightingale

  

Jason Hemann
Jason Hemann
j.hemann@northeastern
326 WVH

  

Vidoje Mihajlovikj
Vidoje Mihajlovikj
v.mihajlovikj@northeastern
132E Nightingale

  

Meredith Bittrich
Meredith Bittrich
m.bittrich@northeastern
132E Nightingale

Staff

  

Kartik Aggarwal
Kartik Aggarwal
aggarwal.kar@husky

  

Pankaj Badgujar
Pankaj Badgujar
badgujar.p@husky

  

Ram Tarun Balagam
Ram Tarun Balagam
balagam.r@husky

  

Yeshwanthreddy Beeravolu
Yeshwanthreddy Beeravolu
beeravolu.y@husky

  

Emma Brown-Carley
Emma Brown-Carley
brown-carley.e@husky

  

Sophia Crennan
Sophia Crennan
crennan.s@husky

  

Saurabh Datir
Saurabh Datir
datir.s@husky

  

Ritesh Desai
Ritesh Desai
desai.rit@husky

  

Yatharth Desai
Yatharth Desai
desai.ya@husky

  

Stephen Dorris
Stephen Dorris
dorris.s@husky

  

Danish Farooq
Danish Farooq
farooq.d@husky

  

Saleha Farooqui
Saleha Farooqui
farooqui.s@husky

  

Thomas Hwang
Thomas Hwang
hwang.t@husky

  

Jovan Jean
Jovan Jean
psvitajj@gmail

  

Tanay Vinayak Joshi
Tanay Vinayak Joshi
joshi.ta@husky

  

James Kuesel
James Kuesel
kuesel.j@husky

  

Shubham Kurkure
Shubham Kurkure
kurkure.s@husky

  

Mayur Kurup
Mayur Kurup
kurup.m@husky

  

Karmen Lu
Karmen Lu
lu.kar@husky

  

Qiaoying Ma
Qiaoying Ma
ma.qiao@husky

  

Abdel-Rahman Madkour
Abdel-Rahman Madkour
madkour.a@husky

  

Fiona McCrae
Fiona McCrae
mccrae.f@husky

  

Luke Nardini
Luke Nardini
nardini.luke@husky

  

Cameron Perry
Cameron Perry
perry.ca@husky

  

Sohil Pyati
Sohil Pyati
pyati.s@husky

  

Siddhesh Rane
Siddhesh Rane
rane.si@husky

  

Ruthvik Ravindra
Ruthvik Ravindra
ravindra.r@husky

  

Colin Riley
Colin Riley
riley.colin5@husky

  

Matthew Salomon
Matthew Salomon
salomon.m@husky

  

Sunny Shukla
Sunny Shukla
shukla.su@husky

  

Anirudh Singh
Anirudh Singh
singh.anir@husky

  

Tanveer Singh
Tanveer Singh
singh.tan@husky

  

Jaison Titus
Jaison Titus
titus.ja@husky

  

Maxim Turkowski
Maxim Turkowski
turkowski.m@husky

  

Alp Tutkun
Alp Tutkun
tutkun.a@husky

  

Peixin Wang
Peixin Wang
wang.peixi@husky

CCIS Tutors:

  

See here

  

  

Office Hours Schedule

Office hours are spread among several rooms; please check this calendar carefully to know where and when staff will hold their office hours.

Meeting places & times

  • Amit Shesh

  

Virtual

  

MTWR

  

9:50am — 11:30am

  • Jason Hemann

  

Virtual

  

MTWR

  

1:30pm — 3:10pm

  

  

MTWR

  

3:20pm — 5:00pm

  • Vidoje Mihajlovikj

  

Virtual

  

MTWR

  

1:30pm — 3:10pm


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.

Materials

Software

For programming assignments, we will use Java 11. You should download and install the Java SE Development Kit, version 11 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 you can also license the Ultimate Edition.

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
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.


Schedule

Lectures

How to read lectures

To get maximum benefit from lecture notes, please follow these steps:

  1. Before the scheduled lecture in class:

    • (3-5 minutes): Go through the lecture objectives to understand the context. If applicable, try to connect the objectives with material from previous lectures

    • (1 hour): Read the lecture notes

      • Take notes as you read, just like in a class

      • After each section, summarize it in your own words in your notes

      • As you read the notes, jot down any questions you have immediately. If they get resolved later in the notes, cross them out

      • For each example in the lecture notes, try to come up with your own example that shows the same concept

      • Highlight your summaries, and any unresolved questions. These are your guidelines for the actual class lecture

  2. Attend lecture. Add to your notes. Ask unresolved questions during or after class

  3. (10 minutes): After class, skim through your notes quickly to make sure you have understood everything

Lecture Schedule

This table specifies the lecture schedule; topics are tentative.

Date

 

Topics (tentative and approximate)

 

Materials

05/04 M

 

Why object-oriented design?

 

notes and notes

05/05 Tu

 

Java review

 

notes and notes

05/06 W

 

Java review

 

notes, notes and notes

05/07 Th

 

Java safari

 

notes

05/11 M

 

MVC and introducing the model

 

notes

05/12 Tu

 

Introducing the Model, and the Builder pattern

 

notes and notes

05/13 W

 

Controllers and Mocks;
Class Activity: abstracting I/O

 

notes

05/14 Th

 

Controllers and Mocks;
Class Activity: abstracting I/O

 

notes and notes

05/18 M

 

Encapsulation and Invariants

 

notes

05/19 Tu

 

Design exercise: Turtle Graphics

 

notes

05/20 W

 

Command Pattern

 

notes

05/21 Th

 

Exam Review

 

05/25 M

 

Memorial Day: no classes

 

05/26 Tu

 

Exam 1

 

05/27 W

 

Inheritance vs. composition

 

notes

05/28 Th

 

Intro to Performance

 

notes and notes

06/01 M

 

Introduction to Views, GUI basics

 

notes

06/02 Tu

 

GUI basics, intro to ICE4

 

notes and notes

06/03 W

 

The Adapter pattern

 

notes

06/04 Th

 

The strategy and decorator patterns

 

notes

06/08 M

 

Model Design Discussion

 

06/09 Tu

 

Exam 2 review

 

06/10 W

 

Exam 2

 

06/11 Th

 

Design Principles; Case study: SceneGraph

 

code

06/15 M

 

Design Principles; Case study: SceneGraph

 

code

06/16 Tu

 

Introduction to JavaScript

 

06/17 W

 

JavaScript continued

 

06/18 Th

 

More JavaScript

 


Graded Work Schedule

Assignments

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

  

Mon 05/04

  

Fri 05/08

Assignment 2: The Model

  

Sat 05/09

  

Fri 05/15

Assignment 3: Interface Design & Representation Design

  

Sat 05/16

  

Fri 05/22

Assignment 4: The Polymorphic Marble Solitaire

  

Sat 05/23

  

Fri 05/29

Assignment 5: ExCELlence — The Easy Animator: Part 1

  

Sat 05/30

  

Wed 06/03

Assignment 6

  

Thu 06/04

  

Fri 06/12

Assignment 7

  

Fri 06/12

  

Thu 06/18

Exams

We will have two examinations:


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.

Using the handin server

You will submit your homework using https://handins.ccs.neu.edu. We have written a how-to guide for using the handin server, if you are unfamiliar with it. (To log in to the handin server, you will need an active CCS account. If you are a CS major or have taken a CS class before, you should have one already. If you have forgotten your account name or password, go to https://my.ccs.neu.edu/ and click on the “Forgot Username” or “Forgot Password” links. If you have never created an account before, click on the “Apply for an account” link in the upper right corner.) Make sure you can log in to the handin server, and register for your section of the course, before the first homework is assigned.

Unlike prior semesters, you will usually need to submit multiple files for your assignments, rather than a single file. You should therefore add all your files to a .zip or .tar file, and submit that archive file. Note:

Additionally, every homework where you write code will be followed one day later by a self-evaluation assignment. Only one partner (for team assignments) needs to complete the self-eval, and it will count for both partners.

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 your professor. Your email should have the subject “HW N submission problems” (where N is the appropriate homework number), and you should attach the ZIP file exactly as you would have submitted it to the server.

Late days & late work

Each student gets four free, no-questions-asked late days for the term. Two of these days can be used for individual assignments, and two will be for group assignments. 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, just submit the homework as normal. The server will keep track of the number of used late days, and will prevent you from submitting more than one day late to any assignment, or late at all if you’ve used all your 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%), in-class exercises (1-2%), and the exams (15%, 24%). 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. Grades are not rounded: for instance, earning a 92.5% does not imply we will round up to a 93% and hence to an A.

Range

  

93%

  

90%

  

87%

  

83%

  

80%

  

77%

  

73%

  

70%

  

67%

  

63%

  

60%

  

0%

Letter grade

  

A

  

A-

  

B+

  

B

  

B-

  

C+

  

C

  

C-

  

D+

  

D

  

D-

  

F