- Mar 12, 2013
- 8,315
- 1,215
- 126
I am developing an embedded system with around 1000 adjustable variables that can be set by the end user. This embedded system will be in safety critical systems.
The question is this. Is it acceptable practice to put all of the range checking of adjustable variables within the configuration tool and then test/verify that improper variable values can never get into the software via the configuration tool OR must the software do all the range checks itself. This can get quite complicated because the value of one variable can impact the limits of multiple other variables. In terms of testing, there is a significant hit to test time when testing of all limits must be run on the configuration tool, the embedded software in run mode and the embedded software in configuration mode. This is eliminated when limit checking is contained within the configuration tool.
The question is this. Is it acceptable practice to put all of the range checking of adjustable variables within the configuration tool and then test/verify that improper variable values can never get into the software via the configuration tool OR must the software do all the range checks itself. This can get quite complicated because the value of one variable can impact the limits of multiple other variables. In terms of testing, there is a significant hit to test time when testing of all limits must be run on the configuration tool, the embedded software in run mode and the embedded software in configuration mode. This is eliminated when limit checking is contained within the configuration tool.