SOA has a single-minded goal when it comes to modeling—to tie business processes together with underlying applications by using Web services in a distributed computing plan.
The purpose of the SOA Service Analysis and Design is to provide a step-by-step process for conducting the analysis of service candidates that one wishes to implement in an SOA. For concepts and theories behind why you need to conduct proper service-oriented modeling, see the Service Modeling best practice guide.
Introduction
SOA is not a product. It is not tangible or something you put your hands on. From a high-level perspective, SOA architecture is extremely flexible and can change or extend when demands warrant. This document, however, is not intended to study architecture. Instead, its purpose is to walk you through the steps of analyzing services, and then defines how to design and implement those services into an SOA that provides your organization with agility.
As you further examine service-oriented analysis and design perspectives, you should be aware that SOA solutions are composed of reusable services based on standards-based, well-defined interfaces.
Service-oriented modeling is a component of the analysis process, in which several processes are executed to help you identify service candidates. The service candidates are then assembled into abstract compositions that implement one ore more business processes.
Analysis and design also helps you to understand what type of thinking is necessary to evaluate business processes and logic to determine if they are SOA-worthy, service candidates.
Tags: .NET Web Services, Service-Oriented Architecture, SOA, SOA Analysis, SOA Design, SOA Modeling, SOA Tutorial, Web Services
