Skip to main navigation Skip to search Skip to main content

Identifier naming conventions and software coding standards: A case study in one school of software

  • Yanqing Wang*
  • , Shengbin Wang
  • , Xiaojie Li
  • , Hang Li
  • , Jin Du
  • *Corresponding author for this work
  • School of Management, Harbin Institute of Technology

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Within software coding standards, identifier naming plays an important role. Identifier naming conventions were divided into four categories in our research - Hungarian, Pascal, Camel and Underscore. Such techniques in compiler theory as regular expression and lexical analysis were used to extract identifiers and to match them with the defined naming conventions in our evaluation system. The consistency of identifier naming was calculated with standard deviation. After testing students' projects in three years and three pedagogical websites in which there were lots of Java files, the evaluating system were proved applicable and some conclusions were made based on the testing results as well.

Original languageEnglish
Title of host publication2010 International Conference on Computational Intelligence and Software Engineering, CiSE 2010
DOIs
StatePublished - 2010
Externally publishedYes
Event2010 International Conference on Computational Intelligence and Software Engineering, CiSE 2010 - Wuhan, China
Duration: 10 Dec 201012 Dec 2010

Publication series

Name2010 International Conference on Computational Intelligence and Software Engineering, CiSE 2010

Conference

Conference2010 International Conference on Computational Intelligence and Software Engineering, CiSE 2010
Country/TerritoryChina
CityWuhan
Period10/12/1012/12/10

Keywords

  • Coding standards
  • Identifier naming convention
  • Regular expression
  • Software metric
  • Software quality assurance (SQA)

Fingerprint

Dive into the research topics of 'Identifier naming conventions and software coding standards: A case study in one school of software'. Together they form a unique fingerprint.

Cite this