CMSC 433
Programming Language Technologies and Paradigms
Fall 2012



Overview: This course covers principles associated with programming concurrent and distributed software. Specific topics to be covered will come from the following list: concurrency, threads and processes, synchronization, design considerations (safety, liveness/deadlock, performance, reusability), algorithm parallelization, and distributed system development. Other topics may be introduced at the discretion of the instructors. Here is a tentative lecture schedule for the semester.
Prerequisites: CMSC 330 and permission of CS Department
Instructors:
Section 0101
Rance Cleaveland
4111 AV Williams Building
rance -at- cs umd edu
301-405-8572
    Section 0201
Evan Golub
1115 AV Williams Building
egolubUMD -at- gmail com
301-405-0180
Time / Place:
MW 3:30-4:45 / CSIC 1121     TuTh12:30-1:45 / CSIC 3120
Teaching Assistants: Daozheng Chen and William Goh
Office Hours: Listed on the web site after the first week of classes.
Text: Both sections will have a recommended (not required) textbook of Java Concurrency in Practice by Brian Goetz. Its ISBN‑13 number is 978-0321349606. Available at the University Book Store and Maryland Book Exchange and many other stores such as Amazon in paperback and Kindle formats as well as at Safari Books Online, and it has a good preview selection at Google Books (these links are not endorsements of any of these sites).
Coursework and Grading: The different tasks to be assigned (all of which fall under the Unviersity category of "Major Scheduled Grading Events") are as follows, together with how they will be weighted for final grades.
    Midterms (2)          25%
    Projects (5-6)        50%
    Final exam            25%
Grades will be assigned based on the following anticipated ranges. It should be noted that these ranges may be expanded based on results obtained during the semester, but they will not be made smaller. The lower and upper parts of each range will be reserved for +/- grades.
      Range      Grade
    90 - 100       A
    80 -  89       B 
    70 -  79       C
    60 -  69       D
     0 -  59       F
Tests: Midterms and the final exam will be administered in class. The lecture schedule gives the anticipated dates. Requests to take tests on alternative days will generally only be granted in the following circumstances: (1) a student has a religious observance falling on the same day that conflicts with the announced test date, or (2) a student is participating in an official University-sponsored activity that conflicts with the announced test date. Any such request must be made at least one week in advance so that alternative arrangements can be made. In case of incapacitating illness on the day of a test, the student must contact his / her instructor as soon as possible, preferably by e-mail on the same day. In this case, the student must produce, within one week of the original test date, a written note from a health-care professional attesting to the nature and severity of the illness. The note must indicate the dates on which the student was incapacitated and a phone number for follow-up verification. When this documentation is provided, alternative arrangements for the test will be made. If no such documentation is produced within the given time frame, a score of 0 will be given on the test.
Projects: The course has a heavy project focus and will involve a substantial amount of programming. Projects are due on the date and time specified when they are assigned; extensions will only be given at the discretion of the instructor. Any request for an extension must be made in advance, and will only be granted if the student has a valid reason for missing a significant portion of the time during the period between the assignment of the project and its due date. Valid reasons include (1) a religious observance, (2) participation in an official University-sanctioned event, and (3) incapacitating illness. Any claims of illness must be supported by documentation from a health-care professional giving the dates of incapacitation and a phone number for follow-up verification.
Academic Integrity: Unless stated otherwise by the instructor, any assignment you turn in for grading must be your own work. In particular, any code you submit as part of a project must have been written by you, and any solutions you prepare for a midterm or final exam must be exclusively of your own devising. Any transgressions of these principles are violations of the campus Code of Academic Integrity and will be handled as such. The webpage of the Student Honor Council contains a detailed explanation of what constitutes academic dishonesty, which includes not only cheating, fabrication, and plagiarism, but also helping other students commit acts of academic dishonesty by allowing them to obtain copies of your work. In short, all submitted work must be your own. For a more extensive list of examples and scenarios, visit the Project Honesty Policy for CMSC 433 page.

Each case of suspected academic dishonesty will be referred to the University's Office of Judicial Programs. If the student is found to be responsible of academic dishonesty, the typical sanction results in a special grade "XF", indicating that the course was failed due to academic dishonesty. More serious instances can result in expulsion from the university. If you have any doubt as to whether a contemplated act of yours might constitute academic dishonesty, please consult one of the course instructors.
Excused Absences: It is the student's responsibility to inform the instructor during the first two weeks of the semester of any intended absences from exams or class for religious observances. Absences related to official University events must be brought to the instructor’s attention at least one week in advance of the absence.
Academic Accommodations: Pursuant to university policy, any student eligible for and requesting reasonable academic accommodations due to a disability is requested to provide his or her instructor with a letter of accommodation from the Office of Disability Support Services (DSS) within the first two weeks of the semester. Note that arrangements for individual exams must be made with the instructor at least one week in advance.




This page last modified on Tuesday, 12-Dec-2017 11:45:24 EST.


Menu Options

Announcements 
Syllabus 
Schedule 
Projects 
Section 0101 Materials 
Section 0201 Materials 
Eclipse/CVS Info 
Grades Server 
Submit Server 
Office Hours 





























Web Accessibility