Vead,
If the comments above are OK for you then good. However, I feel your question is looking for something more basic, so I will give a more basic story.
With the operation of a digital computer, there are many tasks and functions performed, and these tasks will, or maybe, operate at different speeds. For example, to add two numbers together may take say 10 microseconds, but to print the answer may take say 10 seconds on a slow printer. So what does the computer do while the printer is printing. This kind of speed difference between the fastest device in the system and the slowest device in the network needs to be considered in the design of the computer hardware and the software that drives the program. This is what the 'interrupt' system does.
The computer will at some point in the program it is executing, will have cause to stop calculating because it needs some information or it needs to wait for something to happen. What will be done is for the program to instruct the hardware (for example a clock), and the program will tell the clock to start timing. Then, the program will "set a flag", and then will go back to the point in the program where it left off. If there is nothing for the computer to do, the computer will go into a 'wait state', and will wait for the clock to finish its timing sequence. When the clock has timed out, the flag will tell the control unit that the time interval has completed, and the computer will then go and do what it has to do ( for example read a voltmeter reading). However, if the computer has some unfinished task when the clock is timing, then the program design will cause the computer to go back to its task of say calculating a result while waiting for the clock to finish.
Interrupts can be quite complex in that they can be assigned different priority levels, and one interrupt can interrupt another interrupt of a lower priority. It is also possible in the hardware design of the interrupt structure, for the interrupt system to be turned off under software control.
Generally for small systems, use of the interrupt system is not really useful, but where a system is dealing with lots of relatively slow I/O hardware and has lots of calculations to do, then use of the interrupt system can significantly improve the speed of getting the job done.
In one system I had to work with, the I/O consisted of a slow character printer, a capacitance bridge measuring capacitances of devices connected to the bridge through a switching matrix and doing calculations and statistical analysis of the measured results. This system used the interrupt system to drastically speed up the testing time. The computer memory was only 4K words and results could not be stored because of the memory capacity of the computer; results had to be printed as soon as they were calculated.
Sorry if this is too basic; but your question I thought was at this level.