Devlpmnt standards - need your input

From: Scott Orman <scott_orman_at_rc.trw.com>
Date: 10 Aug 1994 15:32:14 GMT
Message-ID: <32artu$pir_at_picard.rc.trw.com>


  I have been tasked with defining our Oracle development standards and procedures. I am looking for inputs from all you experienced Oracle programmers out there. The standards I am talking about include, but are not limited to:

   PL/SQL coding standards (variable naming conventions, differentiating Oracle built-ins

           from my own procedures, indentation, internal comments, ...etc.)    Forms 4.0 coding and object naming conventions (naming conventions for non-base table

           items, push buttons, check boxes, ...etc., and coding standards like should the code for
           a trigger be placed in the trigger or should the trigger merely call a PL/SQL block and all
           trigger code maintained in the blocks?
   Forms 4.0 cross-platform "look & feel" standards (which fonts, sizes, colors are okay to use
           and how should they be used in Macintosh/Windows forms?, ideas on naming
           platform specific visual attributes and manipulating them)
   Standardized menus (what should the base Main Menu bar look like, and with what options.
           The users surely don't (and shouldn't have to) understand Blocks, for example.)
   Standardized toolbar options and implementation.    Row level security implemenation.
   Standards for documenting an application, or a Form.    Other naming conventions (SQL Plus scripts, tables, fields, procedures/functions, ...etc).  

   Basically we have a brand new clean slate that we need to fill in, and would like to do it as close to "the right way" as we can. So I welcome ANY and all opinions, suggestions, experiences, and tips. I would like to see this become a long thread that continues to be molded with new ideas and eventually get placed in the FAQ for other users.              Received on Wed Aug 10 1994 - 17:32:14 CEST

Original text of this message