DMCA
Interface module specifications for real-time systems
| Venue: | in Newfoundland Electrical and Computer Engineering Conference (NECEC), IEEE, Newfoundland and Labrador Section, Nov. 2001. - 714 |
| Citations: | 1 - 1 self |
BibTeX
@INPROCEEDINGS{Wang_interfacemodule,
author = {Yingzi Wang and Dennis K. Peters},
title = {Interface module specifications for real-time systems},
booktitle = {in Newfoundland Electrical and Computer Engineering Conference (NECEC), IEEE, Newfoundland and Labrador Section, Nov. 2001. - 714},
year = {}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
Documentation plays a key role as a component of design process, and a preview of a task before it comes to be executed. A well-specified task might not take less implementation time than one without documents, but one of the obvious advantages is that misunderstandings are avoided and readable specification makes it easy for the successive developers to exploit or modify the software or hardware design. Such merit is particularly useful for aviation and military applications in which reliability and maintainability are very important aspects for judging the success of a project. Interface Modules (IM) are modules that encapsulate input or output device hardware and the related software, so that the application software can be written without specific knowledge of the particular devices used. Replacing or modifying an interface device will only lead to changes in the IM, rather than changing the other modules in the whole system. In real-time and embedded systems, an IM will often relate real-valued external quantities (e.g., time, positions in space) with discrete valued software quantities. An IM specification must therefore use a combination of notations and formalisms. This paper presents a suitable method for IM specification, which is both precise and readable. 1
Keyphrases
interface module specification real-time system im specification readable specification real-valued external quantity military application particular device implementation time hardware design design process application software whole system key role specific knowledge software quantity obvious advantage successive developer suitable method important aspect well-specified task interface device output device hardware interface module embedded system related software
