The industry as a whole has been attempting to define Services Oriented Architecture (SOA). The definition of SOA may wary based on the responsibility of the individual. It is therefore necessary to understand the responsibilities of the stakeholders before defining SOA. The following link to the document is an attempting at identifying the various stakeholders.
http://www.soablueprint.com/whitepapers/SOAStakeHolders.pdf
Monday, July 24, 2006
Monday, July 10, 2006
Enterprise Architects - Roles and Responsibilities
As companies are starting to adopt SOA, one of the questions they keep attempting to answere is "what are the roles and responsibilities?" of an enterprise architect. My thoughts on the role of an enterprise archtiect are available at http://www.soablueprint.com/whitepapers/EARolesAndResponsibilities.pdf
Subscribe to:
Posts (Atom)
-
The purpose of this blog is to get some validation for how I look at Business Processes vs. Business Services. In simple terms, I differen...
-
A lot has been said about how SOA and EDA are unique "architecture styles". It seems like only one or the other architectural prin...
-
One of the key ingredient for success is clearly defining the roles and responsibilities within IT. There are multiple stake holders in IT w...