CS 5113 and 4113 Fall 21

Logo

This is the web page for Fall 2021 Distributed Operation Systems at the University of Oklahoma.

View the Project on GitHub oudalab/cs5113fa22

Final Presentation

C S 4/5113 Distributed OS

Operating Systems Theory (Fall 2022)

Goals of the final

In this semester, we have discussed an array of distributed operating systems concepts. It is your job in this final assignment to showcase the knowledge you have gained. Your final report will consist of

You should submit your GitHub link, but this must only be in addition to the source files.

Project Specific Parameters

All students will generate a unique number of Pokemon and Trainers. Students in the cs4113 class have a minimum board of size 10x10 (N=10). Students in the cs5113 class have a minimum board of size 20x20 (N=20). The number of pokemon and trainers will be equal and should correlate to the letter number of the paper you presented (P = T). The formula for selecting the number of pokemon and trainers is:

total = 10 + num(paperid) + len(letters in firstname)

where, num(paperid) is the paper number associated with your paperid. If you presented paper E, num(E) = 5 because E is the fifth letter of the English alphabet. Also, len(letter in firstname) is the number of letters in your first name.

Important Dates

You may submit the final report as soon as the dropbox is opened. The last time to submit the final project contents is before the final exam period, Wednesday 12/14 from 1:30.

What to submit

Submit a 5-minute video informercial describing your work. The video has a strict structure that must be followed. Please label or overlay your discussion of each required component. If a component is missing or incomplete, you will not receive credit.

Check out some videos from Fall 2020 and Fall 2021.

The components of the video include:

  1. A Title. Including your name and contact information.
  2. Description of the project. Describe the goals of the project and your primary focus.
  3. DS problem #1 Explicitly describe and cite the distributed system problem. Note that problems here refer to issues that you had to resolve, such as threading issues, and no properties of distributed systems such as networking. You may cite the textbook, the original source readings, or any other authoritative source.
  4. DS problem #2 See above.
  5. DS problem #3 – A third is required if you are in the graduate section of the course.
  6. Demonstration. Show the logs of a complete run of your code. Describe what is happening. If the run takes too long to run you can fast-forward the video.

The video must fit within 5 minutes and 59 seconds window. You must upload the video link to Gradescope. Note, the file may be too big to upload, if so, please work with the TA to ensure a good version is uploaded.

You must submit all source code to Gradescope. You must also submit a README file describing the contents of the video and your codebase. Your COLLABORATORS file should include all resources. Each source code file must be submitted as an individual upload.

Rubric

  Percentage
Infomercial 35%
README 35%
Source Code 25%
COLLABORATION file 5%
Total 100%

The video will be evaluated based on the above requirements. We expect the information to be made well, within time, be clear, convey all necessary information, and visually appealing. The README file will be scored based on how descriptive you are of the accomplishments and the organization of the code base, testing methods, etc. Besure to create a detailed discription of how you tested the distributed systems aspects of the code. The source code will be graded based on clarity, commenting, and correctness. The COLLABORATION file will be scored based on its presence and completeness. The content above are expected to be thorough and complete.


Back to CS 5113