CSE 5306 Distributed Systems (Spring 2015)
Midterm exam: 3:30PM-5:00PM on March 19, 2015 @ PKH 204 (both sections) Midterm Exam Topics
Final exam: 3:30PM-5:00PM on May 7, 2015 @ PKH 204 (both sections) Final Exam Topics
|Dr. Donggang Liu
Office: ERB 555
Office hours: Tuesdays & Thursdays 12:30PM - 2:00PM
Voice: 817-272-0741; Fax: 817-272-3784
Email: dliu (at) uta (dot) edu
Section 1: Ahmed rumee, Sarker T (firstname.lastname@example.org)
Section 4: Harshavardha N. Gorla (email@example.com)
Class Time and Location:
Section 1: TuTh 11:00AM - 12:20PM (ERB 129)
Section 4: TuTh 3:30PM - 4:50PM (COBA 252)
- Distributed Systems: Principles and Paradigms (2nd Edition), Andrew S. Tanenbaum and Maarten Van Steen.
- CSE 3320: Operating Systems
- CSE 4344: Computer Networks
Hardware and software issues in
modern distributed systems. Topics may include distributed
architecture, naming, synchronization, consistency and replication,
fault tolerance, security, and distributed file systems. Examples from
current popular distributed systems such as peer-to-peer (P2P) systems
will be analyzed.
From this class the student will
gain enough understanding of distributed operating systems, be able to
explain the principles underlying the functioning of distributed
systems as well as how these principles are applied in distributed
systems and what the problems and challenges are. The student will
understand and estimate the impact of different design choices, system
features on distributed systems
- Pop quiz (10%)
- Projects (30%)
- Midterm exam (30%)
- Final exam (30%)
Note on Assignments:
- Introduction: pdf
- Architectures: pdf
- Processes: pdf
- Consistency and Replication:pdf
- Fault Tolerance:pdf
- Distributed File Systems:pdf
Assignments and Lab Exercises:
- You must use text editor (e.g. MS Word) to complete your homework.
- Handwritten submissions are not acceptable.
- Project assignement: Section 1, Section 4
- Template for design document template
- Presentation schedule schedule
- Final project deadline: April 30, 2014 @ 11:59PM
- Send your source code and the final documents to TA
- Schedule your demo time with TA
- Course Policies:
- Assignment and project deadlines will be firm.
- Late assignments will be accepted with a 10% reduction in
grade for each day they are late by.
- All assignments must be turned in before the start of class
on the due date.
- Students are responsible for checking this web site
frequently for course related material and announcements. This
site will be the primary form of communication for the course
unless otherwise specified.
- Please include "CSE 5306" in the Subject line of all e-mail correspondence.
- No make up exams or assignments will be given.
- You may select any language/system to implement your
labs. In general, there will be more support for C/C++/VB and
Microsoft's Visual Studio environments.
- All exams are closed book.
- The instructor reserves the right to modify the policies, calendar, assignments, point values and due dates.
- Faculty are required by law to provide "reasonable
accommodation" to students with disabilities, so as not to
discriminate because of that disability. Student responsibility
primarily rests with informing faculty at the beginning of the
semester and in providing authorized documentation through
designated administrative channels.
- Taping of lectures:
You may tape the lectures if you wish. Students who's native
language is not English are strongly encouraged to tape the
lectures. Much of the material in this course will be new to many
of you and being able to review my comments will help pinpoint the
important issues in the book.
- Text book:
Because the department cannot endorse violations of copyright law,
you may not bring to class a photocopy of the text book. This also
will apply if any exams are open book. What you do outside class
is your own affair. If you choose to violate the laws then you
will have to pay any penalties if you are caught. This might
include action by the University if they became aware of the
matter. International editions of the text are fine.
- Academic Dishonesty:
It is the philosophy of The University of Texas at Arlington that
academic dishonesty is completely unacceptable and will not be
tolerated. Anyone involved in academic dishonesty will be
disciplined in accordance with University regulations and
procedures, possibly including suspension or expulsion from the
University. "Scholastic dishonesty includes but is not limited to
cheating, plagiarism, collusion, the submission for credit of any
work or materials that are attributable in whole or in part to
another person, taking an examination for another person, any act
designed to give unfair advantage to a student or the attempt to
commit such acts." See:
www-ais2.uta.edu/policy/hop2/2-200.shtml. Read section 2-202.A.6.
- All student labs may be automatically compared with other student labs for similarity:
A high level of similarity will result in a penalty for all
students involved since we have no way of knowing who originated
code that is copied. It is generally permissible for you to use
code from the www or from text books. If you use code from such
sources then you should include in your program comments and
write-up a reference to the material. This will be the only
exception to the assumption of collusion/plagiarism. In this class
we will have no tolerance for cheating. At a minimum it will
result in a grade of -100 on the test or assignment. A grade of
zero is no punishment for wrongdoing since a grade of zero is what
you would receive for doing nothing at all. In order to ensure
fairness to all students, exams will be proctored and possibly
- Other Suggestions:
- We will be using the Tanenbaum 2ED text. The PowerPoint
slides are on my web site. I suggest you download these slides and
print them, preferably 3-6 slides per page. Then you can follow the
lectures without having to write so much.