<story><title>NASA Software Safety Guidebook (2004) [pdf]</title><url>http://www.hq.nasa.gov/office/codeq/doctree/871913.pdf</url></story><parent_chain></parent_chain><comment><author>gibsjose</author><text>As a NASA flight software engineer who has created and worked with coding standards for critical software, I would highly recommend Gerard Holzmann&amp;#x27;s (JPL) Power of 10 Rules [&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;spinroot.com&amp;#x2F;gerard&amp;#x2F;pdf&amp;#x2F;P10.pdf&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;spinroot.com&amp;#x2F;gerard&amp;#x2F;pdf&amp;#x2F;P10.pdf&lt;/a&gt;]. This is a set of the 10 most important (and thus highly restrictive) embedded flight software rules. It gets straight to the point and, at only 6 pages, is much easier to apply to actual software development than this ~400 page tome.&lt;p&gt;EDIT:
Another great point referenced in the Power of 10 rules: a requirement is only valuable as long as you can enforce it. With some exception, if you can&amp;#x27;t enforce it with a static analysis tool or something of the sort, it might not belong in your coding standards.</text></comment>
<story><title>NASA Software Safety Guidebook (2004) [pdf]</title><url>http://www.hq.nasa.gov/office/codeq/doctree/871913.pdf</url></story><parent_chain></parent_chain><comment><author>stuartmalcolm</author><text>The thing to bear in mind is that not every organisation needs &amp;#x27;NASA-level&amp;#x27; quality.
IMHO The Capability Maturity Model is a must-read for everyone interested in professional software development.
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Capability_Maturity_Model_Integration&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Capability_Maturity_Model_Inte...&lt;/a&gt;</text></comment>