When an organization undertakes a major Information Technology project, most executives, managers, and project sponsors overlook an important component in the total cost of ownership equation; “maintenance and enhancements“. I am not referring to software, hardware, and cloud hosting maintenance fees. When capitalized dollars are used as the funding source for the project, due diligence is given to these items as these costs are folded into the depreciation schedule associated with the endeavor. I am referring to the steady state costs. Based on the architecture and design patterns employed in the project, what are the future carrying expenses as enhancements and maintenance activities are performed?
There has been a lot of chatter lately on the various forums discussing the merits of an architect. Specifically, the question being raised have architects out lived their usefulness? I for one see the use of the term Architect overused. Hence thats why there is an emerging movement for an adoption of industry standards and certification. There are specialists within the domain of Information Technology. I would assert that people who specialize in enterprise class data modeling and infrastructure should be considered architects. Vendors, however, who want to impress their prospective clients with the notion that members of their pre-sales team are solution architects, I mean really.