I am the test manager on a major implementation of the Guidewire Policy Centre product. I requested a DBA to join the project. They play a fundamental role in the whole process of ensuring quality. As testers we have no idea what is done to the database in respect of quality, duplication, bad queries, normalization, indexing and a host of other potential pitfall that only DBA’s can enlighten us to. The answer from some areas is because it is a packaged product we should not be worried about the data base (Read Data) My counter argument is that we increased the tables and attributes with more than 50% because of customization. This data will be the company’s biggest asset in future. I do not want to play games with the data. The question is should I be insistent on getting a DBA on board or am I to worried? What is the counter arguments?
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!