Oracle Online Systems
Development Standards
This document describes a standard development environment for
APEX
systems.
Overall approach
APEX is a rapid development tool that can be used to quickly create
working prototypes during the systems analysis and systems design phase.
Each project consists of an on-site DBA and a systems designer who rapidly
develop the data model and design prototypes:
- Fast End-user Feedback -
APEX allows for the daily "Is
this what you wanted?" feedback that is critical for ensuring
that the design matches the needs of the end-user with a WYSIWIG
approach.
- Self-contained analysis & design - All analysis and
design specifications are incorporated directly into APEX,
eliminating lost documentation. A standard button at the
bottom-right or every online screen will display all analysis
specifications, documentation of the existing system, process logic psuedocode and design documents.
- Daily Development Cycles - During analysis and design, a
daily cycle will be used to created a feedback loop:
1 - Analyst and designer conduct detailed interviews.
2 - DBA creates the Oracle schema structures inside
APEX
(see standards below).
3 - Designer builds the online screen and report prototypes
using the data model from step 2.
Application Standards
Application coding standards will ensure uniformity within the application.
- Affirmative error checking - All process logic will
check all non-zero Oracle return codes.
- Standard help key
- Complete Help documentation will be
implemented with the standard F1 Help key and all online help
screens will have context sensitive (mouse-over) descriptions.
- Fast validation - All HTML screens will use Java for
instant field entry validation, before going to the database.
- Standard screen template
- A standard template will be
used for all screens, utilizing "re-usable included components, as
follows:
-
Reusable "include" HTML - header, toc and
footer.htm - A re-usable HTML component
-
Screen ID
= A unique screen ID, consisting of
the application abbreviation and a hierarchy number (e.g. DSS-1420)
-
Screen Specs - The full analysis and design
specification will be accessed by a button in the lower-right corner
of every screen. This important feature names the whole system
self-contained, and paperless.
PL/SQL Standards
All procedures
will be written in PL/SQL (Stored procedures and packages) and utilize
the
dbms_shared_pool.keep facility for caching.
Whenever possible applications should be developed
so that the database interaction is accomplished through stored
procedures and packages. This optimizes performance and standardizes
database application development independent of programming languages.
-
Compiled code - All Non Dynamic PL/SQL may be
compiled for better performance
-
Array Processing – Bulk Collects, forall and
ref cursor usage for maximum system performance
-
Secure pages
- All Secure systems areas will
use HTTPS Secure Protocol
Also see:
PL/SQL best practice Standards
PL/SQL Programming Design Standards
PL/SQL code alignment standards
PL/SQL Capitalization Best Practices Standards
