Experts met at 2nd Annual SOA symposium and finally worked on SOA manifesto. Various experts have mentioned that after 3 days of discussions and sometime heated discussions they have agreed with the following manifesto
Service orientation is a paradigm that frames what you do. Service-oriented architecture (SOA) is a type of architecture that results from applying service orientation. We have been applying service orientation to help organizations consistently deliver sustainable business value, with increased agility and cost effectiveness, in line with changing business needs.
Through our work we have come to prioritize:
Business value over technical strategy
This is most common issue or factor that leads to delays and final product as the focus seem to tending or pulled either way and its balanced well. Technical strategy should help increase the business value not degrade it.
Strategic goals over project-specific benefits
Although strategic goals are always the priority, tactical goals also need to taken in consideration.
As we all know the business is not always on cruise control and shits happen and tactical goals need priority sometimes.
Intrinsic interoperability over custom integration
In many cases , if you try hard you can find a way out of custom integrations.
Shared services over specific-purpose implementations
This has been the trend recently and certainly has greater value at harder times
Flexibility over optimization
umm.. this is a fine line to walk.
Evolutionary refinement over pursuit of initial perfection
Most SOA projects i have seen have fallen into the initial perfection pit hole. Certainly what governance preaches you might lead to this pit fall. This is absolutely a good point and this needs to be on the top
That is, while we value the items on the right, we value the items on the left more.
Guiding Principles... Please check them out at SOA Manifesto Site
Service orientation is a paradigm that frames what you do. Service-oriented architecture (SOA) is a type of architecture that results from applying service orientation. We have been applying service orientation to help organizations consistently deliver sustainable business value, with increased agility and cost effectiveness, in line with changing business needs.
Through our work we have come to prioritize:
Business value over technical strategy
This is most common issue or factor that leads to delays and final product as the focus seem to tending or pulled either way and its balanced well. Technical strategy should help increase the business value not degrade it.
Strategic goals over project-specific benefits
Although strategic goals are always the priority, tactical goals also need to taken in consideration.
As we all know the business is not always on cruise control and shits happen and tactical goals need priority sometimes.
Intrinsic interoperability over custom integration
In many cases , if you try hard you can find a way out of custom integrations.
Shared services over specific-purpose implementations
This has been the trend recently and certainly has greater value at harder times
Flexibility over optimization
umm.. this is a fine line to walk.
Evolutionary refinement over pursuit of initial perfection
Most SOA projects i have seen have fallen into the initial perfection pit hole. Certainly what governance preaches you might lead to this pit fall. This is absolutely a good point and this needs to be on the top
That is, while we value the items on the right, we value the items on the left more.
Guiding Principles... Please check them out at SOA Manifesto Site
Posts
