A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
Pre-physical data base design heuristics
Information and Management
Justifying database normalization: a cost/benefit model
Information Processing and Management: an International Journal
A Flexible Cost Model for Abstract Object-Oriented Database Schemas
ER '02 Proceedings of the 21st International Conference on Conceptual Modeling
Decomposition of Relationships through Pivoting
ER '96 Proceedings of the 15th International Conference on Conceptual Modeling
Proceedings of the Thirtieth international conference on Very large data bases - Volume 30
VLDB '04 Proceedings of the Thirtieth international conference on Very large data bases - Volume 30
DB2 design advisor: integrated automatic physical database design
VLDB '04 Proceedings of the Thirtieth international conference on Very large data bases - Volume 30
Automatic SQL tuning in oracle 10g
VLDB '04 Proceedings of the Thirtieth international conference on Very large data bases - Volume 30
Optimising abstract object-oriented database schemas
ER'06 Proceedings of the 25th international conference on Conceptual Modeling
| Hi-index | 0.00 |
In the traditional waterfall approach for building a software application, the phases of requirements analysis, design, implementation, testing, and maintenance follow one another. Aiming at the efficiency of a database application, we see that the outcome of the implementation phase decisively determines how much time the execution of queries and updates requires and how much space is needed to store the application data. But, these costs of the application result from decisions made not only in the implementation phase but also before that during the design phase. In this paper, we describe a tool to support the cost-based design of database applications. Based on earlier research where we designed a cost-model for an abstract object-oriented database machine, the tool shall provide its user with cost estimates during the design phase. We discuss which modifications and additions to our cost-model we use to build the tool. Specifically, we portray how we adapt the tool to a concrete DBMS. After picturing a design process that employs our tool, we conclude by assessing the achievements of the present work and how we benefited from our earlier underlying research.