c - Misra standard for embedded software -


i have requirement make large amount of code misra compliant.
first question: can give estimation passing written code embedded system based on experience. understand "well written" poorly defined , vague ask raw estimation.
second question: recommendation tool can customizable (i.e allowing suppress specific warnings) , used in automatic build environment (i.e command line interface)
other useful suggestions can task.
ilya.

i highly recommend pc-lint. if happen compiling code visual studio recommend plug-in 'visual lint' riverblade. if cannot compile code in visual studio, can still run pc-lint command line effect.

some embedded system compilers provide misra compliance testing compiler warnings. use iar compiler arm7/arm9 development. provides easy configure misra compliance checklist right in compiler setup.

it difficult come rule of thumb estimating time take make written code misra compliant. lot depends on existing coding habits of programmers , how closely follow misra rules in first place.

rough estimates:
2 - 3 days become adept @ pc-lint usage.
initial pass @ making existing code misra compliant: 10 25 percent of time spent writing code in first place.
keeping code misra compliant: 5 10 percent added code development. half of cost changing habits of coders follow 'misra way' of doing things. other half cost of code testing , inspection ensure misra compliance.


Comments

Popular posts from this blog

c++ - How do I get a multi line tooltip in MFC -

asp.net - In javascript how to find the height and width -

c# - DataTable to EnumerableRowCollection -