[hemmerling] Good Coding ! - Software Coding, Coding Rules, Static Code Analysis, Code Reviews

Related pages:

• Requirements.
• Software Documentation.
• Testing.
• Security.
• System Design.

• “ISO/IEC 25010:2011”.
• The legacy norm EN.Wikipedia "ISO/IEC 9126", DE.Wikipedia "ISO/IEC 9126" - “It has been replaced by ISO/IEC 25010:2011”, “ISO/IEC then started work on SQuaRE (Software product Quality Requirements and Evaluation), a more extensive series of standards to replace ISO/IEC 9126, with numbers of the form ISO/IEC 250mn”.
• EN.Wikipedia "SQALE".

• Software Craftsmanship North America.
  • Manifesto of Software Craftsmanship.
• Softwarekammer - Software Craftmanship Communities in Deutschland.
  • Wiki Groupspaces "Softwarekammer MOB - Software Craftmanship Communities in Münster, Osnabrück & Bielefeld".
  • Wiki Softwarekammer Wiki - Software Craftmanship Communities in Deutschland, Wiki "Hamburg".
• EN.Wikipedia "Software craftsmanship"

• clean-code-developer.de - Prinzipien und Praktiken für bessere Software.
• Robert C. Martin ( = Uncle Bob ).
  • Book Robert C. Martin: "Clean Code: A Handbook of Agile Software Craftsmanship" #.
  • Google Code "myebooksforrefactor".
    • Prentice.Hall.Clean.Code.A.Handbook.of.Agile.Software.Crafts.pdf.
  • Book Robert C. Martin: "Clean Code - Refactoring, Patterns, Testen und Techniken für sauberen Code".
  • Book Robert C. Martin: "Clean Coder: Verhaltensregeln für professionelle Programmierer".
• EN.Wikipedia "SOLID (object-oriented design)", DE.Wikipedia "Prinzipien objektorientierten Designs".
  1. EN.Wikipedia "Single responsibility principle", DE.Wikipedia "Single-Responsibility-Prinzip".
  2. EN.Wikipedia "Open/closed principle", DE.Wikipedia "Open-Closed-Prinzip".
  3. EN.Wikipedia "Liskov substitution principle", DE.Wikipedia "Liskovsches Substitutionsprinzip".
  4. EN.Wikipedia "Interface segregation principle", DE.Wikipedia "Interface-Segregation-Prinzip".
  5. EN.Wikipedia "Dependency inversion principle", DE.Wikipedia "Dependency-Inversion-Prinzip" → EN.Wikipedia "Dependency injection", DE.Wikipedia "Dependency Injection" is one method of following this principle.
• Communication by interfaces.
  • EN.Wikipedia "Interface segregation principle", DE.Wikipedia "Interface-Segregation-Prinzip".
  • Diamond structure of interfaces: There is just one-way calling direction, e.g. every class has an interface.
    • So the calling class calls the called class by the interface of the called card.
    • But the calling class also has its own interface for getting answers by the called class.

• Xp Simplicity Rules.
  • Simple code:
    1. Runs all the tests.
    2. Contains no duplication (OnceAndOnlyOnce).
    3. Expresses all the ideas you want to express.
    4. Minimizes classes and methods.

• Stack Exchange "How can I deal with the cargo-cult programming attitude?".
• EN.Wikipedia "Cargo cult programming".
• EN.Wikipedia "Copy and paste programming".
• EN.Wikipedia "Magic (programming)".

• Abraxas (CodeCheck).
• AdaCore.
  • AdaCore (CodePeer), 2016.
  • AdaCore (GNATcheck), 2016.
  • SofCheck Inspector (AdaCore).
• Checkmarx (Checkmarx CxSAST).
• Cleanscape (Cleanscape LintPlus for C/C++ Lint, FortranLint).
• Coverity / Synopsys (Coverity Static Analysis Verification Engine).
• Cppcheck (Sourceforge).
• Eclipse (Codan).
• Gimpel Software (PC-Lint/FlexeLint).
• GrammaTech (CodeSonar, CodeSurfer).
• HP (HP Fortify Static Code Analyzer) 2015-2016, Micro Focus/HP (Fortify Static Code Analyzer) 2018
• IAR (C-STAT), 2018.
• IBM (Rational Appscan).
• Klocwork / Rogue Wave (Insight) / Klocwork Insight.
• LDRA (LDRA Testbed).
• MathWorks (Polyspace).
• McCabe (McCabe IQ).
• Monroe Software (Quicktest), 2016-08.
• Parasoft (Parasoft C++test/Jtest/dotTEST).
• Programming Research / PRQA (QA-C/C++).
• Sourceforge (CPPcheck), 2016.
• Veracode (Veracode).

