The software development is limited by the strict rules which are essential for the app developing companies. The naming standards are applicable to the names of the collections, files, variables, and so on. The specific sets of the naming rules of how the sequence of characters for identifiers should be chosen are commonly applicable. The identifiers denote functions, variables, various sorts of source code, and documentation entities. The naming convention in programming is applicable for standardization and is expected to satisfy specific demands.
Software and app developers are generally not supposed to use character sequences that do not satisfy the rules. The reasons for the usage of the naming convention are 1) the effort reduction during reading or comprehending the source code; 2) enabling of the tools for checking up the quality of the code, omitting style and syntax preferences; 3) conduction of code reviews for naming and syntax standards. The words in the names should be 1) easily readable, 2) focus on readability instead of brevity, 3) omit non-alphanumeric characters, hyphens, or underscores, exclude Hungarian notation, and avoid identifiers, which are largely used in most of the programming languages (Microsoft, 2017). There are basic naming rules such as the prohibition of the acronyms and abbreviations use. The use of acronyms is typically avoided except for the cases of absolute necessity. Besides, the use of the language-specific naming is advised to be avoided, and semantically unconventional names should be used instead. A generic name of the CLR type is also preferable instead of the language-specific naming in separate cases. The naming should be done based on the previous releases of the existing APIs to emphasize the relationship of the APIs. It is important to use a new but meaningful identifier rather than adding a prefix or a suffix to the original one.
Use your promo and get a custom paper on
"Naming Standards".
Overall, the naming convention is necessary to be able to identify files easily and to denote all types of entities in documentation and source code. The naming rules are mostly dogmatic and have almost no exclusions.
- Microsoft. (2017, Mar. 30). General naming conventions. Retrieved from https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/general-naming-conventions
