CSE 2221 1:50 PM Section (Boggus) Home Page

Class Meetings

TuTh 1:50-2:45PM (lecture/activity) in Baker Systems Engineering 188
WeFr 1:50-2:45PM (closed lab) in Baker Systems Engineering 470

Midterm Exams

Thursday, September 22 in Baker Systems Engineering 188
Thursday, October 27 in Baker Systems Engineering 188

Final Exam

Friday, December 9th, 4:00-5:45PM in Baker Systems Engineering 188

Instructor

Matt Boggus (.2)
- Office: Dreese Labs 279
- Office hours:
  - Monday 1:30-3pm, Friday 3-4:30pm,
  - and by appointment

Graders

Drishti Mittal (.138)
- Office: Caldwell 420
- Office hours:
  - Monday 10:30am-12:30pm
  - and by appointment

Rob Donahey (.16)
- Office: Caldwell 420
- Office hours:
  - Wednesday 6:30-7:30pm and Thursday 3-5pm
  - and by appointment

Attendance Policy

Attendance at lecture periods is highly encouraged, but not required.
Attendance at lab periods is required.
You will be allowed 4 lab absences without penalty. Any lab absence over this limit will result in a 0.5-point deduction from your overall score for each absence.
In order to get credit for attendance in lab, you need to either 1) have your completed lab checked by a grader or me, or 2) be present and working for the majority of the period (45-50 minutes).
For cases where you fall into the second category and do not fully complete a lab activity during the lab period, you should complete it on your own later.
For any closed labs meetings that you miss, you may complete the lab on your own and demonstrate the finished work to me to have it not count towards your absence count.

Collaboration and Cheating

If you have not done so already, read the shared course policies here: http://web.cse.ohio-state.edu/software/web/policies.html
You are permitted to discuss homeworks and closed labs with your peers. This does NOT extend to copying or sharing of answers. If you want to be prepared for the final exam, you need to practice solving problems and writing answers to them.
You may NOT work with anyone else on the projects. If you need guidance, contact me or the graders via email or office hour visit, or ask on MS Teams or Piazza. If you ask a question about a project on Piazza, DO NOT POST ANY CODE; sharing code for projects with other students is considered to be cheating (except in cases where you work on parts of the projects in closed labs).

General Project Notes

Start early! Giving yourself only one day to work on a project is not enough time to complete it thoroughly.
Check your submissions! After uploading a project onto Carmen, download it yourself and see if you turned in the correct files and that they compile and run correctly. Submissions for the wrong project and those that don't compile get a zero, this is easily avoided if you check your work.
Software Sequence Course Policies page provides a brief outline on how projects are graded.
Generally speaking, we grade 2221 projects mainly on functionality (i.e. how many of our test cases does your code handle correctly) and slightly on style (fixing CheckStyle and FindBugs errors and making an attempt to comment your code).

Ask for help when you get stuck. The graders and I want you to succeed in this class and in your future studies, part of that is learning when and how to ask for help.

Additional 2221 advice or Java practice links

Link back to 2221 general homepage