Comments on: 11. Don’t Raise the Drawbridge http://www.soabloke.com/2009/01/12/11-dont-raise-the-drawbridge/ pushing soa up the slope (with a pointy stick) Tue, 30 Nov 2010 19:23:34 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Saul http://www.soabloke.com/2009/01/12/11-dont-raise-the-drawbridge/comment-page-1/#comment-285 Saul Thu, 22 Jan 2009 05:58:43 +0000 http://www.soabloke.com/2009/01/12/11-dont-raise-the-drawbridge/#comment-285 I couldn't agree with you more, Marc. I'll also point to the <a href="http://www.opengroup.org/architecture/togaf8-doc/arch/" rel="nofollow">TOGAF</a> definition: "The primary reason for developing an enterprise architecture is to support the business by providing the fundamental technology and process structure for an IT strategy. This in turn makes IT a responsive asset for a successful modern business strategy." which nicely includes business, technology and organization. I couldn’t agree with you more, Marc. I’ll also point to the TOGAF definition:

“The primary reason for developing an enterprise architecture is to support the business by providing the fundamental technology and process structure for an IT strategy. This in turn makes IT a responsive asset for a successful modern business strategy.”

which nicely includes business, technology and organization.

]]> By: Marc Caltabiano http://www.soabloke.com/2009/01/12/11-dont-raise-the-drawbridge/comment-page-1/#comment-284 Marc Caltabiano Thu, 22 Jan 2009 03:31:48 +0000 http://www.soabloke.com/2009/01/12/11-dont-raise-the-drawbridge/#comment-284 Saul, I have discussed something similar to this at http://lightbulbeffect.blogspot.com/2008/06/what-is-all-fuss-about-enterprise.html The role of the Enterprise Architect, In short. The EA should linking BUSINESS (financial and market goals), TECHNOLOGY (products, vendors, and functionality) with ORGANISATIONAL (people or process) to drive an ongoing strategy or desired outcome. Marc Saul,

I have discussed something similar to this at http://lightbulbeffect.blogspot.com/2008/06/what-is-all-fuss-about-enterprise.html

The role of the Enterprise Architect, In short. The EA should linking
BUSINESS (financial and market goals),
TECHNOLOGY (products, vendors, and functionality) with
ORGANISATIONAL (people or process)

to drive an ongoing strategy or desired outcome.

Marc

]]> By: Barry Steele http://www.soabloke.com/2009/01/12/11-dont-raise-the-drawbridge/comment-page-1/#comment-278 Barry Steele Mon, 12 Jan 2009 23:39:27 +0000 http://www.soabloke.com/2009/01/12/11-dont-raise-the-drawbridge/#comment-278 Hey Saul, You want high powered blue suits, focussed on career promotion and advancement to actually be interested in the workings of the organisation? Lotsa luck with that! BUT, you are 100% accurate solution architecture must incorporate the information, process and social context of the problem space. And "Why are we doing this, again?" is a great question. And if you can get that suit to answer the question fully, you are a genius. And I would sack most IT departments. Hey Saul, You want high powered blue suits, focussed on career promotion and advancement to actually be interested in the workings of the organisation?

Lotsa luck with that!

BUT, you are 100% accurate solution architecture must incorporate the information, process and social context of the problem space. And “Why are we doing this, again?” is a great question.

And if you can get that suit to answer the question fully, you are a genius.

And I would sack most IT departments.

]]> By: Business Analyst http://www.soabloke.com/2009/01/12/11-dont-raise-the-drawbridge/comment-page-1/#comment-277 Business Analyst Mon, 12 Jan 2009 07:52:33 +0000 http://www.soabloke.com/2009/01/12/11-dont-raise-the-drawbridge/#comment-277 I could not agree with you more! Every enterprise architect and enterprise analyst must, first and foremost, have an understanding of the "Why?" They need to understand the rational as to why their services are needed. From there - their goal is to apply their craft to fulfill the business need or solve the business problem. - Adrian I could not agree with you more! Every enterprise architect and enterprise analyst must, first and foremost, have an understanding of the “Why?”

They need to understand the rational as to why their services are needed. From there – their goal is to apply their craft to fulfill the business need or solve the business problem.

- Adrian

]]>