DATABASE DEVELOPMENT LIFE CYCLE - Database Design and Development: An Essential Guide for IT Professionals - page 106

Critical Planning Issues
While preparing the database plan, the staff preparing the plan must be continu-
ously watchful for special challenges and critical issues. Database design and devel-
opment is not a common or easy project. Several new challenges will arise, and
sufficient awareness and planning for the contingencies are necessary. Let us briefly
go over a few of the major issues.
Data Ownership If your organization is making the transition from a file-oriented
data system to a database system, then you will be faced with resolution of data
ownership conflicts. Even when a database project consists of conversion from one
type of database system to another, some data ownership conflicts remain. Who
owns the data in the database? Which user groups are responsible? You know that
the database is for information sharing. No one group has exclusive ownership. Then
who is responsible for data quality? For example, many user groups would be adding
and updating customer data. Which user group owns customer data? Your planners
must recognize potential data ownership conflicts and review general principles
applicable to your organization.
Specialized Skills As already mentioned, implementation and maintenance of
database systems require specialized skills. You need people trained in data admin-
istration, database administration, data modeling, database design, database man-
agement systems, and programming in a database environment. The database plan
must consider issues relating to recruitment and training of personnel throughout
the entire DDLC.
Project Vulnerability For most organizations, when they undertake a database
project they are breaking into new ground. They have not faced many of the issues
and challenges posed by a database project. Possibilities exist for failures, delays,
and cost overruns in such a novel project. Planners ought to recognize the possi-
bilities for failures and suggest preventive measures and remedial action. For
example, if project failure is possible because of the spread of user groups over many
locations, planning must specifically address how to bring about cooperation and
collaboration.
New Overhead Costs Be prepared for additional overhead costs. Some of these
costs may be for additional hardware infrastructure; some may be for enhancing the
operating system software; a large chunk of additional overhead costs may be for
people with new specialized skills. Plan for such new overhead costs.
Issues for Large Projects Large projects pose particular challenges. A large
database project covers numerous user groups, extremely big data volumes, a huge
number of anticipated database transactions, and data about several business
objects. Many database professionals and user representatives participate in a large
project. When the size and scope of a project is huge, communication among the
designers, developers, administrators, and user representatives may be a source of
potential problems. Coordination and control could be difficult. Staff retention for
the entire duration of the project is another area for concern. Recruitment and