Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

Database

Whence Data Quality?


Database Testing

In the September survey, 66 percent reported that they do some form of database testing. In the July survey, I asked about database regression testing, a more complicated form of database testing, and found that less than half of respondents do that form of testing. Figure 5 depicts the relationship between various forms of testing and overall database quality. Many respondents indicated that they take more than one approach to database testing, so the results are commingled. The organizations that do no database testing at all seem to be in the worst shape, which should come as no surprise. Testing at the end of the lifecycle is an improvement, but appears to be the least effective time to test—apparently we need to rethink traditional approaches. Testing at the end of each development iteration is more effective still, but taking a test-driven design (TDD) approach appears to be the best approach.

Figure 5: Database testing and data quality.

Data Modeling

The survey also asked about the approach to data modeling by project teams, and Figure 6 correlates the answers to data quality. It's interesting to note that evolutionary/agile approaches to data modeling prove to be just as effective as traditional/serial approaches, and that both approaches are better than not data modeling at all. What we don't know from the survey is how much data modeling is actually occurring. In my experience, traditional teams seem to do a lot more modeling than agile teams, so potentially, agile teams are achieving the same results as traditional teams for a smaller investment. I suspect that a more detailed study is required to tease out what is really happening.

Figure 6: Approach to data modeling and data quality.

Conclusion

These surveys have shown that we clearly have some serious problems when it comes to data quality. At www.ambysoft.com/ surveys, I have posted the source data (with the e-mails removed), the original questions, and PowerPoint slide decks summarizing critical findings from all of my surveys, including the most recent one. Please use these assets to communicate the challenges with traditional approaches to data management within your organization. Better yet, please analyze the data for yourself and report your findings back to the IT community. Now is the time to start digging ourselves out of the "data morass" that we find ourselves in.

Implications from the Survey

  1. Database service-level agreements (SLAs) appear to lead to improved data quality.
  2. A collaborative approach to data management is more effective than a command-and-control approach, which in turn, is better than no approach at all.
  3. A large percentage of organizations struggle to evolve their database schema in a timely manner, thereby reducing their competitiveness in the marketplace.
  4. The earlier, and more often, that you test your database in the development lifecycle, the greater the data quality.
  5. Evolutionary/agile approaches to data modeling are just as effective as traditional approaches, and both approaches correlated to improved data quality.
  6. —S.A.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.