The coding rules all firmware and software must follow, and the static analysis checks that enforce them, covering the language subset, naming, error handling, concurrency and security practices.
Guide or manual Work product in the Firmware and software stack lifecycle
It makes code safer, more secure and easier to review and maintain across many teams. Teams writing to their own habits let defect classes that static analysis would catch reach bring-up and the field, and safety or security assessments find no evidence of disciplined coding.
The full lifecycle detail, with its charts, flows, tables and every section, is for registered members. Registration is free and takes a minute. You come back to this page afterwards.