PL/SQL Package naming standards   Oracle Tips Coriolis Publishing

PL/SQL Package naming standards

Stored procedures and functions should be named first by the type of action the object performs and then by the object of that action. For example, a procedure that calculates interest on a student's remaining balance would be named Calculate_Balance_Interest.

Packages should be named in accordance with the general purpose of the procedures and functions contained within the package. For instance, a package containing routines used to calculate a student's GPA would be named GPA_Calculations.

All documentation pertaining to system design should follow the conventions identified in this standard. This applies especially to pseudocode that is used to document stored PL/SQL objects.

In addition, all written documentation should reference calls to built-in and developer-written procedures and functions using a set of parentheses, as in ?will call the Calculate_Semester_GPA() procedure?. The names of built-in and developer-written code modules should also be referenced in bold.

This is an excerpt from "High Performance Oracle Database Automation", by Jonathan Ingram and Donald K. Burleson, Series Editor.
 

If you like Oracle tuning, you might enjoy my book "Oracle Tuning: The Definitive Reference", with 950 pages of tuning tips and scripts.  You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.