• CERT, Software Engineering Institute (SEI), Carnegie Mellon University.
  • CERT "CERT Secure Coding Standards".
    • CERT "CERT C Secure Coding Standard".
    • CERT C++ Secure Coding Standard.
    • The CERT Oracle Secure Coding Standard for Java.
    • Informit "Robert C. Seacord: C Secure Coding Rules: Past, Present, and Future", 2013-06-26.
  • CERT "Secure Coding".
  • CERT "Tech Tips - Historical CERT Documents".
  • Book Robert Seacord: "The CERT C Secure Coding Standard (2nd Edition)".
    • Informit - Secure Coding in C and C++, 2nd Edition - extra material, by the publishing house.
    • CERT: C Secure Coding Standard - extra material, by the publishing house.
    • CERT - "Robert C. Seacord: Secure Coding in C and C++ (2nd Edition)".

• “A Community-Developed Dictionary of Software Weakness Types” - See Security.

• “OWASP Top Ten” → See Security.

• See Security.

• IPA.
  • IPA "Software Reliability EnhancementIPA:Software Engineering:Working to Improve Software Development Capabilities".
    • The free PDF document IPA "ESCR (Embedded System development Coding Reference) [C language edition] Ver. 2.0".
    • The free PDF document IPA "IPA:Software Engineering:ESCR C++(Embedded System development Coding Reference)[C++ language edition]".
• LDRA.
  • LDRA "IPA/SEC ESCR Coding Standard Compliance".

• Coala - Linting and Fixing Code for All Languages, GitHub "coala development group", ReadTheDocs "coala: Language Independent Code Analysis" - “coala provides a unified command-line interface for linting and fixing all your code, regardless of the programming languages you use”

• The OpenSource GitHub "squizlabs / PHP_CodeSniffer" - “It tokenises PHP, JavaScript and CSS files and detects violations of a defined set of coding standards”.

• The OpenSoure SonarQube, SonarSource - “A code quality management platform, dedicated to continuously analyze and measure technical quality, from the projects portfolio to the class method”.
  • SonarSource "Editions".
    • SonarSource "Community Edition".
  • SonarQube "Features" - “Languages Support - More than 20 languages”.
  • SonarQube "Documentation".
    • SonarQube "Plugin Library".
      • SonarQube "Java Ecosystem".
      • SonarQube "SonarQube Python Plugin".
  • SonarQube plugins for other host software.
    • Jenkins "SonarQube plugin" - I was told by experts, that you may break a built, using SonarQube with Jenkins by such a plugin...
  • The Codehaus.
    • The Codehaus - “The platform was to be terminated at the end of February 2015”.
    • GitHub "The Codehaus".

• The OpenSource GitHub.io "PMD", GitHub "PMD", SourceForge "PMD", SourceForge "PMD" - “A source code analyzer. It finds common programming flaws like unused variables, empty catch blocks, unnecessary object creation, and so forth. It supports Java, JavaScript, XML, XSL. Additionally it includes CPD, the copy-paste-detector. CPD finds duplicated code in Java, C, C++, C#, PHP, Ruby, Fortran, JavaScript”.
  • SourceForge "PMD" - "Integrations with IDEs".
  • EN.Wikipedia "PMD (software)", DE.Wikipedia "PMD (Software)".
• GitHub "The FindBugs project. Project working on the FindBugs project, a static analysis tool for Java", SourceForge "FindBugs - Find Bugs in Java Programs", SourceForge "FindBugs".
  • Eclipse Marketplace "FindBugs Eclipse Plugin".
  • EN.Wikipedia "FindBugs", DE.Wikipedia "FindBugs".
• GitHub "Checkstyle", SourceForge "checkstyle", SourceForge "checkstyle - static code analysis tool for Java".
  • EN.Wikipedia "Checkstyle", DE.Wikipedia "Checkstyle".

• SonarLint.
  • SonarLint for Eclipse.
  • SonarLint for Visual Studio.
• GitHub "SonarSource/sonarlint-eclipse".
• Eclipse Marketplace "SonarLint".
• Twitter "SonarLint, @SonarLint".

• Experts told me in 2016-08, that with new releases, there might be not just new features, but some features might be discontinued too, unexpectedly...
• EN.Wikipedia "SonarQube", DE.Wikipedia "SonarQube".

• hello2morrow - Empowering Software Craftmanship,
  • hello2morrow "Sonargraph" - “The Sonargraph platform supports Java, C# and C/C++ out of the box and includes powerful features like a Groovy based scripting engine and a DSL (domain specific language) to describe software architecture”.
• EN.Wikipedia "Sonargraph".

• CERT C.
• CERT C++.
• CERT Java.
• HIC++.
• Common Weakness Enumeration (CWE) Secure Coding Standards.
• HIS.
• MISRA C.
• MISRA C++.
• Netrino C.
• JSF AV++.
• PA/SEC ESCR.

• EN Wikipedia "MISRA-C", DE.Wikipedia "MISRA-C".
• MISRA C, MISRA C++.
• MISRA DAY.

