CS 677 Distributed Operating Systems

Spring 2008

Programming Assignment 2: Spring Break Sale at Pygmy.com

Due: April 3, 2008



The Problem:

Requirements:

  • You need to implement BOTH Part 1 and Part 2.
  • All the requirements of Project 1 still apply to Project 2.

  • B. Evaluation and Measurement

    1. Compute the average response time (query/buy) of your new systems as before.
    2. Design a test to show how the election processes affect the performance.
    3. Design a test to show whether the workload is balanced among the three front end servers.
    4. Design a test to show your totally-ordered multicasting, clock syncronization algorithm really do the work as you expect.
    5. Make necessary plots to support your conclusions.


    C. What you will submit

  • When you have finished implementing the complete assignment as described above, you will submit your solution in the form of printouts.

  • Each program must work correctly and be documented. You should hand in:
    1. A copy of the output generated by running your program. When it receives a book, have your program print a message "bought book book_name ". When a client issues a query (lookup/search), the election begins, the election is done, or a coupon is issued/used, having your program print the returned results in a nicely formatted manner.
    2. A seperate (typed) document of approximately two pages describing the overall program design, a description of "how it works", and design tradeoffs considered and made. Also describe possible improvements and extensions to your program (and sketch how they might be made).
    3. A program listing containing in-line documentation.
    4. A seperate description of the tests you ran on your program to convince yourself that it is indeed correct. Also describe any cases for which your program is known not to work correctly.
    5. Performance results.
    6. A readme file about how to run your code on EDLAB machines.
    7. After you turn in all the stuff mentioned above, please also send TA an email telling the location of your files .
  • Let us not waste a lot of trees. So, if any of the above turn out to be large, just save the relevant information in a file, leave it on your EDLAB account and submit the name of the file.

  • D. Grading policy for all programming assignments

    1. Program Listing
        works correctly ------------- 50%
        in-line documentation -------- 15%
    2. Design Document
        quality of design ------------ 15%
        understandability of doc ------- 10%
    3. Thoroughness of test cases ---------- 10%
    4. Grades for late programs will be lowered 12 points per day late.