Naming Standards

General Standards

  • Language: English
  • camelCase and PascalCase

Application

Full Name

  • PascalCase
  • [Customer/Group]:[Application]

Short Name

  • CamelCase

Application Instance

  • Similar to application name
  • include the environment

Component

  • camelCase
  • Unique Names
  • Non-generic
  • Full name contains initial application

Package

  • always start with ‘org.normalizedsystems.nsx’
  • further parts ‘customer.project.functionality’
  • use ‘.common’ for general classes

Data Element

  • PascalCase
  • Singular noun
  • Anthropomorphic
  • Do not use ‘data’ or ‘info’

Field

  • camelCase
  • Singular noun
  • No reuse of Data Element name in field name
  • Boolean field: “is/has” prefix

Finder

  • Composite finder: start every part with a capital, e.g., findByField1Eq_Field2Eq

Status

  • PascalCase
  • Past Particle
  • Status is the end state, not the start state for the next task
  • Failed state: “Failed” suffix
  • Interim state: “ing” suffix

Task

  • PascalCase
  • Singular noun derived from verb

Flow

  • PacsalCase

Command

  • camelCase
  • Verb

Custom Class Names

  • no ‘Helpers’, ‘Managers’, ‘Handlers’
  • Tests: “Test” suffix