Gojko ! you know in SOA is required more "burocratic" specification for align Organizations with Tech.
is Your Book one point for read when one team is looking one OASIS in the SOA Governance and requeriments troubles?
i already sure what the big troubles whit large specification is complexity of the Organizations, in SOA the team must understand the Organization before initial the projects and deliveries.
Thank you and good luck for your book
BTW: Sorry for my english, this is not mi native language.
Joined: Sep 07, 2011
I don't deal with SOA specifically in the book or any of the we-sold-our-children-to-buy-process-from-gartner architecture methods, so if you are looking for answers on that it's better to read something else. the book has case studies on specification and testing processes in large organisations and multi-site or multi-team groups, but approaches that from the perspective of business focus and collaboration rather than technical architecture. tech architecture is an important concern, but there are many other great books about it.
i just looking that! i think of focus over Organization and Methods its the real SOA Approach, SOA in tech level could be make in many alternatives but the essential is align with Bussines Requeriments, i feeling thats its not really in SOA Projects.