• Guidelines For The Use Of The C Language In Vehicle Based Software, 1998.
• IAR Embedded Workbench MISRA C:1998 Reference Guide ( PDF ).
• MISRA-C:2004. Guidelines for the use of the C language in critical systems ( PDF ).
• MISRA C Rules ( PDF ) - The PDF extraction of chapter 7 of the MISRA-C:2004 book.
• MISRA-C++:2008. Guidelines for the use of the C++ language in critical systems ( PDF ).

• Herstellerinitiative Software ( HIS ).
• Herstellerinitiative Software "Software Test".
  • Gemeinsames Subset der MISRA C Guidelines 1.0.3 ( PDF ), 2004-04-20 - Definition of a subset of the “MISRA Guidelines Version 1998”.
    • The MISRA-C rules 3, 4, 6, 12, 15, 28, 44, 49, 82, 92, 110, 111 are no HIS rules.
  • Gemeinsames Subset der MISRA C Guidelines 2.0 ( PDF ), 2006-02-14 - Definition of “MISRA Guidelines Version 2004” as standard, no subset.
• “HIS Source Code Metrics” .

• Gimpel Software.
  • Gimpel Software "MISRA C checking provided by PC-lint/FlexeLint".
  • PC-lint for C/C++ on Windows.
    • PC-lint Support Files #.
    • PC-Lint Distribution Options.
      • PC-lint on CD ROM, will support Windows and OS/2 and 16-bit MS-DOS.
      • PC-lint download will support only Windows.
    • EN.Wikipedia "PC-Lint".
    • ALOA – A Lint Output Analyzer.
      • The free original Ralf Holly "ALOA – A Lint Output Analyzer".
      • The OpenSource SourceForge "ALOA - A Lint Output Analyzer", SourceForge "ALOA - A Lint Output Analyzer".
    • Gimpel - International Dealers for PC-lint Workstation Licenses.
      • German vendor SienerSoft GmbH - search for “lint” .
      • German vendor KESSLER SOFTWARE GmbH & Co. KG - "PC-Lint für C/C++ V9.0" - “Wir liefern nicht an Privatpersonen” .
      • UK vendor Phaedrus Systems Ltd "PC-Lint Static Analyser" - “We are the only UK distributor able to supply PC-Lint site licenses, Flexe-lint, site licences and upgrades”.
  • FlexeLint for C/C++, on Linux.
  • Resources:
    • Phaedrus Systems "IAR Embedded workbench to PC-lint integration" - Free downloads.
    • BARR group "Top 10 Bug-Killing Coding Standard Rules".
    • Robert Gamble - Rob's Programming Blog. Various Musings about Software Development and Technology "Cooperative Limiting of Concurrent Process Instances ", 2011-04-28.
