Service-oriented modeling

Any service-oriented modeling method typically includes a modeling language that can be employed by both the "problem domain organization" (the business), and "solution domain organization" (the information technology department), whose unique perspectives typically influence the service development life-cycle strategy and the projects implemented using that strategy.

[2] IBM announced service-oriented modeling and architecture (SOMA) as its SOA-related methodology in 2004 and published parts of it subsequently.

SOMA identifies services, component boundaries, flows, compositions, and information through complementary techniques which include domain decomposition, goal-service modeling and existing asset analysis.

The fundamental building blocks of SOA consist of services, components, flows and related to them, information, policy and contracts.

These are the modeling pillars that will enable practitioners to craft an effective project plan and to identify the milestones of a service-oriented initiative—either a small or large-scale business or a technological venture.

Furthermore, the video clip below, depicts the three SOMF building blocks, segments that drive the service-oriented modeling process:

Service-Oriented Modeling Framework (SOMF) Processes, Artifacts, and Best Practices
Service-Oriented Modeling Framework (SOMF) Three Segments (while running stop to review in details)