Jump to content

Service-Oriented Modeling and Architecture

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Aarsanjani (talk | contribs) at 22:03, 5 February 2006. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

Service-Oriented Modeling and Architecture

Modeling for object-oriented systems (OOAD) and component-based software has been around for some time. Methods supporting OOAD and CBD do not cover all the elements required to support Service-Oriented Architecture (SOA). The primary elements of an SOA are services, components that realize those services and flows (processes) that compose services into composite services or applications. Services, components and flows are therefore first calss constructs of the service-oriented computing paradigm.

In order to build SOA-based systems, we therefore need to model the three fundamental constructs of SOA. This modeling (analysis and design activities and artifacts produced as a result of conducting those activities) can be seem in SOMA.

Here is an article on SOMA.