SOA Practitioners Opinion on Business Architecture

[Former Member]

This white paper is available [here|http://soablueprint.com/yahoo_site_admin/assets/docs/SOAPOpinion_BusinessArchitecture.49175900.pdf].

Abstract:

As Enterprises are starting to adopt Services-Oriented Architecture,

they are currently in the process of transforming both their Business

and IT organizations. In this context there has been a discussion on

the topic of Business Architecture with a basic consensus that

Business architecture is the link between business and technology (or

IT) but there isn't any clear definition of the roles and

responsibilities of this position. Nor is there clear descriptions of

the practical aspects of what exactly are the Business Architect's

activities and how should enterprises get started with this function.

The objective of this paper to help clarify these points from a

practitioner's point of view as well as help organization kick-start

the Business Architecture function.

Table of Contents:

Industry Context

Enterprise Value Discipline

How Organizations Learn

Introduction to Business Architecture

Business Architecture Defined

Business Architecture Responsibilities

Getting Started with Business Architecture

Adopting Services-Oriented Architecture

Business Driven SOA Planning Framework

Business Architecture Governance

Enterprise Architecture Governance

Enterprise Architecture Organization Structure

Proven Approach to Business Architecture Blueprinting

Developing the Business Architecture Blueprint

Conclusion

[Former Member]

Hi Yogish,

Please go through this link.

http://entarch.blogspot.com/2007/12/soa-consortium-keynote-by-amit-sinha.html

SOA and Business Architecture

One area where SOA has been gaining ground is in its power as a mechanism for defining business services[26] and operating models and thus provide a structure for IT to deliver against the actual business requirements and adapt in a similar way to the business. The purpose of using SOA as a business mapping tool is to ensure that the services created properly represent the business view and are not just what technologists think the business services should be. At the heart of SOA planning is the process of defining architectures for the use of information in support of the business, and the plan for implementing those architectures [27]. Enterprise Business Architecture should always represent the highest and most dominant architecture. Every service should be created with the intent to bring value to the business in some way and must be traceable back to the business architecture.

Within this area, SOMA (service-oriented modeling and architecture) was announced by IBM as the first publicly announced SOA-related methodology in 2004. Since then, efforts have been made to move towards greater standardization and the involvement of business objectives, particularly within the OASIS standards group and specifically the SOA Adoption Blueprints group. All of these approaches take a fundamentally structured approach to SOA, focusing more on the Services and Architecture elements and leaving implementation to the more technically focused standards. Another pertinent example is SAP Enterprise Services Architecture, which is focused on a strict governance process and the use of semantics to improve the usefulness of services in business process innovation.

For Your Information you can check this link.

http://en.wikipedia.org/wiki/Service-oriented_architecture

I think this will help you.

Reward points if useful.

Cheers,

Swamy Kunche.