• COSMIC Software GmbH "Cosmic Software MISRA CHECKER".
• IAR Systems - “IAR Embedded Workbench IDE”.
  • The free Kickstart Development Tools are not shipped with the MISRA-C checker.
  • YouTube "IAR Embedded Workbench with MISRA C".
    • Workspace - right-click on the source file name - “Options / “C/C++ Compiler” / MISRA-C 2004”
    • Workspace - right-click on the source file name - “Options / “C/C++ Compiler” / MISRA-C 1998”.
  • There is no MISRA-C++ 2008 checker:-(.
• LDRA Software Technology "LDRA Tools Suite".
  • LDRA Software Technology "LDRA Testbed".
    • LDRA Software Technology "Programming Standards" → List of coding standards.
      • LDRA Software Technology "MISRA-C:2004 Certification with the LDRA tool suite".
      • LDRA Software Technology "MISRA-C++:2008 Conformance with the LDRA tool suite".
• Mathworks "PolySpace Embedded Software Verification" - checker for MISRA C, MISRA-C++ and JSF++.
  • Mathworks "R2010b Documentation → PolySpace".
• Programming Research Group ( PRQA ) - “QA-C”, “QA-C++”, “QA-J”.
• QA Systems, Germany - “QA-C, QA-C++, QA-MISRA, Cantata++”.
  • QA Systems, Seminare - free german webinars !
• RistanCASE GmbH "Development Assistant for C (DAC)".
  • RistanCASE GmbH "DAC Supported Standards" / "MISRAC".
• TASKING - Embedded Software Tools from Altium - checking for MISRA C and CERT.
  • TASKING "MISRA C code checking compiler technology".
    • “Today, MISRA C code checking is broadly adopted and available in many TASKING tool chains, including Infineon TriCore and C166, ARM, STMicroelectronics ST10, Renesas M16C, NXP XA, and 8051 (over two dozen manufacturers supported)”.
    • “A pull down configuration menu in EDE allows the activation of the MISRA C rules to be applied for a particular project. A predefined configuration for conformance with the required rules in the MISRA C guidelines is readily available”.
    • “Alternatively, it is possible to read C settings from an external configuration file. This feature is particularly useful in situations where the development team needs to comply with a specific set of MISRA C rules under management by the company’s Quality Assurance department”.
• Texas Instruments "Code Composer Studio (CCStudio) Integrated Development Environment (IDE)".
  • TI E2E Community, Support Forums / Development Tools / Code Composer Studio / Forum - Thread "CCS V4 (Microcontroller/Core) Language Options", 2009-09-24.
    • “Under Project Properties, C/C++ Build, Tool Settings, C2000 Complier, Language Options, there is an option 'Enable checking of MISRA-C:2004 rules'”.
    • “Misra support is not actually fully implemented yet and was mistakenly exposed in the build options dialog”.
  • In 2011-07 I learned by a TI representative, that MISRA-C & HIS support is now almost complete. I was told that just the rule 45 of MISRA-C:1998 ( “Type casting from any type to or from pointers shall not be used” ) and rules 11.1-11.5 of MISRA-C:2004 respectively cannot be detected, with pointers.
  • With CCS 5.5.0, you can activate MISRA-C checking by “Project Properties / Build / MSP430 Compiler / Advanced Options / MISRA-C:2004” individually for each rule, or by all rules ( button “All” ).
  • With CCS 5.5.0.
    • “C:\<ccs installation directory>\msp430\MSP430ware\eclipse\plugins\com.ti.ccstudio.buildDefinitions.MSP430_5.5.0.201308270800\resources\buildDefinitions\native\metadata” contains two XML files ( “CHECK_MISRAMSP430_3.3.xml”, “CHECK_MISRAMSP430_3.4.xml”) with the incomplete (!) text of the MISRA-C rules - some rules are missing.
    • If you installed CCS with support for either C2000 or ARM, you can find the file with a list of all implemented MISRA-C:2004 rules in ”<ccs installation directory>\ccsv5\tools\compiler\arm_5.1.1\misra.txt” or ”<ccs installation directory>\ccsv5\tools\compiler\c2000_6.2.0\misra.txt”. The file is not shipped with the MSP430 C compiler.

• University of Oxford, Systems Verification Group.
  • The OpenSource University of Oxford, Systems Verification Group, Carnegie Mellon Homepage "CBMC - Bounded Model Checking for Software".
  • University of Oxford, Systems Verification Group "CPROVER Manual. CBMC: Bounded Model Checking for C/C++ and Java".
• GitHub "diffblue/cbmc".

• I got the 23-pages paper document “C Programming Standards & Practices #10, Version IR” ( “S & P #10 ) by “Commercial Aircraft Products Division” ( CAPD ) of 1990-03-15.
  • “Standards & Practices #10 establishes the programming standards and guidelines to be used by programmers in the development and maintenance of 'C' programs for the Commercial Aircraft Products Division ( CAPD )”.

• High Integrity C++ Coding Standard Version - “Request High Integrity C++ Coding Standard. Complete this form to receive your PDF of the coding standard promptly by email”.
  • EN.Wikipedia "High Integrity C++".

• Joint Strike Fighter (JSF) Program - Downloads - ”JSF Air Vehicle - C++ Coding Standards (Revision C)” ( DOC ).

• Book Michael Barr "Embedded C Coding Standard", 2009 - The official “Barr Group / Netrino” coding rules.
• Book Michael Barr "Programming Embedded Systems.: With C and GNU Development Tools", 2006.
• LDRA.
  • LDRA "Netrino C – The Embedded C Coding Standard by the Barr Group".
• Barr Group.
  • Barr Group "Barr Group's Embedded C Coding Standard".
  • Barr Group "Bug-Killing Coding Standard Rules for Embedded C".
    • SlideShare "Embedded C Coding Standard".
  • Barr Group "Embedded C/C++. Articles relating to C or C++ programming techniques used by embedded software developers".
  • The free quiz Barr Group "Embedded C Quiz".
• Netrino, LLC. - The Embedded System Experts.
  • The free quiz Netrino "Embedded C++ Quiz".

• Phaedrus Systems "quEST".
  • Chris A Hills, Phaedrus Systems "Quality Embedded Software Techniques".
  • Chris A Hills, Phaedrus Systems "MISRA-C [1] A Standard for Embedded and Real-time C".
  • Chris A Hills, Phaedrus Systems "PC Lint".

• GitHub "saaadhu/naggy" for the IDE “Atmel Studio 6” & Atmel “C/C++” compiler chain.
  • Installation is integrated into the IDE “Atmel Studio 6”.
  • “A live compiler diagnostics extension for Atmel Studio”, “An Atmel Studio extension that uses the Clang frontend from the LLVM project to show errors/warnings on the fly, and to lowlight code excluded by preprocessor directives”.

• Microsoft PREfast - A “C++” static code checker.
  • PREfast is integrated in Visual Studio.NET Team Edition and is also included in the “Windows Server 2003 SP1 DDK” and the “Windows Driver Kit (WDK)”.
  • Windows Hardware Developer Central "PREfast for Drivers".
    • Windows Hardware Developer Central "PREƒast Step-by-Step".
    • Windows Hardware Developer Central "Windows Server 2003 DDK".
    • Windows Hardware Developer Central "WDK and Developer Tools".
    • Windows Hardware Developer Central "Windows Driver Kit (WDK)".
    • Windows Hardware Developer Central "Windows Driver Foundation (WDF)".
  • EN.Wikipedia "Windows Driver Foundation".
  • ZH.Wikipedia "PREFast for Drivers".
• The commercial Parasoft C/C++test - “C/C++ Static Analysis, Code Review, Unit Testing, Runtime Error Detection”.
• Splint ( “Secure Programming Lint”, formerly: LCLint ).
  • Splint Publications.
    • “Splint Manual”.
    • “LCLint User's Guide”.
  • Sourceforge "splint - secure programming lint", Sourceforge "splint - secure programming lint".
  • Splint - Win32 Installation.
  • github "maoserr:splint_win32" - Windows installer for splint-3.1.2.
  • EN.Wikipedia "Splint (programming tool)", DE.Wikipedia "Splint (Software)".

• EN.Wikipedia "lint (software)", DE.Wikipedia "Lint (Programmierwerkzeug)".
  • Oracle "C User's Guide. Chapter 6. lint Source Code Checker".
• EN.Wikipedia "Static code analysis".
• EN.Wikipedia "List of tools for static code analysis".
• EN.Wikipedia "Automated code review" - list of free tools.

• "Structural Analyzer- Structure101" - “Visualize, understand, and address complexity in your large C and C++ software projects”.

• Riverblade "Visual Lint" for Windows.
  • “To use Visual Lint, you must have access to licenced installations of PC-lint and Microsoft Visual Studio 2003 Pro, 2005 Pro, 2008 Pro, 2010 Pro”.
  • “Support for Eclipse is under development” ( 2010-12 ).
• Xoreax Software "IncrediBuild" - A 30 days trial version is available for download..
  • Xoreax Software "Accelerating PC-Lint C++ Code Analysis".

• bobah.net. details matter "C++ code coverage profiling with GCC/GCOV".
• CodeFlu "Using Gcov and Lcov to generate beautiful C++ code coverage statistics".
• Eclipse Help "GCov Plug-in User Guide".
• Using the GNU Compiler Collection (GCC) "10 gcov—a Test Coverage Program".

• SourceForge "Gcov Code-coverage plug-in for Eclipse", SourceForge "Gcov Code-coverage plug-in for Eclipse".

• Code Yarns. Notes from a programmer's journal "How to profile C/C++ code using gprof".
• Linux Focus, Arnout Engelen "Profiling with GProF. Optimizing C/C++ programs using the GProf profiler".
• The Geek Stuff "GPROF Tutorial – How to use Linux GNU GCC Profiling Tool".

• Another Gentoo Dev. My opensource life "Use gcov and lcov to know your test coverage".
• GitHub "linux-test-project/lcov".
• die.net "lcov(1) - Linux man page".
• SourceForge "Linux Test Project. Testsuite to validate the reliability, robustness, stability of Linux", SourceForge "Linux Test Project. Testsuite to validate the reliability, robustness, stability of Linux".
  • SourceForge "LCOV - the LTP GCOV extension".
• Michael Stapelberg "Code Coverage testing in C with gcov and lcov".
• The Document Foundation’s wiki "LCOV Code Coverage".

• Oracle "Code Conventions for the Java TM Programming Language", 1999-04-20.
• Gnome "Dia" - Coding Guidelines - “The base of the coding guidelines are Sun's guidelines for Java, even though Dia is written in C”.

• jQAssistant ( jQAssistant Developer Blog ) by buschmais GbR.
  • buschmais GbR "jQAssistant – Entdecke Deine Java-Anwendung", 2013-11-07.
    • GitHub "buschmais/jqassistant" - “Former jQAssistant Master Repository. We splitted jQAssistant in multiple single repositories to be able to build a better and more flexible build an release infrastructure then we had before”.
    • GitHub Wiki "buschmais/jqassistant".
    • Blog jQAssistant Developer Blog - The main resource for jQAssistant, it's not just a blog.
      • QAssistant Developer Blog "Get Started – Scan, explore and validate your Java application in a few minutes" - “Get Started / Download”.
  • Google Groups "jQAssistant".
  • StackOverflow Tag Info "jqassistant" - “jQAssistant is an open source source code analytics tool that scans various aspects of a software project into a graph database (neo4j)”.
• Jens Schauder - Schauderhaft.
  • Blog Jens Schauder - Schauderhaft Blog.
    • Jens Schauder - Schauderhaft "Degraph" - “Take Control of your Dependencies. With Degraph you control and visualize class and package dependencies in your JVM application.”.
    • GitHub "schauder/degraph".

• “Java -Xlint”.
  • Java World "javac's -Xlint Options".
• Crap4j, Google Code " crap4j. A tool for assessing Java project quality".
  • “Change Risk Analysis and Predictions” ( CRAP, C.R.A.P. ).
    • artima "Alberto Savoia: Agitating Thoughts & Ideas Pardon My French, But This Code Is C.R.A.P.".
    • Nuno Franco Da Costa "Your code is CRAP" → PHPUnit.
    • Santos Jacob "What is your C.R.A.P. Index?" - “The upcoming 3.2 release” of PHPUnit “will include software metrics, one of which is Cyclomatic Complexity. Cyclomatic Complexity is used in finding the C.R.A.P. index of a method”.
    • Levi Hackwith "How to Read and Improve the C.R.A.P Index of your code".
    • OXIDwiki "Certification/Modules".
    • Semantic MediaWiki "Help:Code coverage in a nutshell".
    • EN.Wikipedia "Software metric", DE.Wikipedia "Softwaremetrik" - ” C.R.A.P. ( Change Risk Analysis and Predictions )”
• Sourceforge "Checkstyle", Sourceforge "Checkstyle" - “A development tool to help programmers write Java code that adheres to a coding standard. It automates the process of checking Java code to spare humans of this boring (but important) task”.
  • Sourceforge "Eclipse Checkstyle Plug-in", Sourceforge "Eclipse Checkstyle Plug-in" - Eclipse plugin for Checkstyle.
  • Checkstyle is dedicated to check programming style guidelines .
  • Checkstyle uses an ANTLR grammar for Java “com/puppycrawl/tools/checkstyle/grammars/java.g”.
  • EN.Wikipedia "ANTLR", DE.Wikipedia "ANTLR".
  • EN.Wikipedia "Abstract syntax tree", DE.Wikipedia "Abstrakter Syntaxbaum" ( AST ).
• Google Java Developer Tools “CodePro AnalytiX” - “A free powerful software code quality, testing and static analysis tool”.
• Sourceforge "FindBugs - Find Bugs in Java Programs", Sourceforge "FindBugs - A static analysis tool to find bugs in Java programs".
  • The FindBugs Eclipse plugin update site.
  • SourceForge "fb-contrib: A FindBugs auxiliary detector plugin", SourceForge "fb-contrib".
  • IBM DeveloperWorks, Chris Grindstaff "FindBugs, Part 1: Improve the quality of your code.Why and how to use FindBugs".
  • IBM DeveloperWorks, Chris Grindstaff "FindBugs, Part 2: Writing custom detectors. How to write custom detectors to find application-specific problems".
  • Findbugs analysis Java bytecode ( so is suitlable to analyse .JAR libraries and .JAR executables too ) and focusses on correctness bugs .

• Parasoft Jtest - Java Testing, Static Analysis, Code Review”.
• Xanitizer - “Web Application Security mit Statischer Code Analyse”, “Analysiert den Programmcode der Applikation und sucht darin systematisch nach Sicherheitslücken für Angriffsmethoden, wie z.B. SQL Injection, Cross-Site Scripting oder Command Injection”, “unterstützt insbesondere die Analyse von Java Webapplikationen inklusive Web-Frameworks”

• ECLEmma.
• SourceForge "EMMA", SourceForge "EMMA"
• DE.Wikipedia "Emma (Software)".
• EN.Wikipedia "Java Code Coverage Tools".
• EN.Wikipedia "Code coverage", DE.Wikipedia "Testabdeckung".

• The OpenSource JavaScript Lint, SourceForge "JavaScript Lint", SourceForge "JavaScript Lint".
  • The free online service JavaScript Lint - Online Lint.
• JSLint, GitHub "douglascrockford/JSLint" - “The JavaScript Code Quality Tool”.
  • StackOverflow "Why does JSLint give strict violation error on this function?" - “This is because JSLint doesn't recognize your function as a constructor. By convention, you must use uppercase letters”.
  • EN.Wikipedia "JSLint", DE.Wikipedia "JSLint".
• JSHint - “A JavaScript Code Quality Tool”.
  • EN.Wikipedia "JSHint", DE.Wikipedia "JSHint".
• Github "reid / node-jslint" - “The JavaScript Code Quality Tool — for Node.js”.

• The commercial Parasoft doTEST - ”.NET Static Analysis, Code Review, Unit Testing”.

• “ScriptCop” - See Scripting Languages for Windows 2/2 - Windows Powershell.

• The PHP Group - pear "Coding Standards".

• PHP-FIG — PHP Framework Interop Group.
• GitHub "php-fig / fig-standards", "PSR-2-coding-style-guide.md" - “Coding Style Guide”.
• GitHub "php-fig / fig-standards", "PSR-1-basic-coding-standard.md" - “Basic Coding Standard”.

• Sebastian Bergmann.
  • GitHub "sebastianbergmann / phploc" - “A tool for quickly measuring the size and analyzing the structure of a PHP project”.
  • GitHub "sebastianbergmann / phpcpd" - “Copy/Paste Detector (CPD) for PHP code”.
• GitHub "fabpot/PHP-CS-Fixer".
• PHP Depend - “Software Metrics for PHP”.
• PHPMD - PHP Mess Detector - “It is a spin-off project of PHP Depend and aims to be a PHP equivalent of the well known Java tool PMD”.
• Sensio Labs "PHP Coding Standards Fixer. The PSR-1 and PSR-2 Coding Standards fixer for your code".

• Jason McCreary. A PHP and iOS developer. A thinker "Be a Better PHP Developer: Coding Standards".

• See Python 4/6 - Pro & Contra.

• See Tcl / Tk ( tickle ) 2/2 - Debugging & Testing.

• The OpenSource toolkit for rapid development and execution of software quality analyses CQSE GmbH "ConQAT" in Java and .NET 2.0, for Java, C#, C/C++,...
• Blog CQSE GmbH "Software Quality Blog".
• DE.Wikipedia "ConQAT", EN.Wikipedia "ConQAT".

• IBM Rational Rhapsody ( see Unified Modeling Language ( UML ), Systems Modeling Language ( SysML ) ) with “Simplified C++ Execution Framework” ( SXF C++​ ).
  • IBM "IBM Rational Rhapsody Software Version 7.6 and Rhapsody Design Manager Version 3.0: New Features and Enhancements" - “MISRA C++ 2008 compliance with modeling checks​”.
  • IBM Rational Rhapsody 7.6 Help "Simplified C++ execution framework (SXF)".
  • IBM Rational Rhapsody 7.6 Help "Project settings".

​​

• e-Guidelines. Guidelines for Model Based Development by Dr.-Ing. Ingo Stürmer, Model Engineering Solutions.
• MathWorks Deutschland "Automobilindustrie".
  • MathWorks Deutschland "Automobilindustrie" - The MathWorks Automotive Advisory Board - “Control Algorithm Modeling Guidelines using MATLAB, Simulink, and Stateflow” ( DOC+PDF ).
  • MathWorks Deutschland "Simulink Verification and Validation".
  • MathWorks Deutschland "MISRA C Support in MATLAB and Simulink".
• MathWorks, MATLAB Digest - July 2003 "Checking Code and Models in Production Environments".

• Eisenbahn-Bundesamt.
  • “Eisenbahn-Bundesamt, München. Technische Grundsätze für die Zulassung von Sicherungsanlagen (Mü 8004)”.
  • Martin Lottermoser - “Mängel der Programmierregeln des Eisenbahn-Bundesamtes”.
• Bundesanstalt für Arbeitsschutz und Arbeitsmedizin.
  • Bundesanstalt für Arbeitsschutz und Arbeitsmedizin "Programmierregeln für die Erstellung von Software für Steuerungen mit Sicherheitsaufgaben. Schriftreihe der Bundesanstalt für Arbeitsschutzund Arbeitsmedizin Fb 812".

• European Committee for Electrotechnical Standardization ( CENELEC ) - European norm “EN 50128”.
  • DE.Wikipedia "EN 50128".

• Charles Simonyi “Apps Hungarian”. ”Systems Hungarian”.
  • EN.Wikipedia "Hungarian notation", DE.Wikipedia "Ungarische Notation".

• Book Bruce Powel Douglass "Design Patterns for Embedded Systems in C: An Embedded Software Engineering Toolkit".
• Les Hatton.
  • Book Les Hatton "Safer C: Developing Software for High-Integrity and Safety-Critical Systems", 1994.
  • Scientific and other writing of Les Hatton.
    • Scientific and other writing of Les Hatton "Safer Subsets".
      • Les Hatton "Language subsetting in an industrial context: a comparison of MISRA C 1998 and MISRA C 2004".
      • Les Hatton "A MISRA C exemplary test suite" - “This incomplete suite, released under the GPL, was an exemplary set of code examples and supporting infrastructure for MISRA C Version 1 (MISRA-C 1998)”.
• Michael Howard, David LeBlanc.
  • Book Michael Howard, David LeBlanc "Writing Secure Code, Second Edition" #.
  • Microsoft MSDN Library "David LeBlanc: Integer Handling with the C++ SafeInt Class".
• John Viega, Matt Messier.
  • Book John Viega, Matt Messier "Secure Programming Cookbook for C and C++. Recipes for Cryptography, Authentication, Input Validation & More".
  • Companion site John Viega, Matt Messier "Secure Programming Cookbook for C and C++. Recipes for Cryptography, Authentication, Input Validation & More".

• Coccinelle.
• Wiki Coccinelle Wiki.
• EN.Wikipedia "Coccinelle (software)".

• EN.Wikipedia "Source Annotation Language".
• Michael Howard's Web Log. A Simple Software Security Guy at Microsoft! "A Brief Introduction to the Standard Annotation Language (SAL)".
• Microsoft MSDN Library "SAL Annotations".

• Microsoft Research "Spec#" ( “Spec sharp” )

• Developer Express Inc. "Visual Studio Productivity Tools", "Free Editions".
  • The free Developer Express Inc. "Refactor! for C++" for VS.2005 / 2008 / 2010 - “Free Refactoring Tool for C++ Developers”, “A free Visual Studio Add-in that integrates into your IDE providing one-key access to numerous refactorings for C++ code”.
    • MSDN Visual C++ Developer Center "Refactor! For Visual C++ 2005".
  • The free Developer Express Inc. "Refactor! for ASP.NET" for VS.2005 / 2008 / 2010 - “Free Refactoring Tool for ASP.NET Developers”, “A free Visual Studio Add-in that integrates into your IDE providing one-key access to numerous refactorings for ASP.NET code”.
  • The free Developer Express Inc. "CodeRush Xpress" for VS.2008, VS.2010 - “Includes intelligent code navigation, selection and declaration features with over 50 refactorings for VB and C# developers”.
  • Once in 2007, there was a free “Refactor! for Visual Basic”.

• The OpenSource JaMoPP by DevBoost- “Java Model Parser and Printer” - “Bridging the gap between models and source code”.

• TechQues "Power Efficient Software Coding".

• The commercial Atlassian "Crucible" - “Code review tool for SVN, Git, Perforce and more”.
  • EN.Wikipedia "Crucible".
• The commercial Atlassian "FishEye" - “Code search and diff tool for SVN, Git and more”.
  • EN.Wikipedia "FishEye (software)".

• Google Code "gerrit. Gerrit Code Review".
• EN.Wikipedia "Gerrit (software)", DE.Wikipedia "Gerrit (Software)".
• Gerrit works closely together with the CVS software “Git” → See Revision Control & Revision Control Systems (RCS), Source Code Version Control Systems ( SCVCS, VCS, CVS ), Software Configuration Management ( SCM ).
• Gerrit collaborates with the automatic built tools “Hudson” and “Jenkins” → See Continuous Integration ( CI ) & Continuous Delivery ( CD ).
• Gerrit 1.0 in Python, a fork of Rietveld.
• Gerrit 2.x and newer in Java.

• Google Code "rietveld. Code Review, hosted on Google App Engine".
• EN.Wikipedia "Rietveld (software)" in Python.

• EN.Wikipedia "List of tools for code review".

• Book Adam Tornhill "Your Code As a Crime Scene: Use Forensic Techniques to Arrest Defects, Bottlenecks, and Bad Design in Your Programs.
  • The accompanying website The Pragmatic Bookshelf | Your Code as a Crime Scene.
  • YouTube "Code, Crime, Complexity: Analyzing software with forensic psychology | Adam Tornhill | TEDxTrondheim".
  • ScanLibs "Your Code as a Crime Scene: Use Forensic Techniques to Arrest Defects, Bottlenecks, and Bad Design in Your Programs".

• SANS Institute.
  • SANS Institute "CWE/SANS TOP 25 Most Dangerous Software Errors".

• The execution result of this code depends on compiler implementation and maybe even the code optimisation level

  int aArray[10], aIndex;
  aIndex = 5;
  aArray[aIndex] = aIndex++;
  

• Canadian Mind Products, Roedy Green "unmaintainable code : Java Glossary".
  • Blog Roedy Green "Unmaintainable code. How to write unmaintainable computer programs".
• COMEFROM.
  • EN.Wikipedia "COMFROM".
  • Come From. The opposite of a goto statement.
• Dr. Dobbs Journal "Robert C. Seacord: Integral Security".
• heise "Daniel Düsentrieb C#, Java, C++ und Delphi im Effizienztest, Teil 2", 2003-10-06.
• Netrino - Embedded Systems Experts.
  • Netrino - How-To - Articles.
    • Netrino - How-To - Articles "Nigel Jones - Efficient C Code for 8-bit Microcontrollers".
    • Netrino - How-To - Articles "Michael Barr - Bug-Killing Coding Standard Rules for Embedded C".
• SlideShare, Dire "Weil, gedoplan: 'Gute Zeilen, schlechte Zeilen – Regeln für wartbare Programme'" - Coding rules for Java #.

• Book Karl Eugene Wiegers: "Peer Reviews in Software: A Practical Guide".
• Slideshare "Frank Sons".
  • The BarCamp Hamburg 2012 session Slideshare "Frank Sons: Code reviews - Leave your ego at the door".
• Smart Bear Software, Inc..
  • The free PDF book Smart Bear Software, Inc. "Best Kept Secrets of Peer Code Review".
  • Blog Code Review and More - The Smart Bear Blog.

• Johan Bezem - White Papers.
  • Johan Bezem "How to wield PC Lint" (PDF).
• Embedded C++.
• Green Hills, white paper "Static Analysis of Popular Open Source Internet Communication Applications".
• Ralf Holly, Approxion - Code – People – Everything".
• EN.Wikipedia "User:Nickj".
  • EN.Wikipedia "User:Nickj/List of tools for static code analysis".
• EN.Wikipedia "Syntactic sugar", DE.Wikipedia "Syntaktischer Zucker".

• DevExpress Forums.
• Gimpel Software Forum.
• Google Groups "Clean Code Developer" by clean-code-developer.de - Prinzipien und Praktiken für bessere Software.
• MISRA Bulletin Board.
• Software Quality Connection by SmartBear Software.
• XING "Clean Code Developer" by clean-code-developer.de - Prinzipien und Praktiken für bessere Software.