The question is often raised among the IT fraternity as to what should constitute IT architecture best practices. However, the answer is elusive and difficult. However there are a few processes which can make a good system work better though there is little one can do if faced with a bad legacy system.

The first step towards IT architecture best practices is design. It is imperative that enough thought is given to the vision and reason for IT implementation. Poor vision and purpose is the main reason why IT infrastructure fails to meet the practical requirements of an organization. In fact , fifty percent of the project time should be spent on design . Even before considering software or a system, it is necessary to understand the process flow. A thorough understanding of business processes is essential for IT architecture best practices . Somehow we seem to hurry through this process and then try to fix bugs as we go along the way. No doubt pressure from higher ups in the executive level , is mostly responsible . The new paradigm of fixing things as we go along seems to have given an impetuous to this hasty design process. However these are by no means to be construed as IT architecture best practices.

After creating carefully designed system architecture, we have to decide the tools, software and systems required to bring the design to fruition. Here again there is a need for understanding the present and future needs of the enterprise. A holistic view with cost, efficiency, ease of maintenance and operatability is necessary. There are many IT architectures which have a proven pedigree and can be considered.

The final bit of IT architecture best practices would consist of up gradation and portability. Though it is very difficult to predict the direction of technology in the field of IT , it should be robust enough to incorporate changes in business environment.

Ultimately IT architecture best practices means common sense. Small enterprises learn from past mistakes and word of mouth is sufficient to ensure future reliability. As far as big businesses are concerned, history is replete with examples where ad hoc decisions have led to mammoth wasteful expenditure. The blame is taken by the IT architect without analyzing the underlying issues leading to disasters. An excellent suggestion is to document the processes and steps taken while implementing large IT projects. Keeping record is among the best of IT architecture best practices. At least the blame can be shared by all instead of solely the IT department

By Jose L. Anton, CEO

(954) 840-8068