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…