Database Development Methodology and Organization - High-Performance Web Databases: Design, Development, and Deployment - page 8

understands the linkage between the business and the individual
items of data.

• Data Modeler: This person works with the data architect to build a log-

ical relational data model and also may get involved in transforming
the logical data model into a physical data model.

• Object Modeler: The object modeler becomes involved in projects to

build an object model, including messages and methods. This person
also may be responsible for mapping the object model to the corpo-
rate data model.

• Database Administrator: This person implements the physical data-

base, maintains and optimizes the physical environment, restricts ac-
cess to the database by controlling privilege levels for users, offers
advice to the development team for converting the logical data model
to the physical data model, and holds the overall responsibility for
running the database environment on a data-to-day basis.

• Network Administrator: The network administrator maintains the phys-

ical network, has the responsibility for maintaining the integrity of the
physical environment that supports the data environment, and oper-
ates at the operating system level and the hardware level. For exam-
ple, this person would add more physical disk to support larger
databases.

• Developer: This person uses the database(s) for application develop-

ment.

PITFALLS

Misuse or misinterpretation of how methodologies should be executed
can result in signficantly negative impacts to project timelines. It is not un-
usual for organizations to use methodologies as process charts or recipes
without streamlining any of the activities. This can result in a considerable
amount of wasted time as deliverables or activities are produced without
an understanding of how they are leading toward a solution. Methodolo-
gies should be adjusted for specific projects. Activities or deliverables that
are not necessary should be dropped from the project plan.

Methodologies that are too complicated or difficult to learn and used
frequently are avoided by project teams. There are some methodologies
that may contain information for thousands of project contingencies. How-
ever, they require thousands of megabytes of storage or dozens of manuals
to store. During tight project timeframes, such methodologies are sidelined
quickly.

It is important to update methodologies over time. New project experi-
ences and best practices should be included in the methodology at specific
intervals.