2007
DOI: 10.1016/j.csi.2006.07.002
|View full text |Cite
|
Sign up to set email alerts
|

An interface test model for hardware-dependent software and embedded OS API of the embedded system

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0

Year Published

2008
2008
2014
2014

Publication Types

Select...
5
2

Relationship

3
4

Authors

Journals

citations
Cited by 18 publications
(12 citation statements)
references
References 3 publications
0
12
0
Order By: Relevance
“…An embedded system's Interface Test Model (emITM) with respect to both the kernel interface and the hardware interface has already been developed by us as part of our prior work [21]. Our emITM provides a set of test requirements based on the kernel and hardware interfaces.…”
Section: The Proposed Mutation Operatorsmentioning
confidence: 99%
See 1 more Smart Citation
“…An embedded system's Interface Test Model (emITM) with respect to both the kernel interface and the hardware interface has already been developed by us as part of our prior work [21]. Our emITM provides a set of test requirements based on the kernel and hardware interfaces.…”
Section: The Proposed Mutation Operatorsmentioning
confidence: 99%
“…The global variables in this software gain control over the physical hardware devices and are usually declared in a system configuration file. All the hardware IO devices are directly controlled by writing/reading the values to/from the RAM or registers [21]. In this case, the hardware interfaces are global variables declared in the system configuration file.…”
Section: Kernel-based Software For Hardware Layermentioning
confidence: 99%
“…Embedded software testing has been studied in the last few years and a number of approaches can be found [17][18][19][20][21][22][23][24]. Some dynamic testing strategies are proposed for specific platforms [17][18][19][20]24].…”
Section: Static Analysis and Related Workmentioning
confidence: 99%
“…Sung et al [36] test interfaces to the kernel via the kernel API and global variables that are visible in the application layer. The methodology we present, in contrast, is a white-box approach, analyzing code in both the application and kernel layers to determine testing requirements.…”
Section: Related Workmentioning
confidence: 99%