Design reviews are an important facet of the system development life-cycle for database applications. It is during the design review that all aspects of the database and application code are reviewed for efficiency, effectiveness, and accuracy. It is imperative that all database applications, regardless of their size, are reviewed to assure that the application was design properly, efficient coding techniques were used, and the database is accessed and modified correctly and efficiently. The design review is an important process for checking the validity of design decisions and correcting errors before applications and databases are promoted to production status.
But still there are sometimes many companies will skip this process due to the following reasons:.
1) Lack of understanding: First we need to understand the requirements of the users. Why do they want a database? What is it supposed to achieve? What real-world process is it designed to emulate? Then we need to actually create a technical solution "a set of tables, complete with columns, each of which has the correct data type. Sometimes these things were not cleared and the company wants to start the work on priority as the company has timelines to complete the project.
2) Effect of Cost: It is true that the costs and benefits of sustainable design can and should be analyzed holistically, including operations and maintenance implications, user productivity and health, design and documentation fees, among other financial measurements. We conclude that many projects achieve sustainable design within their initial budget, or with very small supplemental funding. This suggests that owners are finding ways to incorporate project goals and values, regardless of budget, by making choice. Substantial hardware and software start-up costs also affect this. Extensive conversion costs in moving form a file-based system to a database system.