Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 20.10

VA Java Programming Standard
VA Java Programming Standard Standard or Specification

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Documentation: Please view the Reference tab.
Description: The VA Java Programming Standard consists of four broad categories of coding standards:
  • Naming - The very first aspect of development that requires convention is how development artifacts are named. Consistent and proper naming of packages, types, variables, and other code artifacts will help to ensure that any skilled Java developer can pick up a piece of code and understand its function.
  • Documentation - All languages provide the ability to create inline comments, which can be viewed while looking through the code. Java also provides the ability to formally document code inline, in a manner that allows for that documentation to be extracted and presented in the form of a browsable reference guide.
  • Style - Coding style for most developers is a matter of preference. However, there are certain coding conventions that should be standardized to ensure proper readability and to produce software artifacts that are easier to maintain.
  • Design - Though detailed design is outside of the scope of this document there are some coding standards and conventions related to design, which can be outlined that may lead to defects. An example is the use of Boolean.TRUE, Boolean.FALSE as opposed to new Boolean(true), new Boolean(false).
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:
Decision: Approved. This entry has been approved for general use.
Decision Constraints:

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v19.12
Decision Date: 12/05/2019
Introduced By: Enterprise Program Management Office (EPMO) TRM Team
- The information contained on this page is accurate as of the Decision Date (12/05/2019).