Difference between revisions of "Software-in-the-Loop Testing (glossary)"
Jump to navigation
Jump to search
m (Text replacement - "<center>'''SEBoK v. 2.0, released 1 June 2019'''</center>" to "<center>'''SEBoK v. 2.1, released 31 October 2019'''</center>") |
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023") |
||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
| − | <center>'''SEBoK v. 2. | + | <center>'''SEBoK v. 2.9, released 20 November 2023'''</center> |
Latest revision as of 23:56, 18 November 2023
In software-in-the-loop testing, the actual Production Software Code is incorporated into the mathematical simulation that contains the models of the Physical System. This is done to permit inclusion of software functionality for which no model(s) exists, or to enable faster simulation times. (Argonne National Lab 2012)
Sources
Argonne Naltional Lab. 2012. Model based design definition of terms. Available at http://www.autonomie.net/references/model_based_design_defs_24c.html.
Discussion
This is one of three related techniques: model-in-the-loop, software-in-the-loop, and hardware-in-the-loop.