# General guidelines

- Do not use reserved java words.
- Do not use spaces.
- Do not abbreviate.
- Do not use punctuation.
- Do not start the name with a number.

Here are our project guidelines for naming properties:

- Generally, do not abbreviate. The exceptions are SA, and SP, for when the name would get too long if written as is. For example: `ServiceAgreement`, as part of a much longer field name.
- In line with the above, spell out `amount` and `total`.
- Boolean values (SW) are prefixed with `is`, `has`, `can`, `are`, or `should`, according to what is grammatically correct.
- Date fields end with `Date`.
- Time fields end with `Time`.
- Datetime fields end with `DateTime`.
- Id is spelled `Id`.
- Do not include a final Flag (FLG) or Code (CD).
- Use `min` instead of minimum, and `max` instead of `maximum`.
- Can be generic. That is, for the field `BILL_STATUS`, you can just name it `status`.

Parent topic: Naming Standards