Difference between revisions of "Software-in-the-Loop Testing (glossary)"
| Line 2: | Line 2: | ||
====Source(s)==== | ====Source(s)==== | ||
| − | Argonne Naltional Lab. 2012. ''Model based design definition of terms | + | Argonne Naltional Lab. 2012. ''Model based design definition of terms''. Available at [http://www.autonomie.net/references/model_based_design_defs_24c.html http://www.autonomie.net/references/model_based_design_defs_24c.html.] |
===Discussion=== | ===Discussion=== | ||
Revision as of 02:22, 13 September 2012
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)
Source(s)
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.
SEBoK Discussion
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.
blog comments powered by Disqus