Maybe you recognize one of the following situations… Your lead programmer just left to take another job, and now you have an un-maintainable application because of his non-standard approach to development. You are asked to create a web application from an old desktop application, and you must write the whole thing from scratch because you did not take advantage of n-tier techniques when you wrote the original desktop application. Your various programmers in your organization refuse to work on each other's code, because they do not like each others code. You find that the quality of the software you get from one group within your organization is always better than another group. You have two different sets of programming standards in your organization. You find you can not justify the time you spent developing an application, or you just do not know how long an application took you to create. You find that your estimates are too often not accurate. Your software projects are always over budget and late. If any of these situations is familiar to you, then it might be time you adopted a formal architecture for your organization. The focus of this article will be on how to apply a formal IT architecture to your organization. It is not possible in one small article to go into great detail on any one topic, but you will gain a good sense of what it takes to implement a good architecture and how this architecture will solve many of the issues presented above.    lees meer...