Computer Science student, web professional

Data Modeling

data with representation of relationships

Example of Data Model

I was looking for an internship and in conversation with the President, Chad Stoker, of CodeSmart Inc, he mentioned that data modeling was essential to be familiar with. This had me dive into the world of “data modeling.” I presumed it had something to do with representing data, but wasn’t sure at what level.

I did a bit of research and discovered it was in fact how we discuss, organize and then implement projects that need data stored, accessed, and manipulated. It takes business processes and computerizes them. I have done this process a number of times. I usually use the top-down method where you create relationships between data entities and then implement those in a database. This is usually followed up with some implementation in order for non-computer savvy users access and usage ability of the data. Data Modeling on Wikipedia or on Agile Data

I believe time put in at the beginning of this process of establishing the data necessary for storage, the structure and methods of access, and then how implementation will look will lead to a much quicker process of implementing the project. I have experienced that when you do not have a solid understanding of what the client/customer envisions the data’s usage to be, the less you’ll be clear on how to develop an application that will be used by that user. It is essential through drawings, examples, or any other method to have a clear concept of what is expected of processes that the client desires. Data Modeling tools

I would recommend reading a little bit about data modeling and then about computer project development prior to implementing any type of data structure that a client will be accessing via an application. Look at the different visual representations N Way FuN!

Catch ya later…

Comments on: "Data Modeling" (3)

  1. eventfulness said:

    I also think that before diving into any implementation you have to spend time designing your project/application/database. I found ER diagrams to be very useful in database design. It’s a very good practice to follow, and doing this will help during interviews as well. I’ve been previously to technical internship interviews and can tell that nobody likes if you start implementing anything before first giving it a deep thought. You have to gather all the requirements, understand them as well as the problem fully, and only then start implementing.

    • I took TCSS360 at UWT with Professor Josh Teneberg, which provided me a great understanding of the details that are needed and the check-backs required in order to have a project go as smoothly as possible.

  2. Completely agree, my dad always said that understanding the problem is 50% of the solution, and in data modeling would go even further, this is 75%, maybe even more, because it takes some understanding and solving to model it right, and then all you need is to code it (which is just being a writer). Good post.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Tag Cloud

%d bloggers like this: