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
Practitioners observations and view on the best practices, key learning on the fast changing landscape of technology and architecture. - Strategic User of Information Technology - Cloud Computing - Big Data
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)
Key Learnings - Using EDA to implement the core SOA principle of "loose-coupling"!!!
A lot has been said about how SOA and EDA are unique "architecture styles". It seems like only one or the other architectural prin...
-
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...
-
Looks like there is a contant need to educate the industry on SOA and this time I shall take a stab at what SOA is not.... SOA is not about ...
-
A lot has been said about how SOA and EDA are unique "architecture styles". It seems like only one or the other architectural prin...