Summary of the course

This course provides an introduction to distributed systems, primarily through a focus on the design and development of software that transmits information across networks. Topics will include some but, perhaps, not all of the following: the architecture of distributed systems; networking; synchronous and asynchronous protocols network programming; remote procedure calls; threading and shared memory concurrency; cryptography and security.

Textbooks and printed resources

Java Network Programming (4th edition), E. R. Harold. O'Reilly & Associates, 2013, Print ISBN: 978-1449357672.

The textbook is not required and no reading assignments will be given from it. It is a useful resource for learning the programming techniques in which you must develop basic proficiency in order to pass this course.

Prerequisites

CSC 301, 383, or CSC 393; and CSC 374

Office Hours

I will be in my office, CDM 838, during the following days/times:

• M 1:00pm - 3:00pm
• T 3:15pm - 4:00pm
• W 9:00am - 10:00am
• Th 3:15pm - 4:00pm

Exercises and Grading

Overview

This course focuses on the implementation of distributed systems using a system level library in Java. Several programming exercises will be provided to reinforce learning. Additionally, homework problems covering various aspects of networking and related topics will also be provided. Your understanding of the material will be tested through a Midterm and a Final exam. Further details will be posted on the class website, which is on Desire2Learn (D2L).

Sec. 1. Programming Exercises

• Each programming exercise is designed to develop proficiency in performing system level tasks. You should complete each program individually in order to maximize your benefit, although you are free to work with others.
• Executable scripts and test files that are used to assess the performance of your code will also be provided. As you develop your code, you should use the scripts and test files to determine how well your code is performing the specified tasks.
• Although I will not grade your programming exercises, I will use them to devise questions for the exams.

Sec. 2. Homework Problems

• There will be two to four short homework problem sets, consisting mainly of problems involving protocols and infrastructure.
• You should complete these problems individually in order to maximize your benefit; however, you may discuss the problems with your classmates.
• I will also supply you with the answers to the homework problems. You may look at the answers if you are stuck; otherwise, I would recommend reviewing them after you complete the problems in order to determine how well you performed. The answers will also be helpful in correcting any misunderstandings or gaps in your knowledge.
• Although I will not grade your homework problems, I will use them to devise questions for the exams.

Sec. 3. Midterm Exam

• The exam will consist of questions drawn from the textbook, the lectures, the programming exercises, and the homework problems.

Sec. 4. Final Exam

• The Final exam is comprehensive; therefore, it will consist of questions drawn from the textbook, the lectures, all programming exercises, and all homework problems.

Sec. 5. Substitution of Final Project for Final Exam

• A Final Project may be submitted in lieu of taking the Final Exam.
• The Final Project may be completed alone or by a group composed of no more than three (3) students.
• The purpose of the project is the creation of a simple distributed system using system level libraries. Sample projects will be discussed in class.
• A written project specification must be submitted to and approved by the instructor as the first step in substituting a Final Project for the Final Exam.
• The project proposal must include at least four (4) significant functions beyond setting up connectivity between clients and servers.
• The source code for the project must be written in Java.
• The source code must be maintained in a public repository using Git or Mercurial.
• An Ant file that creates a final submission build must also be included in the repository.
• Additionally, the project must include documentation about the architecture of the system and the classes in the project, as well as the build and test processes.
• Each participant in a final project must contribute at least two hundred (200) source lines of code, all of which must originate this quarter.
• If more than one person has participated in the project, each participant must also submit a list of credits, indicating precisely what source code contributions each person made to the project.
• The final submission must build and execute in order to score any points.
• The Final Project will be presented to the class on the day of the Final Exam.
• In lieu of a grade for the Final Exam, the grade for the Final Project will be assigned as follows:
  • 98 -- all functionality implemented as specified
  • 85 -- the majority of the significant functionality implemented as specified
  • 72 -- at least one-third of the significant functionality implemented as specified
  • 60 -- at least one significant function implemented as specified
  • 30 -- the minimum amount of code was submitted, the project builds and executes, but no significant functionality was implemented as specified
• In order to clarify which functionality is significant for purposes of grading, the project specification must categorize all specified functionality as either significant or optional. This categorization must be approved by the instructor as part of the specification approval process.

Earning Extra Points

You may earn extra credit points by completing a Final Project in addition to taking the Final Exam. The extra points are added to your final grade for the course as follows:

• 10 -- all functionality implemented as specified
• 6 -- the majority of the significant functionality implemented as specified
• 3 -- at least one-third of the significant functionality implemented as specified
• 1 -- at least one significant function implemented as specified
• 0 -- no significant functionality implemented as specified

How Your Grade for the Course Is Calculated

Your final grade for the course is simply the average of your Midterm and Final exams, plus any extra credit points earned.

I will not curve the course grades; therefore, you must earn at least an average of 70% in order to pass the course.

Alternative grade procedure for Midterm and Final exams: If you have a documented disability, such as a history of extreme test taking anxiety, please see me for accommodation.

Policy on Working Together

Each student is expected to turn in original code for the Final Project. Copying code from another person is considered a serious violation of the university's academic integrity policy (see below).

Course Schedule

The schedule of topics will be determined later and posted on the class website, which is on Desire2Learn (D2L).

Attendance

Although attendance is encouraged in order to foster participation, it is not mandatory.

Academic Integrity and Plagiarism

This course will be subject to the university's academic integrity policy. More information can be found at http://academicintegrity.depaul.edu/. If you have any questions be sure to consult with your professor.

Academic Policies

All students are required to manage their class schedules each term in accordance with the deadlines for enrolling and withdrawing as indicated in the University Academic Calendar. Information on enrollment, withdrawal, grading and incompletes can be found at: http://cdm.depaul.edu/enrollment.

Students with Disabilities

Students who feel they may need an accommodation based on the impact of a disability should contact the instructor privately to discuss their specific needs. All discussions will remain confidential. To ensure that you receive the most appropriate accommodation based on your needs, contact the instructor as early as possible in the quarter (preferably within the first week of class), and make sure that you have contacted the Center for Students with Disabilities (CSD) at: csd@depaul.edu.
Lewis Center 1420, 25 East Jackson Blvd.
Phone number: (312)362-8002
Fax: (312)362-6544
TTY: (773)325.7296

Online Course Evaluations

Evaluations are a way for students to provide valuable feedback regarding their instructor and the course. Detailed feedback will enable the instructor to continuously tailor teaching methods and course content to meet the learning goals of the course and the academic needs of the students. They are a requirement of the course and are key to continue to provide you with the highest quality of teaching. The evaluations are anonymous; the instructor and administration do not track who entered what responses. A program is used to check if the student completed the evaluations, but the evaluation is completely separate from the student’s identity. Since 100% participation is our goal, students are sent periodic reminders over three weeks. Students do not receive reminders once they complete the evaluation. Students complete the evaluation online in CampusConnect.

Changes to Syllabus

This syllabus is subject to change as necessary during the quarter. If a change occurs, it will be thoroughly addressed during class, posted under Announcements in D2L and sent via email.

School Policies

Policies of the school are explained on the webpage for this course on my.cdm.depaul.edu.