8.10

CS 3500: Object-Oriented Design

Syllabus – Fall 2023

Course staff

Instructors

  

Benjamin Lerner
Benjamin Lerner
blerner@ccs
WVH 326

  

Lucia Nunez
Lucia Nunez
l.nunez@northeastern
Meserve 335

  

Vidoje Mihajlovikj
Vidoje Mihajlovikj
v.mihajlovikj@northeastern
Meserve 309

  

Amy Gately
Amy Gately
a.gately@northeastern
Meserve 301

Staff

  

Adeyinka Adedewe
Adeyinka Adedewe
adedewe.a@northeastern

  

Ayman Ahmad
Ayman Ahmad
ahmad.ay@northeastern

  

Tarun Ari
Tarun Ari
ari.t@northeastern

  

Christian Bernier
Christian Bernier
bernier.c@northeastern

  

Charles Bershatsky
Charles Bershatsky
bershatsky.c@northeastern

  

Aretha Chen
Aretha Chen
chen.ar@northeastern

  

Jonathan Chen
Jonathan Chen
chen.jonath@northeastern

  

Erika Ding
Erika Ding
ding.er@northeastern

  

Jona Fejzaj
Jona Fejzaj
fejzaj.j@northeastern

  

Vidya Ganesh
Vidya Ganesh
ganesh.vi@northeastern

  

Nathan Gooneratne
Nathan Gooneratne
gooneratne.n@northeastern

  

Valay Gundecha
Valay Gundecha
gundecha.v@northeastern

  

Diego Hernandez
Diego Hernandez
hernandez.die@northeastern

  

Jane Kamata
Jane Kamata
kamata.j@northeastern

  

Derek Kaplan
Derek Kaplan
kaplan.de@northeastern

  

Veena Kodakirthi
Veena Kodakirthi
kodakirthi.v@northeastern

  

Hyun Kong
Hyun Kong
kong.hy@northeastern

  

O'Neal Kpodar
O’Neal Kpodar
kpodar.o@northeastern

  

Garrett Ladley
Garrett Ladley
ladley.g@northeastern

  

Alexander Malakov
Alexander Malakov
malakov.a@northeastern

  

Easha Patel
Easha Patel
patel.ea@northeastern

  

Shaan Patel
Shaan Patel
patel.shaan@northeastern

  

Rakshika Raju
Rakshika Raju
raju.r@northeastern

  

Minda Ren
Minda Ren
ren.mi@husky

  

Patrick Sanpietro
Patrick Sanpietro
sanpietro.p@northeastern

  

Micah Weston
Micah Weston
weston.m@husky

  

Jonathan Yu
Jonathan Yu
yu.jona@northeastern

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

  • Benjamin Lerner

  

Snell Engineering 168

  

MWR

  

9:15am — 10:20am

  • Benjamin Lerner

  

Snell Engineering 168

  

TF

  

1:35pm — 3:15pm

  • Lucia Nunez

  

Churchill Hall 101

  

MR

  

11:45am — 1:25pm

  • Vidoje Mihajlovikj

  

Shillman Hall 125

  

MW

  

2:50pm — 4:30pm


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


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 gives the approximate lecture schedule. Since our sections meet on different days of the week, individual lectures may be out of sync, but each week will stay synchronized.

Week

 

Topics (tentative and approximate)

 

Materials

09/06 – 09/08

 

Why object-oriented design?

 

notes

 

The essence of objects

 

notes

09/11 – 09/15

 

Java review

 

notes and notes

 

Java safari

 

notes

09/18 – 09/22

 

MVC and introducing the model

 

notes

 

The Builder pattern

 

notes

09/25 – 09/29

 

Controllers and Mocks;

 

notes

 

Class Activity: abstracting I/O

 

notes

10/02 – 10/06

 

Encapsulation and Invariants

 

notes

 

Design exercise: Turtle Graphics

 

code

10/09 M

 

No class: Indigenous Peoples Day

 

10/10 – 10/13

 

Command Pattern

 

notes

 

Inheritance vs. composition

 

notes

 

Design critique

 

10/16 – 10/20

 

Intro to Performance

 

notes and notes

 

Introduction to Views, GUI basics

 

notes

10/23 – 10/27

 

GUI basics, intro to ICE4

 

notes and notes

10/23 M

 

Exam 1

 

10/30 – 11/03

 

The Adapter pattern

 

notes

 

The strategy and decorator patterns

 

notes

 

Model Design Discussion

 

11/06 – 11/10

 

Design Principles; Case study: Puralax

 

notes

 

Design Principles; Case study: SceneGraph

 

code

11/13

 

Exam review

 

11/13 – 11/17

 

Slack

 

11/16 Th

 

Exam 2

 

11/20 – 11/21

 

Slack

 

11/22–11/24

 

No class: Thanksgiving break

 

11/27 – 12/01

 

Introduction to Javascript

 

12/04

 

Slack

 

12/06

 

Wrapup

 


Testing and Examplar

Understanding and implementating an assignment correctly are two distinct tasks, and demonstrating both tasks requires related but separate skills, and related but separate artifacts.

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.

Examplar

When possible this semester, we intend not just to provide test cases for your implementations, but also to provide a mechanism to test your understanding of the problem requirements. This system is called Examplar. It will take a bit of practice to get used to the system: read these instructions carefully, and be sure to work through the lab about it, prior to encountering it on your homework.

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. Most homework assignments have several parts to submit, so multiple deadlines are shown for each assignment. See each assignment for additional information.

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

Link

  

Assigned

  

Due

Assignment 1: Java finger exercises

  

Tue 09/12

  

Tue 09/19
Wed 09/20

Assignment 2: Playing with Cards, Part 1: The Model

  

Wed 09/20

  

Sat 09/23
Thu 09/28
Fri 09/29

Assignment 3

  

Fri 09/29

  

Mon 10/02
Sat 10/07
Sun 10/08

Assignment 4

  

Tue 10/10

  

Fri 10/13
Wed 10/18
Thu 10/19

Assignment 5

  

Fri 10/20

  

Tue 10/31
Wed 11/01

Assignment 6

  

Wed 11/01

  

Tue 11/14
Wed 11/15

Assignment 7

  

Wed 11/15

  

Tue 11/28
Wed 11/29

Assignment 8

  

Wed 11/29

  

Wed 12/06
Thu 12/07

Assignment 9

  

Wed 12/06

  

Before Wed 12/15

Exams

We will have two examinations during the semester:


Labs Schedule

Labs are all on Mondays this semester. Lab work will not always be submitted; read each lab carefully for more detail.

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

Link

  

Assigned

  

Complete by

Lab 0: IntelliJ Setup

  

Wed 09/06

  

Mon 09/11

Lab 1: Introduction to JUnit testing

  

Mon 09/11

  

Tue 09/12

Lab 2: Abstraction and access

  

Mon 09/18

  

Tue 09/19

Lab 3: The Builder pattern

  

Mon 09/25

  

Tue 09/26

Lab 4

  

Mon 10/02

  

Tue 10/03

Lab 5

  

Mon 10/16

  

Tue 10/17

Lab 6

  

Mon 10/30

  

Tue 10/31

Lab 7

  

Mon 11/06

  

Tue 11/07

Lab 8

  

Mon 11/13

  

Tue 11/14

Lab 9

  

Mon 11/20

  

Tue 11/21

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