Bertrand Duperrin's Library tagged soa →  View Popular, Search in Google

"La taille d’une organisation influe sur les modes de prise de décision, de transfert d’information ou de coopération, ce qui fait que les « bonnes recettes » à 10 personnes ne fonctionnent pas forcément à 100 ou encore moins à 1000. Plus précisément, un grand nombre de problèmes apparaissent lorsque la taille augmente, et l’efficacité n’est pas proportionnelle à la force de travail disponible. Cette constatation n’est pas sans rappeler ce qu’on observe dans les systèmes parallèles (cf. la loi d’Admdhal) qui montre que la puissance que l’on obtient en multipliant les processeurs est compensée par la tâche croissante de synchronisation. Ce n’est pas une surprise : les petites structures souffrent moins des problèmes de coordination et de synchronisation !"

organization coordination dunbar scale scalability context teams management structure organizationaldesign lean interfaces autonomy SOA complexity networks socialnetworks enterprise2.0 socialbusiness podularity

"Anyway, this post aims to discuss the issue of Process Integration using Social software as this looks like a great opportunity for both parties. Solving the Business Process Management equation thanks to Social Software agillity on one hand and putting Enterprise 2.0 into the flow of business processes."

socialbusiness BPM PLM CRM SCM SOA socialmessaging flows processes businessprocess

Somewhere in this book Clay says that the transformative potential of a technology on society is realized when that technology becomes boring

technology software adoption web2.0 SOA

But the world isn’t like that - it can be risky and unpredictable, and, whilst you do need systems and processes, you need to be able to account for the exceptions - which often happen more often than you think. The irony is, as SOA-type systems handle processes more and more effectively, it means that people have less to do with processes, and therefore get more involved with exceptions. The more processes get standardised the more costly exceptions become as a percentage of operating expense. Customer requirements, supply problems, pricing can move incredibly quickly, and an SOA architecture isn’t going to help you when the problem is not knowing who to call.
[...]
From a technology point of view, employees need the social software tools required to resolve exceptions, and to disseminate the tacit knowledge that goes hand in hand with exception handling throughout the enterprise. You need to be able to quickly find the veteran who knows exactly what to do when a particular supplier drops the ball and you need to bypass standard procurement in order to meet a customer’s expectations. Once found, the resolution to that exception needs to be captured in a way that it can be found long after the veteran has retired.

SOA exception knowledge expertise tacitknowledge process

We do not make reuse an explicit goal and reward people who reuse things, or who design things so that they can be reused by others.

soa reuse