Database Implementation
... in the design and the implementation process. User participation increases the understanding and acceptance of the new database and oftentimes allows the designer to detect major flaws or system failures at early stages. This is cost efficient and facilitates programming, testing and conversion before the database goes in production. Be sure that you also consider potential interfaces or acceptance problems from the supplier or customer side. Proper System Implementation Before a database goes in production thorough testing / simulation has to be conducted in order to ensure the proper functioning of the new system. System features and processes must be documented in order to train personnel to use the database for daily business activities. Usually old and new systems run together for a certain period of time until tests and pilot studies are successfully completed and the new database is debugged and certified to go to production. In order to limit business risk a new database may be introduced in phases. Single functional or organizational units are involved in tests and pilot studies before the new database is distributed to the whole organization. When a new data-base is in production it is important that the system is carefully monitored, secured and maintained. To accomplish op-erational objectives ensure that the database allows for modification if business needs or markets change. Data loss or system failure may painfully harm a firm’s operations resulting in higher costs, lower revenues and profits. Key findings from Nutmeg & Coke The Nutmeg article clearly shows that the test procedures before the implementation of the new database were insuffi-cient. Hardware and software failures were detected too late when the system was already in production. Since the problems occurred in Nutmeg’s busiest season the database deficiencies had a major impact on financial results. Addi-tional cost arose because internal and external resources had to make extra efforts to bring Nutmeg’s operations back on track. If the company had chosen a parallel or step-by step introduction of the new database the impact of system deficiencies could have been considerably limited. The implementation of the database was not well timed and should not occur during the peak of business activities. Apparently work f...