Hello group!

As my final project, I'm supposed to design and implement a
demonstration program for my professor that shows how a database
scheduler works. It's up to me to come up with an idea of how such a GUI
could look like.

I have been thinking about how to visualize the concurrency control, how
the actions are interleaved with each other or the likes. I have started
out understanding the theory, however after days, I still can't come up
with an adequate idea of how such a program could work and look like.
Since it's for demonstration purposes only, the size and scope of the
program will be somewhat limited.

A feature that is mandatory, is to be able to produce and view wrong
schedules, along with their consequences for the data... Well, that's
the theory so far. But how could the GUI look like and how are the
interactions performed?

I'd really appreciate if some of you could make some suggestions of how
such a program (GUI) could look like. I'm in need of a brainstorming
here. Any chunks of ideas could be helpful...

Thanks for helping!

Karsten

PS: Recovery is not an issue in this demo program.

Hi,

Karsten Wutzke <kwutzke-blahblah (AT) starconcept (DOT) de> wrote

What exactly do you mean by a database scheduler? How does it work?

Seun