It's strange how little things like this are overlooked. And this is so incredibly important. Taking the little extra time to develop a business layer properly can save monumental amounts of time later in the project. Even an improperly developed business layer can help save time! I've worked with senior developers that have opted to have basically the same business logic in several different pages instead of placing the code in a centralized area. The thought was that time would be saved if they just wrote the business logic in the page's code behind. And, honestly, they probably did save time initially, but the cost of the decision to "save time" up front has often cost companies unimaginable amounts of time later.
I think it's not only important to point out that the code in a business object is reusable, which will save time when you're developing something similar, but to state what this means for the project down the road: sweeping changes to a site can be made in a small amount of time by developing and referencing a business layer; if the business layer is not referenced for business logic a "simple" change to a site can end up taking far longer than one would imagine. I prefer changing a single line of code in the business layer than trying to find where each reference to a similar piece of logic might be, changing it, testing it, releasing it and then realizing that I had forgotten other pieces of code. Then you have to roll back, retest, etc, etc, etc...
A business layer will help save you time in the long run. It will also help save you from annoying inconsistencies that the customer will find and point out, which will make the customer and your superiors lose trust in you. If you're unfamiliar with the differences in layers, check out http://dofactory.com/Patterns/Patterns.aspx[dofactory]
Last Visit: 31-Dec-99 18:00 Last Update: 21-May-24 5:04