The Database Journal
03/10/2006
Adjusting Autonumber Increments

03/10/2006
Moving Access Data to Microsoft Excel

03/10/2006
Exporting Access Data with TransferSpreadsheet

03/10/2006
Export Access Data with VBA

03/13/2006
Data Layout in Microsoft Excel

03/17/2006
Excel Text to Number Conversion

03/21/2006
Transposing Excel Ranges

03/25/2006
Access VBA Timer Event

03/29/2006
What is MySQL?

04/02/2006
Microsoft Access Parameter Query Tutorial Video

04/06/2006
How does PHP Work?

04/10/2006
Microsoft Access VBA Tools - References

Click here to view all articles.

Database Design
Website Design
Search Engine Marketing
Home
Contact Us
About Us
Database Journal
Newsletters
Database Newsletter

Database Design Interviewing

An interview? No, not for a new job, and not just for fun.

Interviewing for a database shouldn’t be a foreign concept if you’ve designed a database before. Interviewing in general shouldn’t be a foreign concept since you’ve been interviewed numerous times, although you may not have used that exact word for it. When was the last time you heard of someone walking onto a used car lot and having an exchange like this:

    Salesman: Can I help you?
    Customer: I need something with four wheels.
    Salesman: Okay, that’ll be $24,999.99.
    Customer: Okay here’s a check.

That doesn’t happen (if it did, there’d be many more car salesmen in the world). The fact is that the customer has certain expectations that need to be met and may not even know what they are. The salesman is there to ask the proper questions, do the paperwork, and smile as his client drives off the lot. Wouldn’t you expect questions like, “Do you want a sports car or a minivan?” or “Did you want that in Ocean Blue or Flaming Magma Red?”

The interview process is exactly the same when building a database for your organization or even yourself. Your client may say, “Give me something that holds information.” Sure, you could give them a database that keeps track of … well … anything, and you’ve met the expectations that they have communicated to you. But without interviewing your client beforehand, your job will be impossible, and nobody will get their expectations delivered because you don’t know what to design.

You’ve got to ask questions in order to understand what it is that’s going to be developed. Whether it’s just a casual email to some users to ask them about what they want from the database, a conference call with management, or a chat with the “resident expert” who knows everything about the business process but nothing about the technology of automating it. The more questions you ask the better the project will be because of it. Answers are what you need to take the project from concept to reality!


©2010 Blue Moose Technology, LLC

David Badurina, President of Blue Moose Technology, LLC, is a relational database design expert. David's unique ability to easily explain virtually any technical concept has allowed him to work with companies such as AMD, Motorola, the American Heart Association, and countless small businesses. Learn more about database design right now at http://www.bluemoosetech.com.

Article Publishing and Re-Print Guidelines

You can easily link to this article!

If you'd like to link to this article from your own website, copy and paste the following HTML code onto your page:

On your page, the code will appear like this:

Database Design Interviewing