如何说明一个中断驱动的过程? [英] How to illustrate an interrupt-driven process?

问题描述

This question is related to diagraming a software process. As an electrical engineer, much of the software I do is for embedded micro-controllers. In school, we learned to illustrate our algorithm using a flowchart. However, nowadays, many of my embedded projects are heavily interrupt-driven where the main process runs some basic algorithm a variety of interrupt sources provide its stimulus. So, my question is, what are some diagramming techniques that I can use to illustrate my process such that future developers can understand what I am doing easily and get involved in development?

Here are some key features that I am looking for:

• Shows data structures and how data is passed between processes & interrupts
• Shows conditions that cause each interrupt
• Shows how data is gathered and passed through a downlink
• Shows how command messages are received, parsed, and executed
• Ideally is well suited for hierarchical breakdown into smaller processes with greater levels of detail

解决方案

There are many of interesting approaches you can find in diagram drawing. I will post a few here. You will find a lot of Operation System and Architecture scpecific names in there such as register , event, function names and etc. It is more for representation so far, right? So he we are.

这篇关于如何说明一个中断驱动的过程?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！