SOAConcepts.com

The word “offshoring” and its sibling “outsourcing” can provoke instant, righteous anger among some people, while being touted as a one-size-fits-all panacea by others. The recent decade or so of outsourcing and offshoring—particularly to India within the IT business—has generated copious case studies, best practices, and worst practices.
 

How do you establish agile enterprise architecture? How can you rapidly develop and deploy applications to satisfy or even lead the market demand? Many enterprises are constructing and reorganizing the architecture using the concept of service-oriented architecture (SOA).
However, we may all encounter some problems when applying SOA using some existing development processes and notations, such as object-oriented analysis and design (OOAD), enterprise architecture (EA) frameworks, and business process modeling (BPM).

Business process management (BPM) is a business management philosophy consisting of the idea that a business can be understood and managed solely in terms of business processes. BPM is process-centric and responsive to change in business requirements and objectives. Businesses are defined through dynamic processes that change almost constantly.
Workflow Management Coalition Terminology and Glossary defines a business process as follows:

When people are first exposed to a new technology, their first urge is to apply yesterday's approaches, theories, and concepts to that new technology. It is only natural, of course, to think of new technologies the way that one traditionally thought of the old technology that it might be replacing, because there is simply no experience yet with how the new technology can be best applied.

What are the main benefits of SOA ?

SOA helps create greater alignment between IT and line of business while generating more flexibility - IT flexibility to support greater business flexibility. Your business processes are changing faster and faster and global competition requires the flexibility that SOA can provide.

SOA is for building business applications. Many legitimate approaches to software architecture exist, and SOA is not intended for building every kind of software. It is intended explicitly for building business applications.

SOA is a black-box component architecture. SOA deliberately hides complexity wherever possible, and the idea of the black box is integral to SOA. The black box enables the reuse of existing business applications by adding a fairly simple adapter to them, no matter how they were built.

What is an Asset in the SOA world?

An asset is something that adds value and provides a solution to a problem. The asset should be reusable in similar contexts and may be customized. Three dimensions describe reusable assets: granularity, variability, and articulation:

Here are the definition of some of the key terms related to SOA Governance.

List down some of the roles and responsibilities in a SOA Implementation:

The following SOA roles and responsibilities have been found to be a worthwhile starting point for consideration:

A service is a well-defined unit of work performed by a component and packaged for easy access. The idea is to implement the functionality exactly once, do it well, and then make it widely accessible. The extra effort involved in initially creating the service (and there is always extra effort) is paid for by avoiding future development costs either through the direct reuse of the service or by isolating the service user from ongoing internal implementation changes within the service.