Databases Reference
In-Depth Information
a mapping between the logical data model with a user interface and re-
ports to identify gaps.
•
Conversion Strategy:
This is a statement of the strategy used to convert
data into a new application. The level of detail can vary signficantly.
This could be anything from high-level principles to detailed conver-
sion scripts.
TOOLS
Modeling tools are critical for the database development process. There
are a number of tools with various add-ons that can be used in this pro-
cess. Modeling tools should offer support for both data models and pro-
cess models. It also is becoming more useful for modeling tools to support
object models or to link to other tools that do. Tools that support reverse-
reengineering from physical databases to generate logical data model or
scripts are useful for organizations that require extensive changes to data
structures (possibly following a corporate merger).
There are many other tools that are useful in the database development
process. Some of these include CASE tools, conversion tools, testing tools,
and database server tools.
ORGANIZATION
When staffing a project that involves a data initiative, it is necessary to
fill specific roles. The roles defined in this section are generally specific to
the data initiative. These roles often are complemented by other roles in
full implementation projects. Projects that have high object-oriented con-
tent skew the organization towards object-modeling skillsets.
•
Project Sponsor:
Projects should not be initiated or conducted without
a senior project sponsor who is positioned to remove obstacles and
ensure that the project team has the full support they require to be
successful.
•
Project Manager:
The project manager is in charge of the entire project,
including the data initiative.
•
Business User:
This person provides the business rules for the applica-
tion, which are used to derive the entities and attributes necessary to
save the data.
•
Business Analyst:
The business analyst provides a critical link between
the business user and the data architect by understanding the busi-
ness requirements and translating them into technical words.
•
Data Architect:
This person has the responsibility of defining the data
architecture. This could be distributed, central, standalone, or inte-
grated with a sophisticated overall architecture.
•
Data Analyst:
The data analyst works with the business analyst to
build a consistent view of each element of the data. This person
Search WWH ::
Custom Search