Applications lay more and more on databases as long as technology provides new functionality. Databases present a characteristic that is not common to other software system components: they have contents. Data issue has been traditionally left on the end-user side. However, bad quality data may damage the application performance seriously. Even when this is simple to state a lot of problems remain behind. Assessment models do not always contemplate database development process characteristics. As we show, work products are not often those expected in a database development process. Furthermore studies on data quality are rather recent and are a not-yet-consolidated discipline. A strategy is presented to introduce some issues related to data quality in the base practices considering the proposed processes for a specific assessment model, SPICE. As we explain, these base practices and work products should be considered as extensions to the conventional assessment model, as it presents problems to support database development processes.