Assignment

• Each process will include some information about its resource requests/needs/allocations, as needed to implement deadlock avoidance.

• You program (simulated OS) will need to keep track of all the resources, in connection with information kept at each process.

• You also need to simulate some resource request/(allocation)/use/release sequences in coordination with your processes and your simulated OS. To do this, you might need to implement a simulated clock.

• Some standard test cases will be posted close to the project due date so that you can test you program before the demo and handing in the deliverables.

• Design considerations and utility programs to report the status are similar to Part I of your project.

What to turn in:

• The program code (written in your favorite language).
• Some execution trace.
• Documentation on how to install (compile/link) your program on SEAS/UNIX machines or on PC running Windows OS.
• All the above three parts, as well as overall code/design clarity and documentation, will be considered in grading your project.
• A demo need to be scheduled with your grader Sudipti Mishra. A sign up sheed will be passed out in early April.

Due date:

• On-campus and TAGER/Green-network students: 4/10/03.
• Video students: 4/21/03.