Development Standard Cheat Sheet

Many large implementations which we took part in, have volumes of development standards document which nobody reads. Truly, one need to be a saint to read 50+ pages of text and memorize intricacies of naming. What we find useful, is having a cheat-sheet with most ‘critical’ standards whose violation render severe damage to the development process. Adjusted to my current implementation the cheat sheet or survivor’s guide looks like this.

1. Name for any custom object should start with ‘[customer_tech_name]_[gap_number]_’ with proper casing, i.e. Profile Name ‘BOLINF_4000_SAMPLE’
2. User name for any custom object should start with ‘[customer_short_name]: ‘, i.e Profile User Name ‘MB: Sample Profile’
3. Any custom object which requires registration to an application must be registered to ‘Custom Application’, i.e. Profile Application
4. Any custom PL/SQL procedure should not exceed 4 printed pages, otherwise PL/SQL procedure must be re-factored into smaller procedures
5. Any custom Java method should not exceed 1 printed page, otherwise Java method must be re-factored into smaller methods or classes
6. Any business logic of a professional form must reside in the database PL/SQL packages so that it can be reused by non-forms gaps, such as data conversion. Likewise, any business logic of OAF page must reside in the database PL/SQL packages.
7. No loose procedure or functions. All procedures or functions must be packaged.
8. MD120 must have no manual steps except for validation
9. Each development object must have its own installation file, i.e. do not install multiple views with one file
10. File name for an object must reflect the name of the object, i.e. BOLINF_4000_SAMPLE.ldt rather than BOLINF4000A.ldt