Want this question answered?
Yes, it is one of many scheduling algorithms suitable for time sharing.However it is not suitable for scheduling in a hard realtime OS that must consistently meet deadlines.
Compatible Time-Sharing System was created in 1961.
Universal Time-Sharing System was created in 1966.
the block diagram of time sharing system in o.s
A single user OS could also be a real-time system. The differences in the two are based on how a process is given control or priority within the system. Realtime systems give preferences to realtime control processes (realtime runs at a much higher priority level). Most single-user operating systems treat processes with equal priority unless you indicate that a certain process is to receive preferential treatment. This can be done by raising the priority of the user process to that of realtime, meaning it will receive resources (such as CPU cycles) above other programs in the system.
The main difference between batch sharing and time sharing is that in batch sharing system tasks are processed in order in which they arrive. Whereas, in the later the system switches between tasks.
One example of a time-sharing system is the bank's bankcard system, which allows hundreds of people to access the same program on the mainframe at the same time. The Multics & Unix operating systems are time sharing Operating Systems
time sharing operating system is user interactive, but multiprogramming operating system need not be user interactive
A complete answer to this question is beyond the scope of this website, as it requires several years of college courses and about twice that in on the job experience to properly learn. However it is basically an extension of standard systems analysis and design (which is still at least 2 full college courses) with a large amount of tedious bookkeeping added to make certain that all realtime requirements are fully met.Another point that is vital to understand is whether this is a hard realtime system or a soft realtime system. Hard realtime systems are much more difficult, as failure to meet even one of the real time requirements means total failure of the system to fulfill its purpose, making it useless. Soft realtime systems on the other hand are permitted to occasionally miss deadlines or otherwise fail to consistently meet some of the realtime requirements, as long as it is able to catchup later and meet the realtime requirements on the average.
There are several advantages and disadvantages of having a real time operating system. One disadvantage is unseen errors, an advantage is timing.
response time would be
A hard real-time system guarantees that critical tasks complete on time. This goal requires that all delays in the system be bounded from the retrieval of the stored data to the time that it takes the operating system to finish any request made of it. A soft real time system where a critical real-time task gets priority over other tasks and retains that priority until it completes. As in hard real time systems kernel delays need to be bounded