Misplaced Pages

Enterprise architect: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 11:27, 14 July 2012 editHappyuk (talk | contribs)53 edits External links← Previous edit Revision as of 04:54, 28 August 2012 edit undo173.226.246.179 (talk) Architect metaphor: Remove "architect" title protection FUD. Inaccurate, and thus not relevant. See http://www.aia.org/about/AIAB091369; CSPE v. NOVELL, etc.Tag: section blankingNext edit →
Line 39: Line 39:
*Customer service orientation *Customer service orientation
*Time management and prioritization *Time management and prioritization

==Architect metaphor==
The use of any form of the word 'architect' is regulated by 'title acts' in many states in the UK and the US, and a person must be licensed as a building architect to use it.<ref>The term "]" is a ''']''' protected by ] and restricted, in most of the world's jurisdictions, to those who are trained in the planning, design and supervision of the construction of ''']'''. In these jurisdictions, anyone who is not a licensed architect is prohibited from using this title ''in any way''. In the State of ], and in other ] states, the unauthorized use of the title "architect" is a ] and is subject to ].{{cite web|url=http://www.aianys.org/what's_legal_whats_not.pdf |publisher=AIA New York State|title=Architecture: What’s Legal, What’s Not|accessdate=9 Jul 2012}}{{cite web|url=http://www.op.nysed.gov/prof/arch/article147.htm|title= NYS Architecture:Laws, Rules & Regulations:Article 147 Architecture|accessdate=9 Jul 2012}}</ref>


==References== ==References==

Revision as of 04:54, 28 August 2012

This redirect is about the job title. For the UML modeling tool Enterprise Architect, see Enterprise Architect (Visual Modeling Platform).
This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)

No issues specified. Please specify issues, or remove this template.

(Learn how and when to remove this message)
It has been suggested that this article be merged into Enterprise architecture. (Discuss) Proposed since February 2012.

Enterprise architects are practitioners of enterprise architecture; an information technology management discipline that operates within organizations.

Role

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 organization to its IT strategy, and documents this using multiple architectural models or views that show how the current and future needs of an organization will be met in an efficient, sustainable, agile, and adaptable manner.

Enterprise architects operate across organizational 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.

Responsibilities

  • Alignment of IT strategy and planning with company's business goals.
  • Optimization of information management approaches through an understanding of evolving business needs and technology capabilities.
  • Long-term strategic responsibility for the company's IT systems.
  • Promotion of shared infrastructure and applications to reduce costs and improve information flows. Ensure that projects do not duplicate functionality or diverge from each other and business and IT strategies.
  • Work with solutions architect(s) to provide a consensus based enterprise solution that is scalable, adaptable and in synchronization with ever changing business needs.
  • Management of the risks associated with information and IT assets through appropriate standards and security policies.
  • Direct or indirect involvement in the development of policies, standards and guidelines that direct the selection, development, implementation and use of Information Technology within the enterprise.
  • Build employee knowledge and skills in specific areas of expertise.

Skills and knowledge

  • Systems thinking - 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 - servant leadership, collaboration, facilitation, and negotiation skills
  • 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 organizational skills
  • Knowledge of financial modeling as it pertains to IT investment
  • Customer service orientation
  • Time management and prioritization

References

  1. Rosen, Mike Ten Key Skills Architects Must Have to Deliver Value, November 2008

External links

Template:Misplaced Pages books

Categories: