CMSC 433, Spring 2014 -- Syllabus

CMSC 433, Spring 2014

Programming Language Technologies and Paradigms

Syllabus

Optional Textbook

Java Concurrency in Practice by Brian Goetz, Tim Peierls, Joshua Bloch, Joseph Bowbeer, David Holmes and Doug Lea. ISBN 0-321-34960-1.

Topics

The topics for the class are taken from a variety of sources. There will be readings from both texts and web resources. Here is the tentative topic list (likely to be changed as the semester progresses):

Introduction
Concurrency
- Intro to Concurrency
- Modeling Concurrent Systems
- Java threads
- Java memory model
- Synchronization: locking (synchronized) and signaling (wait/notify)
- Design forces (safety, liveness/deadlock, performance, reusability)
- Threaded programming patterns
- Synchronizers
- Advanced Locking
- Non-blocking data structures
Event-based programming (Java NIO, Android)
Distributed Programming (RMI)

Grading

For most of the topics in this class, you will learn by doing. So this class will place a substantial emphasis on programming projects. The expected work and grading breakdown is shown below (we will inform you if it changes). We reserve the right to take into account circumstances other than the ones indicated below in calculating the grade (e.g., class participation, appearance at office hours, etc.).

	#	% each	% total
Programming projects	5	10	50
Mid-term	1	25	25
Final	1	25	25

Projects

Projects are to be done individually, unless explicitly specified otherwise in the project description.
Projects are due at midnight on the due date.
Projects may be turned in late up until 9am the next morning. Late submissions receive a 0.8 multiplier. We will grade your latest submission. If you submit both on time and late, only the late submission will be graded (and it will receive the 0.8 multiplier). NOTE: Read this carefully. It is generally NOT in your interest to submit late. So start early.
Submit early and often. The solution submitted last before the deadline is the one that will be graded.
You must demonstrate a good faith attempt to complete each programming project and submit it by that project's late due date. If you do not, the instructor may fail you for the entire course.
Your success on this course's exams will depend on understanding gained through the programming projects. Do not let anyone spoon-feed you the way to solve the programming projects, because this will leave you unprepared for the exams.

Regrades

Any regrades for project or exams must be requested within one week of the date your initial grade was given to you.

Academic Dishonesty

The University of Maryland, College Park has a nationally recognized Code of Academic Integrity, administered by the Student Honor Council. This Code sets standards for academic integrity at Maryland for all undergraduate and graduate students. As a student you are responsible for upholding these standards for this course. It is very important for you to be aware of the consequences of cheating, fabrication, facilitation, and plagiarism. For more information on the Code of Academic Integrity or the Student Honor Council, please visit the Student Honor Council website for more information.

Here are some highlights of this Code as it applies to this course:

The standard penalty for any academic dishonesty, including facilitating academic dishonesty, is to receive a grade of XF in the course. This grade denotes failure due to academic dishonesty.
All graded materials (whether exams or programming assignments) must be strictly individual efforts.
Allowing another student to examine a listing of your program or examining the listing of another student's program, for any reason, is strictly forbidden. This includes posting or displaying your code in a place or manner in which it is reasonably likely that others will see it.
Logging onto another student's account, for any reason, is academic dishonesty.
Attempting to falsely represent the correctness of your program, or to delay other members of the class from completing a programming assignment, is academic dishonesty
We expect you to follow all guidelines for responsible machine usage.
The instructor is the information owner for all CSIC accounts in this class, and all files in those accounts may be inspected by him at any time, and may be used by him as he sees fit to support educational ends.

Policies and Responsible Conduct

Cell phones. As a courtesy to your fellow classmates, pagers and cell phones must be off or on vibrate during class. Having cell phones or pages ring during class repeatedly can result in points being deducted from a student's semester grade.

Office Hours and E-mail. Questions concerning the content of the course or project should, as a general rule, be directed to the class discussion forum. This allows questions to be answered by whoever is monitoring the forum, and the answer can benefit all students.
The instructors (Dr. Porter and the TAs) are happy to answer questions during office hours and on the discussion forum. However, office hours and email are not intended as a replacement for attending lectures and recitations. As a result, instructors will only respond to questions, whether during office hours or on the newsgroup, from those students who regularly attend class. Instructors may not respond to electronic questions instantly. However, the instructors will try to respond to email by the next regularly scheduled office hour after it is sent. If a student cannot make it to scheduled office hours, he or she is encouraged to make an appointment by e-mail or after class.

Excused Absences. Any student who needs to be excused for an absence from a single lecture, recitation, or lab due to a medically necessitated absence shall:

Make a reasonable attempt to inform the instructor of his/her illness prior to the class.
Upon returning to the class, present their instructor with a self-signed note attesting to the date of their illness. Each note must contain an acknowledgment by the student that the information provided is true and correct. Providing false information to University officials is prohibited under Part 9(i) of the Code of Student Conduct (V-1.00(B) University of Maryland Code of Student Conduct) and may result in disciplinary action.

The self-documentation may not be used for the Major Scheduled Grading Events as defined below and it may only be used for only 1 class meeting during the semester. Any student who needs to be excused for a prolonged absence (2 or more consecutive class meetings), or for a Major Scheduled Grading Event, must provide written documentation of the illness from the Health Center or from an outside health care provider. This documentation must verify dates of treatment and indicate the time frame that the student was unable to meet academic responsibilities. In addition, it must contain the name and phone number of the medical service provider to be used if verification is needed. No diagnostic information will ever be requested. The Major Scheduled Grading Events for this course include:

Midterm Exam - 3/13/14 during the lecture period
Final Exam - 5/15/15 8:00am - 10:00am in the regular classroom.

Accommodating Disabilities. Any student eligible for and requesting reasonable academic accommodations due to a disability must provide the instructor with a letter of accommodation from the Office of Disability Support services (DSS) within the first two weeks of the semester.
Course Evaluations. I take your feedback seriously. At the end of the semester you will be able to fill out a course evaluation at www.courseevalum.umd.edu. However, while this feedback may benefit future students it doesn't help you. So if you have a question, concern, suggestion, etc. let me know now, while I still have a chance to address it.

Web Accessibility