Databases Reference
In-Depth Information
BENEFITS
The complexity that is inherent in constructing relational database so-
lutions can be reduced by using proven database development methodol-
ogies on projects. Methodologies are an excellent example of best
practices and project lessons. Use of methodologies, therefore, reduces
risk on development projects. Methodologies define activities and deliver-
ables that are constructed in projects that were successful. Following
these successful lessons can reduce project development time while in-
creasing product quality. Furthermore, the use of methodologies simpli-
fies the process of tracking project progress because there are clear
benchmarks that can be reviewed by the project manager. Methodologies
that offer templates/deliverables also allow a quickstart to the develop-
ment process.
SELECTING A DATABASE DEVELOPMENT METHODOLOGY
Development methodologies with well-defined database development
phases are commonly available in the marketplace. Some are freely avail-
able with modeling or project management tools, although others are
found on the World Wide Web. Many of the larger consulting firms have de-
veloped proprietary methodologies based on their corporate project expe-
riences and proven best practices. These can be purchased separately or
they can be bundled with consulting/mentoring services retained from the
firm. The following list identifies some of the features that should be includ-
ed in any database development methodology that is being considered for
deployment in an organization.
•
Linkage to a full lifecycle development methodology:
A full lifecycle
methodology supports more than database development. The data-
base development methodology chosen should either be a compo-
nent of a larger full lifecycle methodology, or link seamlessly with one.
Failure to do this could result in mismatched techniques or the devel-
opment of deliverables that are not used.
•
Techniques:
Many popular development methodologies support a
combination of techniques to streamline development of deliverables.
The traditional waterfall approach involves producing deliverables in
a sequential fashion. Deliverable B is not started until Deliverable A is
completed and signed off. This approach, however, historically has
proven to be slow on many projects of all sizes. As a result of this ex-
perience, a rapid application development (RAD) approach has gained
popularity in the past 10 years. RAD produces deliverables in a much
smaller timeframe than the older waterfall approach. Iteration and
prototyping are cornerstones of most RAD approaches, as are teams
that combine technical resources and users during the analysis and
design phases of the project lifecycle. RAD has proven to be successful
on smaller projects, but has been problematic on the larger ones due
Search WWH ::
Custom Search