Usable RTOS-APIs ?
Usable RTOS-APIs ?
复制标题
可用的 RTOS-API ？
DOI：
--
复制
发表时间：
--
期刊：
影响因子：
--
通讯作者：
Wolfgang Schröder
中科院分区：
文献类型：
--
作者：
T. Klaus;Florian Franzmann;Tobias Engelhard;F. Scheler;Wolfgang Schröder
我们认为应用程序编程接口（API）是实时操作系统（RTOS）的一个通常被忽视但非常重要的属性。它不仅是完整的I。例如，提供了实现通用实时系统所需的所有机制，但也易于使用，以防止编程错误并使实时系统更加可靠。遗憾的是，关于可用的RTOS API应该是什么样子的信息很少。因此，本文的目的是提供帮助评估和设计RTOS API。首先，我们概述了我们期望RTOS API提供的概念，并介绍了我们认为API被称为“可用”必须满足的标准。然后，我们研究了广为人知的API规范POSIX和OSEK OS以及RTOS FreeRTOS和Windows Embedded Compact 7 w的API。R. t.这些标准。最后，我们讨论了可能的原因，我们的检查结果，我们推导出一些建议，如何设计RTOS的API。关键词-操作系统，系统软件，实时系统，应用程序编程接口，人机工程学，人为因素
We believe that the Application Programming Interfaces (APIs) is a commonly ignored but very important property of a real-time operating system (RTOS). It should not only be complete i. e., offer all mechanisms needed to implement common real-time systems, but also be easy to use in order to prevent programming errors and make real-time systems more reliable. Sadly there exists only little information about how a usable RTOS API should look like. Therefore this paper aims to give assistance in assessing and designing RTOS APIs. First we give an overview of concepts we expect an RTOS API to offer and introduce criteria we think must be fulfilled for an API to be called ‘usable’. Then we examine the widely known API specifications POSIX and OSEK OS as well as the APIs of the RTOSes FreeRTOS and Windows Embedded Compact 7 w. r. t. to these criteria. Finally we discuss possible reasons for the outcome of our examination and we deduce some advice on how to design RTOS APIs. Keywords—Operating Systems, System software, Real-Time Systems, Application programming interfaces, Ergonomics, Human factors