Feature: Embedded
Critical tools in the software development chain
By Marcel Beemster, Chief Technical Officer, Solid Sands
Repeatedly re-configuring and re-qualifying the compiler brings unwanted additional effort and potential delays, along with cost over-runs. Therefore, it is very important to be precise about the use case
C
ompilers are a critical tool in the soſtware development chain, but they can also be somewhat enigmatic. Te developer must place great trust in the
conversion from human-readable source code into machine-ready object code. Te compiler can
potentially introduce non-conforming behaviour into the program, which may only become apparent aſter the soſtware has been deployed. Tis is clearly not satisfactory when developing safety-critical
soſtware. Functional-safety standards, such as IEC 61508, which covers industrial applications, and ISO 26262 in the automotive arena, call for the compiler to be explicitly qualified for the intended application use case. Te use case is important because the compiler needs to be specifically configured for it, and the options change the generated object code. Te safety standards require that the compiler be verified with the same configuration used in the application’s development. Any changes to the use case are assumed to change the compiler behaviour and will therefore invalidate the qualification. Compiler qualification is a laborious task that demands attention
to detail and can impose harsh penalties for errors. Repeatedly re-configuring and re-qualifying the compiler brings unwanted additional effort and potential delays, along with cost over-runs. Terefore, it is very important to be precise about the use case. Ideally, the correct configuration should be identified at the beginning, to avoid errors. Te first step in the qualification methodology is to analyse
the use case and define the compiler requirements. Next, select the tests to verify these requirements, perform the tests, and then analyse the results. Te final stage is to prepare the documentation required to meet the safety standard. Clearly, there’s always a learning curve associated with any
methodology and tools, as is the case here. In addition, developers must consider overheads such as the costs of licensing test suites, interacting with certification bodies, and dealing with any test failures.
Get help, or… It can be smart for developers of safety-critical soſtware to seek help from a company such as a supplier of safety embedded
16 May 2024
www.electronicsworld.co.uk
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48
