|
Service-Oriented
Architecture (SOA) is a software architecture style
that defines
the use of loosely coupled and inter-operable software
services to support the requirements of the business
processes and software users. In an SOA environment,
resources on a network are made available as independent
services that can be accessed without knowledge
of their underlying platform implementation. |
|
|
| With SOA and the
Service-Oriented computing platform becoming more
mature, there has been an emergence of more formal
approaches and methodologies to building service-oriented
solution logic. |
| |
|
| This refers to
a pre-design effort centered around the definition
of conceptual services or a conceptual service-oriented
architecture. Much like object-oriented analysis,
the goal is often to achieve an ideal representation.
The first vendor-agnostic service-oriented analysis
process to be published was documented in Thomas
Erl's "Service-Oriented Architecture: Concepts,
Technology, and Design" in which the conceptual
services were termed "service candidates".
|
| |
|
| The completion
of a service-oriented analysis leads to the service-oriented
design process, wherein the conceptual services
are subjected to the real world factors and conditions,
ultimately resulting in concrete service designs.
Thomas Erl was also responsible for publishing the
first vendor-agnostic service-oriented design process
in his book, "Service-Oriented Architecture:
Concepts, Technology, and Design". |
| |
|
| Service modeling
refers to a sub-process of the service-oriented
analysis process documented in Thomas Erl's book
"Service-Oriented Architecture: Concepts, Technology,
and Design". The service modeling process is
responsible for the definition and refinement of
service candidates based on various considerations,
including a specific subset of the service-orientation
principles. |
| |
|
| SOAP, the acronym
for the now-discarded “Simple Object Access
Protocol”, is a protocol for exchanging XML-based
messages over a computer network, normally using
HTTP. SOAP, the successor of XML-RPC, forms the
foundation layer of the Web services stack, providing
a basic messaging framework that more abstract layers
can build on. There are several different types
of messaging patterns in SOAP, but by far the most
common is the Remote Procedure Call (RPC) pattern,
in which one network node (the client) sends a request
message to another node (the server), and the server
immediately sends a response message to the client.
Originally designed by Dave Winer, Don Box, Bob
Atkinson, and Mohsen Al-Ghosein in 1998 with backing
from Microsoft as an object access protocol, the
SOAP specification is currently maintained by the
XML Protocol Working Group of the World Wide Web
Consortium. |
| |
|
| Service-Oriented
Development of Applications (SODA) was coined by
Gartner to define the realignment toward applications
that can be "constructed" by business
analysts via Process Modeling mechanisms. |
| |
|
Service-oriented
analysis and design also referred to as "service-oriented
modeling",
refers to an approach of software modeling and development
specially designed for SOA. SOAD adds innovations
for service repositories, service orchestration,
and the enterprise service bus. It also helps design,
build, aggregate, and deploy applications as Web
services based on SOAP, WSDL and UDDI technologies.
|
| |
|
| Service-oriented
modeling and architecture, coined by IBM, refers
to the more general domain of service modeling necessary
to design and create SOA. SOMA covers a broader
scope and implements service-oriented analysis and
design through the identification, specification
and realization of services, components that realize
those services ("service components"),
and flows that can be used to compose services.
SOMA includes an analysis and design method that
extends traditional object-oriented and component-based
analysis and design methods to include concerns
relevant to and supporting SOA. |
|
