| Auto-generated source code is in separate directories from other source code. |
|
|
|
0.2 |
0.3 |
0.4 |
0.5 |
0.6 |
0.6 |
| Coding standards are recommended by the project. |
|
|
0.1 |
0.1 |
0.2 |
0.3 |
0.4 |
0.5 |
0.5 |
| Coding standards are required to be observed. |
|
|
|
0.1 |
0.1 |
0.3 |
0.4 |
0.5 |
0.5 |
| How to regenerate the auto-generated source code is documented. |
|
|
|
|
|
0.2 |
0.4 |
0.5 |
0.5 |
| Project files for IDEs are provided. |
|
|
|
|
|
|
0.1 |
0.3 |
0.4 |
| Project-specific coding standards are consistent with community or generic coding standards (e.g. for C, Java, FORTRAN, Python, Ruby, etc.) |
|
|
0.1 |
0.3 |
0.5 |
0.7 |
0.8 |
0.8 |
0.8 |
| Source code comments are written in an API document generation mark-up language e.g. JavaDoc or Doxygen. |
|
|
0.1 |
0.2 |
0.3 |
0.4 |
0.6 |
0.7 |
0.7 |
| Source code is commented. |
|
|
0.2 |
0.4 |
0.6 |
0.8 |
1.0 |
1.0 |
1.0 |
| Source code is laid out and indented well. |
|
|
0.1 |
0.3 |
0.3 |
0.5 |
0.7 |
0.8 |
0.8 |
| Source code or content is structured into modules or packages. |
|
|
|
0.1 |
0.2 |
0.3 |
0.4 |
0.6 |
0.6 |
| Source code or content repository is a revision control system. |
0.1 |
0.2 |
0.3 |
0.4 |
0.5 |
0.7 |
1.0 |
1.0 |
1.0 |
| Source code structure relates clearly to the architecture or design. |
|
|
|
0.1 |
0.2 |
0.3 |
0.4 |
0.6 |
0.6 |
| Source code uses sensible class, package and variable names. |
|
|
0.1 |
0.2 |
0.3 |
0.5 |
0.7 |
1.0 |
1.0 |
| Source or content releases are snapshots of the repository. |
|
|
0.1 |
0.2 |
0.3 |
0.5 |
0.8 |
1.0 |
1.0 |
| Structure of the source code or content repository and how this maps to the software’s components is documented. |
|
|
|
0.1 |
0.3 |
0.4 |
0.6 |
0.8 |
0.8 |
| There are no old source code files that should be handled by version control e.g. “SomeComponentOld.java”. |
|
|
|
|
|
0.1 |
0.3 |
0.5 |
0.5 |
| There are no TODOs in the code. |
|
|
|
|
|
|
|
0.1 |
0.2 |
| There is no commented out code. |
|
|
|
|
|
|
|
0.1 |
0.2 |