General Questions

Your main function: Firmware developer Hardware developer Hardware and firmware developer Management Other

Number of firmware developers on your last project:

Number of hardware developers on your last project:

Your team's development methodology: No defined process Waterfall V-model XP, followed religiously XP, followed as appropriate TDD, on all or most functions or features TDD, on more than a third of functions or features Scrum, followed religiously Scrum, followed as appropriate Other agile, followed religiously Other agile, followed as appropriate We call it agile, but there's no real discipline CMM/CMMI level 2 CMM/CMMI level 3 CMM/CMMI level 4 CMM/CMMI level 5 PSP Divine intervention Other

If you selected "other" for the previous question, what method do you use?

The Use of Tools

Lint: We rarely use lint We lint some modules We lint most modules

Static analyzers (i.e., as in the use of tools from Coverity Polyspace, GrammaTech, Klocwork, etc., that do a mathematical analysis of what the code will do at runtime): We don't use static analysis We use static analysis on some of the code We use static analysis on most of the code

If you indicated you do use static analysis in the previous question, which tool do you use?

If you indicated you do use static analysis, are you satisfied with the results? (Feel free to elaborate in the comments at the end of this survey): We don't use static analysis The tool isn't worth the money or hassle We get decent but not stellar results Static analysis provides real value

Does your team routinely use version control? No Yes

If you indicated you do use version control in the previous question, which tool do you primarily use:

Does your team routinely use a tool to manage requirements? No Yes

If you indicated you do use a tool to manage requirements in the previous question, which tool do you use:

Does your team routinely track requirements to test cases? No Yes

Does your team routinely update requirements docs when requirements change? No Yes

Cyclomatic complexity: We don't measure complexity We measure complexity of some functions We measure complexity of most functions

If you indicated your team measures complexity in the previous question, which tool do you use:

Metrics, Standards and Code Inspections

Does your team measure the cost to produce code? No Yes

Does your team measure the number of defects found pre-test? No Yes

Does your team measure the number of defects found during test? No Yes

Does your team measure the number of defects found in integration? No Yes

Does your team use these test metrics to tune your development process? We don't collect any useful test metrics No - the data goes into the bit bucket Yes

Use of firmware standards: Little of the last project complies with a firmware standard Our last project mostly complies with a firmware standard Our last project fully complies with a firmware standard Our last project is mostly MISRA compliant Our last project is fully MISRA compliant

Does your team perform formal code inspections/reviews on most of the code? No Yes

Does your team always or mostly do pair programming? No Yes

Does your team review the code using tools that allow reviews without meetings? We don't use these tools We sometimes use these tools We usually use these tools

If your team uses some other sort of inspection/review, what method do you use?

Testing

Does your team always or mostly create and run unit tests? No Yes

Does your team always or mostly create and run black box tests? No Yes

Automatic vs manual testing: All testing is manual Less than half of our tests are completely automatic More than half of our tests are completely automatic

Does your team, and not the QA group, always or mostly do integration testing? No Yes

Does your team have dedicated testers (not including the QA group)? No Yes

Does your team (or your QA group) always or mostly run regression tests prior to shipping? No Yes

Miscellaneous

Does your team have - and use - a formal change control process? No Yes

Does your team use UML or other formal modeling? No We use modeling to design our product We use it and even generate code from our models

How many assert macros (or equivalent) do you estimate your team uses per 1000 lines of code:

Feel free to make any comments about your team's firmware engineering processes: