Originally Posted by flyingnewbie10
I am no specialist,
Yes, we have noticed. And then please don't try to apply your knowledge from a completely different domain.
but where you read IRQ please read it as any circuit that handles asynchronous I/O, meaning that processing of I/O signals is not synchronized with all the FADEC scheduled processes , but rather is done through interrupts that call a specific function only when an I/O is performed, be it a small controler in a PC or a more complex device in a mainframe.
No asynchonous I/O on safety-critical real-time systems.
No multitasking/threading, either.
Avionics hardware bears no resemblance to either PCs or Mainframes.
Don't think Avionics software development is anything like "normal" software development, or that the structures are even remotely similar.
And don't assume avionics software developers are stupid enough to use async I/O or something as utterly useless (because essentially unverifiable) as pre-emptive multitasking. It is not done.
Please, before you try to apply your knowledge of how business/office software is "created" to the development processes of real-time safety critical system, learn something about the methods and techniques involved. Your skills and experience simply don't apply here.
No offence intended, but avionics software engineers know this stuff. You obviously don't even know the basics of real-time systems.