CSE 2221 9:10 AM Section (Chawla) Home Page
Class Meetings
- TuTh 9:10-10:05AM (lecture/activity) in DL 357
- WeFr 9:10-10:05AM (closed lab) in DL 280
Midterm Exams
- Thursday, September 22 in DL 357
- Thursday, October 27 in DL 357
Final Exam
- Friday, Dec 9, 8:00-9:45AM in DL 357
Instructor
- Piyush Chawla (.81)
- Office: Dreese Labs 680 & Zoom (check Carmen announcements)
- Office hours:
- Wednesday, Friday, 5:00-6:00 PM
- and by appointment
Graders
- Luke
- Office: Zoom (check Carmen announcements)
- Office hours:
- Tuesday, 4:00-5:30 PM
- Thursday, 7:30-9:00 PM
- and by appointment
- Sebastian
- Office: Zoom (check Carmen announcements)
- Office hours:
- Monday, 3:00-4:00 PM
- Tuesday, 10:00-11:00 AM
- and by appointment
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 Piazza. If you ask a question about a project on
Piazza, DO NOT POST ANY CODE; sharing code with other students is
considered to be cheating. [Au'21 note, we may no longer be using Piazza
due to legal reasons. The no sharing source code rule applies for
any communication tool we might be using]
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.
- If you have not already done so, read the Software
Sequence Course Policies page. It 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.
Important links