SWEREF-477

Link Leave blank if none exists	Unknown macro: {div} https://pdfs.semanticscholar.org/cc9e/074f90d73ff1d389b85dbafcec30a82a9330.pdf
Title This is the text which will be hyperlinked, if a link exists	Software Certification – Coding, Code, and Coders,
SWE or Topic	SWE-061, SWE-185,
Citation This contains additional information, which will appear after the title, separated by a comma	Klaus Havelund and Gerard J. Holzmann Laboratory for Reliable Software (LaRS) Jet Propulsion Laboratory, California Institute of Technology 4800 Oak Grove Drive, Pasadena, California, 91109-8099.
Notes More specific directions where to look in the resource for relevant content

Example Reference as it will appear to end user:

1. Title, Citation

where:

• Title = Title
• Link = http://www.nasa.gov
• Citation = Citation

Quotes used in SWEs and Topics

• SWE-061 - Coding Standards - tab 3 - from various sections

“Code should be checked against the standards with the help of state-of-the-art static source code analyzers. ... Flight code should be checked nightly for compliance with a coding standard and subjected to rigorous analysis with state-of-the-art (static source code analysis tools). The warnings generated by each of these tools are combined with the output of mission-specific checkers that secure compliance with naming conventions, coding style, etc. Also, all warnings, if any (there should be none), from the standard C compiler, used in pedantic mode with all warnings enabled, should be provided to the software developers... (who) are required to close out all reports before a formal code review is initiated. In peer code reviews, an additional source of input is provided by designated peer code reviewers... Separately, key parts of the software design can also be checked for correctness and compliance with higher-level design requirements with the help of logic model checkers.”

• SWE-185 - Secure Coding Standards Verification - tab 3, from abstract and section 2.2 The Code

ABSTRACT: "code is mechanically checked against the standards with the help of state of-the-art static source code analyzers..."

Paraphrasing from section 2.2 The Code
"Code should be checked nightly for compliance with a coding standard and subjected to rigorous analysis with state-of-the-art (static source code analysis tools). The warnings generated by each of these tools are combined with the output of mission-specific checkers that secure compliance with naming conventions, coding style, etc. In addition, all warnings, if any (there should be none), from the standard C compiler, used in pedantic mode with all warnings enabled, should be provided to the software developers... (who) are required to close out all reports before a formal code review is initiated. In peer code reviews, an additional source of input is provided by designated peer code reviewers... Separately, key parts of the software design can be also checked for correctness and compliance with higher-level design requirements with the help of logic model checkers.”