如何说明中断驱动的过程？ [英] 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屋！