The Architect Roles in an Enterprise

Enterprise Architect, Business Architect, Data Architect, Service-Oriented Architect, Cloud Architect, Information Architect, Technology Architect – etc. OH MY!! How many more architects in an enterprise can you label? Google has 11,400,000 entries for the term “Enterprise Architect” alone.

Perhaps the “correct” definition is entry number 8,457,394 – just kidding, of course. Not much help? Perhaps you look for a definition on the first page of your favorite “search engine.” Perhaps experiencing “confirmation bias.” Let us get through this madness and bring proven methods into play.

The Enterprise Architecture Center Of Excellence (EACOE), through our thousands of Architecture client engagement experiences, identified and defined twelve Architecture Modeling Roles in an Enterprise.

These Architecture Modeling Roles are:

• Mutually exclusive – providing clear role responsibility, and

• Complete, no loose ends or unassigned gray areas to be overlooked or to be a source of concern.

Organizations can use the Architecture Modeling Roles in conjunction with

• The Enterprise Framework™ provides a frame of reference, and

• The Enterprise Framework Practitioner’s Guide – available to EACOE Certified Enterprise Architects - provides guidance for each Architecture Modeling Role.

For each Architect Role, the EACOE defines the Architecture Role Support Elements an organization will need to begin successfully modeling its Enterprise Architecture. This guidance includes;

• Role responsibilities and common Architecture Role interactions

• Architecture element naming standards

• Graphical notations that are “human consumable”

• Definition Templates for complete, non-redundant deliverables

This webinar will provide an overview of this important and unprecedented work, professionalizing and providing a consistent understanding of these vital skills an enterprise and its architects need.

Please fill out the form below to download the 2-page PDF.