1 / 9

CSE 762 “Advanced Operating Systems Laboratory’’

This lab focuses on constructing advanced operating system components, such as internet, client-server, remote file server, distributed namespace, and user interface software. It covers web services, XML, SOAP, WSDL, UDDI, Jax-RPC, and requires project proposals, progress reports, and final demos/written documentation. Teamwork and distributed algorithms are emphasized.

epippen
Download Presentation

CSE 762 “Advanced Operating Systems Laboratory’’

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CSE 762 “Advanced Operating Systems Laboratory’’ Gagan Agrawal

  2. Outline • CSE 762 / Background / New Format • Capstone criteria • Issues • Caveats: • Haven’t seen student final project demos • Haven’t seen teaching evals • I need to leave at 12:50 

  3. Background • Operating systems sequence • CSE 660 – Basics of operating systems • CSE 662 - Implementation of basic uniprocessor OS modules • CSE 760 - Concurrency / Distributed algorithms • CSE 762 - ``advanced operating system laboratory - capstone class • 25 word description: Construction of advanced operating system components: internet, client-server, remote file server, distributed namespace, user interface software.

  4. 762 • Old Format • Focus on operating system shell implementation and sockets programming • Well defined labs • Capstone requirements • Open-ended design projects • Technology Trends • Middleware replacing ``distributed operating systems’’ • Revision discussed last spring (OS course report)

  5. New Format • Web-services as the implementation vehicle • Open-ended distributed software design projects • Team work • More independent work • Define projects • Learn details of underlying technologies somewhat independently • Project details: • Distributed software with web-services, including a non-trivial client • Must have a significant distributed algorithm

  6. Detailed Outline • First 3 weeks: • Web-services, XML, SOAP, WSDL, UDDI, Jax-RPC • Weeks 4-5 • Student project proposals • Weeks 6-10 • Project progress report and discussions • Final: • Final project demo and write-up

  7. Projects • A distributed production/sales management software for a manufacturing company (distributed mutual exclusion) • A bank with a replicated database (voting protocols) • A bank with distributed database (commit protocols) • A war game with potentially malicious generals (byzantine generals) • A web-based file sharing system

  8. Capstone Criteria • No. 1: Senior level class • No. 2: Prereqs: 601 and 662 (and others by transitivity) • No. 3: Design decisions everywhere (even the project definition) • No. 4: Web-service standards are used • No. 5: Written documentation is a requirement • No. 6: Several oral presentations from each team • No. 7: All work in teams • No. 8: 30 official cap, only 14 this time

  9. Issues • Started with 8 UGs, ~20 Grads, finally, 6 UGs, 8 Grads • Need to advertise the class better to UGs • Prereq not changed while revising the class: • 662 not needed, but students need to have advanced systems programming background • 662/621/677 or permission of instructor ? • Could attract more UGs • 3 credits currently, should it be 4 credits ? • Was it too open ended (have 1 well-defined lab before the open project ?)

More Related