| Revision as of 07:03, 7 May 2007 edit192.165.213.18 (talk) →Responsibilities of Enterprise Architects← Previous edit | Latest revision as of 17:10, 5 May 2018 edit undoChiveFungi (talk | contribs)Extended confirmed users2,615 edits This article is about what an enterprise architect does, i.e. enterprise architecture. There's no need for two articles on the same topic - so redirect per WP:BOLDTags: New redirect 2017 wikitext editor | ||
| (195 intermediate revisions by more than 100 users not shown) | |||
| Line 1: | Line 1: | ||
| ⚫ | #REDIRECT ] | ||
| {{Otheruses4|the job title|the UML modeling tool Enterprise Architect|Sparx Enterprise Architect}} | |||
| '''Enterprise Architects''' are practitioners of ]; an ] discipline that operates within large enterprises. | |||
| ==Role of Enterprise Architects== | |||
| Enterprise architects work with stakeholders, both leadership and subject matter experts, to build a holistic view of the organization's strategy, processes, information, and information technology assets. The role of the Enterprise Architect is to take this knowledge and ensure that the business and IT are in alignment. The enterprise architect links the business mission, strategy, and processes of an organisation to its IT strategy, and documents this using multiple architectural models or views that show how the current and future needs of an organisation will be met in an efficient, sustainable, agile, and adaptable manner. | |||
| Enterprise architects operate across organisational and computing "silos" to drive common approaches and expose information assets and processes across the enterprise. Their goal is to deliver an architecture that supports the most efficient and secure IT environment meeting a company's business needs. | |||
| Enterprise architects are like city planners, providing the roadmaps and regulations that a city uses to manage its growth and provide services to its citizens. In this analogy, it is possible to differentiate the role of the system architect, who plans one or more buildings; software architects, who are responsible for something analogous to the HVAC (Heating, Ventilation and Air Conditioning) within the building; network architects, who are responsible for something like the plumbing within the building, and the water and sewer infrastructure between buildings or parts of a city. The enterprise architect however, like a city planner, both frames the city-wide design, and choreographs other activities into the larger plan. | |||
| Delivered successfully, an enterprise architecture has the potential to allow both the Business and IT strategies to enable and drive each other. Therefore, effective enterprise architecture may be regarded as one of the key means to achieving competitive advantage through information technology. | |||
| ==Skills and Knowledge== | |||
| *] - the ability to see how parts interact with the whole (big picture thinking) | |||
| *Knowledge of the business for which the enterprise architecture is being developed | |||
| *Interpersonal and leadership skills - servent leadership, collaboration, faciliation, and negotiation skills | |||
| *] - self awareness, confidence, ability to manage conflict, empathy | |||
| *Communication skills, both written and spoken | |||
| *Ability to explain complex technical issues in a way that non-technical people may understand | |||
| *Knowledge of IT governance and operations | |||
| *Comprehensive knowledge of hardware, software, application, and systems engineering | |||
| *Project and program management planning and organisation skills | |||
| *Knowledge of financial modeling as it pertains to IT investment | |||
| *Customer service orientation | |||
| *Time management and prioritisation | |||
| ==Collaboration== | |||
| The Enterprise Architect often closely collaborates with: | |||
| *] | |||
| *] | |||
| *] | |||
| *] | |||
| *] | |||
| *] | |||
| *] | |||
| *] | |||
| *] | |||
| *] | |||
| *] | |||
| To be successful in large organisations, enterprise architecture requires a top-level mandate, executive buy-in, tools, deliverables, formal structures and governance, and resourcing. Other factors for success include business unit stakeholder buy-in, a non-centralist approach (federated effort with central coordination only), a strong theoretical base (get the basics right), a practical focus (avoid dogma), adaptable tools (evolve constantly), user and “business owner” feedback loops, as well as reinforcement through measurement. | |||
| ==See also == | |||
| * Other wiki articles | |||
| ⚫ | |||
| ==References== | |||
| * | |||
| * | |||
| * IBM Developer Works: | |||
| * Daljit Banger , British Computer Society, March 2006 | |||
| ==External links== | |||
| * | |||
| * | |||
| * | |||
| * | |||
| * | |||
| ] | |||
| ] | |||
| ] | |||
Latest revision as of 17:10, 5 May 2018
Redirect to: