[/caption]
Heredity is a strong factor, even in architecture. Necessity first mothered invention. Now invention has little ones of her own, and they look just like grandma. – E.B. White
Architecture standards in informational technology are critical to being able to deliver and support enterprise level systems and applications. By thinking through the standard platforms, technologies and protocols once, and then having all software and hardware adhere to these pre-defined standards numerous development and operational aspects of an IT department more efficient. It becomes easier to build reusable components. Standardized patterns can be developed. Delivery schedules will become more predictable. Integration across disparate systems will be much easier. Adopting new technology concepts can be made simpler. Investment in a technology can be maximized.
What happens when the technology platform which you have adopted is eclipsed by newer more efficient or effective technology? It is easy for this to happen. The decisions made today will have a shelf life. Vendors of software platforms are frequently purchased leaving the acquired platform in limbo. Different technologies and platforms which perform similar roles can gain more market traction leaving the chosen platform in question. New concepts, as we are currently seeing with Web2.0 technologies, can make existing standards obsolete. Grassroots movements from within the organization can cause an overwhelming demand to move in a direction that must be listened to.
For these reasons and many others it is important to keep the architecture alive. It needs to adjust with the changing environment and address new needs as they arise. In most cases once an architecture is defined it will have a long shelf life, but an annual review is in order for all IT organizations which are mature enough to develop an architecture.
