How to illustrate interrupt driven process?

Question

This question is related to a software process diagram. As an electrical engineer, most of the software I do is for embedded microcontrollers. At school, we learned how to illustrate our algorithm using a flowchart. However, at present, many of my built-in projects are severely interrupted when the main process runs some basic algorithm, and many interrupt sources provide its incentive. So, to my question: what diagram methods can I use to illustrate my process so that future developers can understand what I am doing easily and participate in the development?

Here are some key features I'm looking for:

• Shows data structures and how data is transferred between processes and interrupts.
• Shows the conditions that trigger each interrupt.
• Shows how data is collected and transmitted in a downlink
• Shows how command messages are received, analyzed, and executed.
• Ideal for hierarchical breakdown into smaller processes with a high level of detail

Answer 1

There are many interesting approaches that you can find in a graphic drawing. I will post a few here. You will find many names of system functions and architecture, such as names of registers, events, functions, etc. This is more for presentation so far, right? So is he and we.

Answer 2

:

:

, .

---

,

Answer 3

UML . ( ). , , ( ). , . , , , . .

The main thing is that UML supports many different representations (static, dynamic, logical, deployments) in your system. Do not try to express everything at once.

The diagram below shows an example of a process interruption.