Amro - thanks for the question. With SOA, we're really talking about an architectural style\approach that is focused on meeting the needs of the business through a solid understanding of the business, aligning IT with the business and delivering the right set of services. There are a number of different technologies that can be used to realize the services, and it's great that you have experience with one of those approaches, web services.
The book should give you some insights into the work that is done in learning about the needs of the business and translating those into a set of service specifications and how these services collaborate in delivering value. The book also discusses the importance of architecture in SOA, it's so important that it's part of the name :-), introduces related Domain Specific Languages (business modeling and SoaML), a set of patterns to help with Business Modeling, Service Identification and Service Specification, and ways in which automation helps not only with analysis and design, but also with SOA Governance.
I expect that you will benefit from giving the book a read in a couple of ways:
1. If you are looking to gain a better understanding of some of the work, responsibilities and thought that goes into the design and architecture of an SOA solution
2. Gain insights into how a set of automations (patterns, constraints, and reports) can work together to help in creating a solution.