Databases Reference
In-Depth Information
Figure 9-1.
Data model of the sample application
The Approach
Which elements did we consider for this approach? In order to be truly effective, we felt that we needed a
broader scope than just looking at purely source code-related issues. Thus, we developed solutions for
managing the source code (files, folders, database objects, APEX application components) as well as the
documentation and requirements.
Version Numbering Scheme and the Overall Delivery Process
As applications change over time, you have to implement and deliver new versions of the software to
your clients.
To understand the functional as well as the technical differences of each release you need a means
of communicating these differences. To accomplish that, use a specific numbering scheme to keep track
of different versions of the software. Many different approaches are possible; a good overview can be
found at
http://en.wikipedia.org/wiki/Software versioning
.
Use the following convention to assign a version number to your software:
<Major Release>.<Minor Release>.<Patch>.<Revision>
•
Major Release
: This digit is increased when there are significant jumps in
functionality, fundamentally changing application concepts' interfaces.
