by Daniel M
The article i read was about proper naming standards for data modeling. One of the most important things that the article says is that you need to be concise and clear when naming your entities. This allows for people other than yourself to be able to understand what is being named and how you have the structure set up. The article also says that an abbreviation list should be used if you are abbreviating the names of entities. this will allow you or anyone else to go back and look up what you are referring to. The organization that you are working for should also have a clear process in place of how to create new abbreviations. The article also talks about how there should be a consistent rule in place of where to put hyphens if you are using them. There also should be a standard set if you are capitalizing anything in the names, whether it be the entire name or just the first letter.
Basically this article was all about being consistent and having rules set up for your naming of entities. This is very important to us as a class because setting the foundation for naming at the very beginning will allow us to create good habits and not have to try to change the way we name stuff in the future. The other topic that this article brought up was to make sure that the organization that we eventually work for has a clear cut naming standard set up so that all the developers can easily understand and use the same naming process.
The other reason this article is important is because it stresses consistency in naming. If you name one entity Customer First Name, don’t use Cust_last_name as the last name. You need to keep a consistent naming standard. If you don’t use an underscore in the first name, then don’t use one in the last name. If you capitalize all the first letters then you need to keep it that way through all the like entities. Consistency is the key.
Hoberman, H. (2007, July 10). [Web log message]. Retrieved from http://www.tdan.com/view-featured-columns/5091