Here is a calendar of all the office hours that the course staff offer. If you would like to speak to an instructor and you cannot make it to their office hours, send an email to set up a meeting. If you have a general question and cannot make it to anyone’s office hours, post to Piazza (see below).
For the most part, staff members will have the same office hours every week. Before going to someone’s hours, check where they will be on the calendar below. Should there be a change to someone’s hours, there will be a post on Piazza and the calendar will be updated.
Log in with your Khoury account credentials.
Go to CS 2510 on the top left.
Add your name to the queue. Enter the question you wish to ask. Be as detailed as possible.
Log in to Microsoft Teams using your Northeastern credentials. When it is your turn, we will get in touch with you via Teams.
Professor Razzaq’s office hours will be in Meserve 329, Wednesdays 3pm–4:30pm and by appointment.
Your TAs help run the labs, help grade the exams, and hold office hours. In general, they are apprentice teachers and are here to learn how to run a course. At the same time, though, they are your peers who have taken the course, and can see your problems from your perspective.
Your tutors help run the labs, grade the homework sets, and hold office hours. In general, they are people who are interested in helping others learn, and they are your peers who have taken the course, and can see your problems from your perspective.
If you need help, you may talk to any of the instructors, the TAs or tutors during their office hours.
Use Northeastern email (@northeastern.edu) to reach any of the course staff; usernames are given above.
Piazza is an on-line forum for class discussions. Anybody can post a question and anybody else can reply. (Please do not post grading questions to Piazza. It’s best to email the grader instead for those kinds of questions.)
Before posting, check whether or not your question has already been asked. If it already has been asked and has not yet been answered, provided the question is not more than a day old, it likely will be answered soon. Do not double post.
Posting any parts of a solution to any parts of a homework assignment is considered cheating. You don’t want to do this. Limit your answers to other students to providing clarity when needed and hints when appropriate. This is good practice should you ever want to be a tutor :)
Note: anonymity on Piazza is implemented to make you anonymous to students (if you prefer) but not to staff members.
Late assignment policy: An assignment that is one fraction of a second late is automatically counted as late by the handin server. Late submissions will be accepted for a grace period of up to 24 hours late, with a 4% penalty per hour per submission.
In addition, each student gets one (1) free, no-questions-asked late day for the term. The purpose of the late day is to make the extension process fair and transparent by getting the instructor out of the extension-granting business entirely. Instead, when you need an extension because of illness or travel or for whatever reason, you can take one—provided you have a late day remaining. To use a late day, let the instructor know, by email, that you want to use your late day and submit the homework as normal.
No submissions will be accepted after the due date and grace period have passed.
No other extensions will be granted. These policies apply to everyone equally. Conserve your late day carefully!
Feedback: Sometimes mistakes can happen so if you are confused or concerned about your feedback, don’t be afraid to reach out to a grader for further explanation. You must submit any requests for clarification at most 7 days after the homework/exam feedback was released. Note that asking us to regrade your work means that there is also a possiblility of losing points if a mistake was overlooked the first time.
Academic honesty: We will strictly enforce Northeastern’s academic integrity policy. You may discuss problems with other students, but you may not share or show code to anyone other than your assigned partner or the course staff. Violations of academic integrity will be reported to OSCCR and will have a negative impact on your grade. (See below for more details on this important policy.)
Sec 1: MWR at 9:15am–10:20am
SN 108 Razzaq
Sec 2: MWR at 10:30am–11:35am
CH 103 Razzaq
You are required to read the lecture material for the given lecture before coming to class. During the lectures we will discuss the material covered in the required reading, answer questions, provide additional examples and applications. You will be required to participate in and submit class work occassionally.
It is OK if you do not understand everything when you first read it, but reading about the new concept ahead of the time will give you a chance to anticipate the questions you may have and allow you to follow better the details of explanation during the lectures.
Section 3 (CRN: 11690): 9:50am-11:30am in WVH 210B
TAs: Jeffrey W. Tutors: Khoi N.
Section 4 (CRN: 11854): 9:50am-11:30am in WVH 212
TAs: Dave B. Tutors: Sutton
Section 6 (CRN: 15345): 11:45am-1:25pm in WVH 210B
TAs: Nitsa K., Malia W. Tutors: Amanda
Section 7 (CRN: 19743): 11:45am-1:25pm in WVH 212
TAs: Dave B. Tutors: Daniel K., Jan H.
Section 8 (CRN: 19744): 1:35pm-3:15pm in WVH 210B
TAs: Sarah K., Jaren A. Tutors: Daniel Y.
The goal of the labs is to see in practice problems that illustrate the concepts covered in the lectures, and to prepare you for the next programming assignment. Attendance is required.
There is a lot of technical detail related to running Java programs that will be covered in the early labs. Later labs will focus more on design questions and on good Java programming practice.
Lab attendance is required. We will be assigning some lab work to be submitted which will be graded. The goal of lab work is to see that you are familiar with the most basic concepts covered during the recent lectures, labs, and assignments.
If you have trouble completing lab work, it would be a good idea to meet with the instructor within the next week, to identify the problems you may have and to help you get back on track.
We may also be conducting code reviews in labs, of either the material from that lab or from the prior week’s homework. As presenters, be prepared to explain your design choices to your classmates. As reviewers, pay attention both to how the presenters organize their explanations and how they organize their code, and feel free to ask clarifying questions about either.
You will complete your assignments (other than the first one) using the Eclipse IDE. Though, if you feel more comfortable, you may choose to use another IDE (e.g. NetBeans) or work directly from the command line, but you and your partner must both be comfortable with the chosen programming environment, and the staff may not be able to assist you with issues encountered in other environments.
You will use the handin server to submit your homework. You may submit as many times as you wish, though submitting too frequently will be detected and rate-limited, to ensure fairness for other students. Be aware that close to the deadline when everyone submits all at once, the server will become slower. Don’t wait until the last minute to submit!
There will be one or two problem sets each week. The problem sets often include finger exercises and practice problems, that you are strongly encouraged to look at and confirm that you can solve. You are welcome to bring solutions to these problems to the course staff during the semester for informal feedback on how you’re doing.
The graded problems are to be solved collaboratively with your partner when you are assigned one in the second half of the term. The problems will consist of structured programming assignments that may be based on the work done in previous weeks, and may also include more creative projects where you can practice your design skills.
Assignments may not be resubmitted after their deadlines (and the grace period with penalties) have passed.
Due Dates: Mondays and Thursdays at 9:00pm, unless otherwise specified. See the late policy above.
Note: You will submit each problem separately on the handin server. This is for your benefit: the server will attempt to compile and run your program against automated test cases. Having separate submissions for each problem means that a syntax error in one problem won’t immediately prevent your other problems from compiling also. Be careful to submit the correct answers to the correct problems.
Your last submission will be graded. It is your job to make sure that the last submission is the one you want us to grade.
Although the homework problems can be solved individually, you must work on some of the problem sets in pairs in the second half of the term. You will get a partner from your lab section and you will work on labs together as well.
Important Pair programming means that you and your partner work on the problem sets jointly. You read them together and you work on the solutions together. One of the lab’s purposes is to teach you how to work in pairs effectively; indeed, pairs are provably more effective than individuals in programming. The rough idea is this: One of you plays pilot, the other co-pilot. The pilot works on the keyboard and explains aloud what is going on; it is the co-pilot’s responsibility to question everything. After a problem is solved to the satisfaction of both, you must switch roles.
Every partner must be able to solve every homework problem in the end. It is an academic integrity violation to submit work under your name that you have not worked on. Doing so may result in earning a 0 on the work and a report to OSCCR. You may also lose the privelege of working with a partner. Therefore both partners must make the effort to meet regularly and work together on every part of the assignments/labs.
If you are having difficulties working with your partner, please inform your lab TA or your instructor quickly: we cannot help if we don’t know there’s a problem.
Any and all submitted work must be your own. If an assignment/lab is to be completed individually, only you and the course staff are allowed to look at your code. If an assignment/lab is to be completed with a partner, only you, your partner and the course staff are allowed to look at your code (see above as well about working with a partner). Use of material from previous classes, solution manuals, material from the Internet or other sources (such as AI assisted tools like ChatGPT or sources such as parents, friends, siblings etc.) that directly bears on the answers is strictly prohibited.
You are allowed to discuss the problem sets with others, so long as you acknowledge (in comments, in your submitted files) whoever you discussed the problem with. Discussing the "what to solve" is OK, discussing "how to solve" is a slippery slope. Once you start discussing possible solutions, you may not realize when you have crossed the line. Ultimately we will judge you by the work you submit. If you think you are smart enough to use somebody’s code and hide it well enough to deceive us, please channel that intelligence towards completing the assignment yourself! Doing the assignments yourself is essential for doing well on the exams which tend to be higher stakes than homework.
NOTE: Be aware that while submitting someone else’s code is clearly a violation, so is sharing your code with others, even if you truly just mean to help. You will be doing your friend or peer a disservice by helping them this way. Please direct them to the course staff instead.
Outside an academic environment, sharing code with unauthorized parties can be a criminal offense and have severe and unanticipated consequences.
Submitting code that is not your own or sharing your code to unfairly help another student will be considered a violation of the University’s Academic Integrity Policy (page 38 of the 2022-2023 Undergraduate Student Handbook). Violations of academic integrity will be reported to OSCCR, and will have strong consequences on your grade, from an automatic zero on the assignment to failing the course.
If you are ever unsure of whether sharing is unacceptable or not, or you are struggling in the course, please contact one of the course staff. We are here to help.
You may bring one sheet of notes to exams (may be typed or hand-written, one-sided or double-sided).
Exam 1: October 20th
Exam 2: November 17th
40% homework. Most homeworks will be equally weighted, but larger projects that will take more time will be weighted more heavily.
50% exams, with exact proportions to be determined.
10% lab work, class work and quizzes
You can use the handin server to see the current weights of each assignment, and your approximate grade in the course so far. The exact weights of assignments, quizzes and exams may change during the semester, depending on exactly how many of each we have. We will try to keep weight changes as infrequent as possible.
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% 86% 83% 80% 76% 73% 70% 66% 63% 60% 0% Letter grade: A A- B+ B B- C+ C C- D+ D D- F