| Standard id |
Standard |
Clasification |
| ARM_COS_1 |
Select the programming language appropriately to meet the documented requirements of the system |
Mandatory |
| ARM_COS_2 |
Indent code for better readability |
Mandatory |
| ARM_COS_3 |
Establish a maximum line length for comments and code to avoid horizontal scrolling of editor window |
Mandatory |
| ARM_COS_4 |
Use space after each comma, operators, values and arguments |
Mandatory |
| ARM_COS_5 |
Break large, complex sections of code into smaller comprehensible modules/ functions |
Recommended |
| ARM_COS_6 |
Arrange and separate source code between files |
Recommended |
| ARM_COS_7 |
Choose and stick to naming convention |
Recommended |
| ARM_COS_8 |
Avoid elusive names that are open to subjective interpretation |
Recommended |
| ARM_COS_9 |
Do not include class names in the name of class properties |
Recommended |
| ARM_COS_10 |
Use the verb-noun method for naming routines |
Recommended |
| ARM_COS_11 |
Append computation qualifiers (Avg, Sum, Min, Max, Index) to the end of a variable name where appropriate |
Recommended |
| ARM_COS_12 |
Use customary opposite pairs in variable names |
Recommended |
| ARM_COS_13 |
use mixed-case formatting to simplify reading |
Recommended |
| ARM_COS_14 |
Boolean variable names should contain Is which implies Yes/No or True/False values |
Recommended |
| ARM_COS_15 |
Avoid using terms such as Flag when naming status variables, which differ from Boolean variables in that they may have more than two possible values |
Recommended |
| ARM_COS_16 |
Even for a short-lived variable that may appear in only a few lines of code, still use a meaningful name. Use single-letter variable names, such as i, or j, for short-loop indexes only. |
Recommended |
| ARM_COS_17 |
Develop a list of standard prefixes for the project to help developers consistently name variables |
Recommended |
| ARM_COS_18 |
For variable names, include notation that indicates the scope of the variable |
Recommended |
| ARM_COS_19 |
Constants should be all uppercase with underscores between words |
Recommended |
| ARM_COS_20 |
Wrap built-in functions and third-party library functions with
your own wrapper functions
|
Recommended |
| ARM_COS_21 |
Report error message and recover or fail gracefully |
Recommended |
| ARM_COS_22 |
Provide useful error messages |
Recommended |
| ARM_COS_23 |
When modifying code, always keep the commenting around it up to date |
Recommended |
| ARM_COS_24 |
At the beginning of every routine, it is helpful to provide standard, boilerplate comments, indicating the routine's purpose, assumptions, and limitations |
Recommended |
| ARM_COS_25 |
Avoid adding comments at the end of a line of code |
Recommended |
| ARM_COS_26 |
To conserve resources, be selective in the choice of data type to ensure the size of a variable is not excessively large. |
Recommended |
| ARM_COS_27 |
Keep the scope of variables as small as possible to avoid confusion and to ensure maintainability |
Recommended |
| ARM_COS_28 |
When writing classes, avoid the use of public variables. Instead, use procedures to provide a layer of encapsulation and also to allow an opportunity to validate value changes. |
Recommended |
| ARM_COS_29 |
Do not open data connections using a specific user's credentials. Connections that have been opened using such credentials cannot be pooled and reused, thus losing the benefits of connection pooling. |
Recommended |
| ARM_COS_30 |
for coding standard, follow https://bcc.gov.bd/site/page/f64470aa-1f1d-406c-a7a9-54125efb2ed3/- |
Mandatory |