|
Many data base design software goes far beyond only modeling
database structures. Some can be used to model a business
process, construct a database from a model, and generate forms
and database links for an application. There are several different
forms. Some for design and to construct the database, some
are used for data warehouse design and construction, building
applications, and maintaining and exchanging model information
among the tools and among users working together in a team
environment. You can pick and choose which pieces you want
to use for framework to create and maintain your applications,
based on how it fits into your development environment.
During the beginning application development
stages, one should figure out which business processes database
applications will be built and how the data needs to be moved.
Though you may choose only one method for your analysis, you
can usually change in midstream so your existing information
will be automatically converted to the new method. Some modules
allow the user to specify processes; data stores (tables),
data items (fields), data flow, and control flow for the business
process. The fundamental pieces may be graphically arranged
a series of dialog boxes may be used to obtain details like
the names and attributes for data items, and processes might
be hierarchically organized, so you can create a root set
of processes, then further break them down into detail processes.
There are several features, for example, error correction.
If an error is found, clicking on the error or warning generated
by the model checker may automatically takes you to the correct
dialog box to add or change information. The reports may be
extensible, and have the ability to import into any word processor
that recognizes certain files. Other features may include
the ability to specify the effect a process has on data in
terms of create, read, update, and delete. Some modules can
also specify business rules -facts, validations, and formulas-for
process and data entities. Others can export data items, data
stores, and business rules created in a process model.
Some modules can take conceptual information to meet the
physical implementation, organize information into "entities"
(tables), and define relationships between the entities. The
following diagram, then can be taken and converted to a physical
model, which shows exactly how the entities and relationships
can be transformed into an actual database implementation.
With this feature you may be able to generate actual database
tables, fields, indexes, constraints, referential integrity
triggers, and views, (in some cases, you can use almost and
data file format).
If you do not wish to start with a conceptual model, you
may be able to populate a modules diagram by reverse engineering
an actual database. This may give one the ability to import
certain objects, preview a report and select all neighboring
objects to the object you select. Some modelers are a cross
between a physical modular and an application generator. Additional
features include the ability to extended attributes to the
tables and fields in a physical database model and apply an
application template to give the applications you generate
a specific look. Some include templates, which allow you can
modify or recreate. There is also available, modulus with
high performance indexing schemes, partitioning tools, the
ability to store your data models and generated information,
and dimensional modeling.
Copyright
© 2005 Database Design Information. Send comments here. |
 |
