Course Description

This course will study the fundamental aspects of modern distributed systems. Issues concerned with distributed systems such as transparency, communication, resource sharing, fault tolerance, scalability, consistency, and security as well as those concerned with designing, developing, and managing distributed applications and services will be covered in this course.

Instructor:

Prof. Won-Ki Hong (PIRL 216) : 279-2244, jwkhong_at_postech.ac.kr

Lectures:

Mon. & Wed. 13:15-14:30 (PIRL 222)

Pre-requisites:

A course on computer networks and operating system is required. If a student did not take these courses but wishes to take the course, the student may be admitted under the discretion of the instructor.

Required Text:

• Andrew S. Tanenbaum and Maarten van Steen, Distributed Systems: Principles and Paradigms, Prentice-Hall, ISBN ISBN 0-13-088893-1, 2002.

Recommended References:

• G. Coulouris, J. Dollimore and T. Kindberg, Distributed Systems: Concepts and Design, 4th Edition, Addison-Wesley, ISBN 0321263545, 2005.
• John Bloomer, Power Programming with RPC, O'Reilly & Associates,Inc., Sebastopol, CA, ISBN 0-937175-77-3, 1992.
• Jon Siegel, CORBA Fundamentals and Programming, Wiley, New York, ISBN 0-471-12148-7, 1996.
• David Reilly and Michael Reilly, Java Network Programming and Distributed Computing, Addison Wesley, ISBN 0-201-71037-4, 2002.
• A. S. Tanenbaum, Computer Networks, 3rd edition, Prentice-Hall, 1996.
• S. J. Leffler, M. K. McKusick, M. J. Karels and J. S. Quaterman, The Design and Implementation of the 4.3BSD UNIX Operating System, Addison-Wesley, Reading MA, ISBN 0-201-06196-1, 1989.

Course Evaluation:

• Term Project: 50%
  
• Assignments: 30%
  
• Quizzes: 15% (Quiz1 Soluition, Quiz2 Soluition)
  
• Class Participation: 5%
  Note: the above evaluation scheme may change slightly during the course.

Term Project:

There will be a single major group term project (worth 50% of the final mark). It will involve developing a non-trivial distributed system using the techniques learned in this course. The project can be done in groups of two or four and is expected to start from the beginning of the course and finish towards the end of the course. It also involves generating a number of documents (including requirements, design, implementation, system and testing), oral presentations and demos. More detailed description and the schedule on the project will be available during the course.
1. Team Formation and Project Proposal
2. Term Project Schedule
   • Requirement Analysis (Deliverable: Requirements Document) - due Sept. 25
   • High-Level Design (Deliverable: High-Level Design Document) - due Oct. 16
   • Detail Design (Deliverable: Detail Design Document) - due Nov. 13
   • Implementation, Testing and Integration (Deliverable: Implementation Document) - due Dec. 4
   • Demo (Deliverable: User guide, Installation guide) - due Dec. 11
   Note that the deliverables and due dates may change as the course progresses.
   
   
3. Term Project Team Homepages
   • PK Team
   • MEDIC Team
   • Ubi Team

Assignments:

There will be several assignments (worth 30% of the final mark). Programming assignments will be done using C, C++, or Java.
• Assignment 1 (1%)
• Assignment 2 (due Sept. 20 - 5%)
• Assignment 3 (due Oct. 9 - 6%)
• Assignment 4 (due Oct. 30 - 6%)
• Assignment 5 (due Nov. 22 - 12%)
1. Semantics Web - Ȳ¹Î°æ
2. Peer-to-Peer Algorithms and Systems - ¹Úº´Ã¶
3. Autonomic Computing - °­Áظí
4. Web Services - ¹Úâ±Ù
5. Large-Scale Sensor Networks - Á¤±¤º»
6. Location-based Services - ¿ø¿µÁØ
7. Distributed File Systems - ¹Ú¿ì¶÷

Late assignments may be handed in, but there will be a penalty of 20% of the mark for assignments turned in less than one day late, and an additional penalty of 10% for each day thereafter.

Quizzes:

There will be two or three in-class quizzes (worth 20% of the final mark) during the course of the term. There will NOT be a midterm or final exam for this course.

Class Participation:

Students are strongly encouraged to attend all lectures and to participate in discussions during lectures. Up to 5% of the final mark will be given for good class participation.

Cheating Policy:

Cheating will not be tolerated in this course. Students are encouraged discuss things related to courses and assignments but the materials handed in for individual assignments must be his/her own. The maximum penalty for each offense is -100% for the assignment in question. Please click here for the departmental policy on cheating.

Computer Accounts:

You should all have an AFS account. If you do not have one yet, you should get one right away since it will be used extensively for accessing course-related materials and submitting assignments.

Using the BBS:

A BBS has been set up for course use. You can read and post articles to this BBS. In this BBS you will find changes to the lecture schedule, clarifications to the assignments, etc. It is your responsibility to read this newsgroup on a daily basis. There is likely to be little information at the beginning, but more as the course progresses.

Lecture Notes

• Introduction to Distributed Systems
• Useful Process Structures
• Communication
  1. IPC in UNIX
  2. Remote Procedure Call (RPC)
  3. Sun RPC
  4. Distributed Computing Environment (DCE)
  5. Remote Object & Method Invocation
  6. Message-Oriented Communication
  7. Stream-Oriented Communication
  8. CORBA
• Processes & Threads
• Naming
• Synchronization
• Consistency and Replication