We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Enterprise Architecture Matters

Adrian Grigoriu

Requirements, Strategy and Enterprise Architecture

Vote 0 Votes
Requirements apply to projects rather than to Enterprise Architecture. 

 It is the strategy concept that applies to the EA, rather than the requirements one. 

The strategy team (which usually, is not the same as the EA team), is responsible for putting together the goals and the directions of enterprise transformation in order to realise the desired enterprise state and vision.  

Theses strategic directions are then analysed and implemented by Programs/Projects, executed by transformation teams, which will collect their own Requirements.

The EA would not collect the requirements for these individual programs, at least because it will not be able to.

 The EA could be seen though as implementing the requirements of all the individual programs gathered under the enterprise transformation portfolio that executes the strategy. 

Hence, the requirements concept does not apply to EA. 

 From this point of view, TOGAF ADM represents a project delivery rather than an EA development process. In TOGAF, strategy is seldom mentioned, if at all. 


| Leave a comment

Strategy or requirement ?
I think that we need both. At the end, the requirements have to be satisfied, in accordance with the strategy.

When you say that EA will not collect the requirements, do you mean the EA team or EA as a transformation process ?
How can you be successful without knowing and covering the requirements ?

And, strategy is mentioned in Togaf. But, it is supposed that you already have a strategy before starting an ADM cycle.

Renaud, an enterprise transformation effort is greater than EA. The transformation projects collect requirements.

If TOGAF claims to be an enterprise transformation process and all, why does not aim to implement the strategy?

I hope you don't use TOGAF.

Leave a comment

Adrian Grigoriu blogs about everything relating to enterprise and business architecture, SOA, frameworks, design, planning, execution, organization and related issues.

Adrian Grigoriu

Adrian is an executive consultant in enterprise architecture, former head of enterprise architecture at Ofcom, the spectrum and broadcasting U.K. regulatory agency and chief architect at TM Forum, an organization providing a reference integrated business architecture framework, best practices and standards for the telecommunications and digital media industries. He also was a high technology, enterprise architecture and strategy senior manager at Accenture and Vodafone, and a principal consultant and lead architect at Qantas, Logica, Lucent Bell Labs and Nokia. He is the author of two books on enterprise architecture development available on Kindle and published articles with BPTrends, the Microsoft Architecture Journal and the EI magazine. Shortlisted by Computer Weekly for the IT Industry blogger of the year 2011.

Recently Commented On

Monthly Archives