This may not be a new discussion for many, but I am writing this out of recent observations when people of all walks of IT think themselves doing some kind of architectural work. Every computer programmer, system designer, IT support director, computer operator, PC owner, data architect, database architect, network architect, business analyst, systems analyst, enterprise architect, service architect, object architect, project manager calls whatever they do or want to do or maybe, whatever, they are doing as, “Architecture?" It is chaos. As John Zachman puts it, "This is killing Enterprise Architecture…". So what is Enterprise architecture from an IT perspective?
Enterprise Architecture when defined from an information and technology perspective explicitly describes an organization through a set of independent, non-redundant artifacts, defining how these artifacts interrelate with each other, and developing a set of prioritized, aligned initiatives and road maps to understand the organization, communicate this understanding to stakeholders, and move the organization forward to its desired state.
From a Business perspective, Enterprise Architecture illuminates how an organization and all of its members can achieve its objectives, through the creation of a series of engineered models and project initiatives, that can be easily understood by all of the people associated with the organization.
If an individuals contribution is to just about talk on these artifacts (or even worse BS on those) and not work towards creating them, please stop calling yourself an Enterprise Architect. May be they can be called as "Art Vandelay" Architect as in one of SeinField's episode.
No comments:
Post a Comment