java代码规范（Java code specification）.docVIP

java代码规范（Java code specification） Coding specifications are important for developers for several reasons: 1. in a software life cycle, 80% of the cost is in maintenance 2., almost no software, throughout its life cycle, is maintained by the original developer 3. coding standards can improve the readability of software, allowing programmers to understand new code as quickly and thoroughly as possible 4., if you release the source code as a product, you need to make sure that it is packaged well and clearly, just like any other product you have built 5. provide standard code formats for different project groups or individuals. 6. increase readability. After more than two years without Java, I was transferred to Java development because of the need of work. For this reason, I sorted out the following coding standards so that I could follow them in the future. Naming rules 1) package: naming should be all nouns or noun phrases. All lowercase words are separated by .. The general use of the company / organization domain name is inverted, followed by the specific internal module name of the software Package naming example: package com.sun.java; package com.mycompany.db; 2): a noun or a noun phrase, each word capitalized; generally do not use abbreviations, unless the abbreviation is more general and easy to understand, such as the HTML; when the difference between interface and implementation class, the class can add Impl, for example: interface Container and class ContainerImpl; Exception the use of Exception as the end, for example: class named DataNotFoundException; abstract class Abstract start, for class names such as: AbstractBeanDefinition, AbstractBeanFactory; Test is best to use Test end class named. For example: ContainerTest Class naming example: class Person; class SpringRain 3) interface: naming rules for the same class Interface naming example: interface Runner; 4) method: verb or verb phrases, initial letters, lowercase, second and later words first letter