Using UML service components to represent the SOA architecture pattern
Help stakeholders to better understand service components that comprise an SOA
From the developerWorks archives
First published: June 19, 2007
As an architect, you are often challenged -- by client enterprise architects and IT stakeholders -- to articulate Service-Oriented Architecture (SOA) patterns and service components in a nonproprietary, product-agnostic way. In this article, use Unified Modeling Language (UML) models to describe the SOA architecture pattern and its associated service components. You also learn about the service components of the SOA pattern in the context of industry-standard UML formats to help stakeholders to better understand the components that constitute an SOA.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.