SOA Workshop - SOMA

Service Oriented Methodology & Architecture – SOMA

• History of SOMA• In 2005, IBM introduced a way to map business processes to Service Oriented Architecture.

• SOMA (Service Oriented Modeling and Architecture) was born.

• Familiar Techniques• Domain Analysis

• Process Modeling

• Component-based Development

• Object-oriented Development

• Component Based Modeling• A functional decomposition approach

• Focuses on Business Process issues/interactions

• Provides scope for SOA

What is SOMA?

❑ Service-oriented Modeling Approach

Definition: Service-oriented modeling approach provides modeling,

analysis, design techniques, and activities to define the foundations of

a SOA. It helps by defining the elements in each of the SOA layers and

making critical architecture decisions at each level. It does so using a

combination of a top-down, business-driven manner of service

identification coupled with a stream of work that conducts service

identification through leveraging legacy assets and systems.

SOMA and Banking Transformation

Banking Transformation has an “As-is” and a “To-be” desired state.

As-Is” means older structured programming model, monolithic applications, batch processing, brittle and time consuming to modify.

“To-Be” means enablement with flexible, reusable, object oriented programming model, online and scalable business services that are easy to assemble, easy to modify, reliable and independent for ease of maintenance.

SOMA addresses the gap.

© 2017 TxMQ, Inc, 2351 North Forest Rd., Suite 120 Getzville, NY 14068 | 716-636-0070 | www.txmq.com

… with each project delivering immediate and long-term value

SOMA – Agility across projects

2. Select a project

3. Assess and address capability gaps4. Execute

5. Review result

1. Select (next) project scope

5

SOMA Supports SOA Lifecycle ..

▪Discover

▪Construct & Test

▪Compose

▪ Integrate people

▪ Integrate processes

▪Manage and integrate information

▪Manage applications &

services

▪Manage identity &

compliance

▪Monitor business metrics

▪Financial transparency

▪Business/IT alignment

▪Process control

▪Gather requirements

▪Model & Simulate

▪Design

6

IBM SOMA Tools

Part of a broader portfolio to meet your SOA needs

IBM Business Process ManagerIBM Integration Bus

IBM Business MonitorTivoli Composite Application ManagerTivoli Identity & Access Manager

IBM Business Modeler Rational Software Architect

IIB Developer ToolkitRational Application Developer

… with each project delivering immediate and long-term value

SOMA – Refinement within a Project

SOMA – Lifecycle

SOMA – Inputs & Outputs

10

As Patterns Have Evolved, So Has IBM

▪ Point-to-Point connection

between applications

▪ Simple, basic connectivity

Messaging Backbone

▪EAI connects applications

via a centralized hub

▪ Easier to manage larger

number of connections

Enterprise Application

Integration (EAI)

▪ Integration and choreography of

services through an Enterprise

Service Bus

▪ Flexible connections with well

defined, standards-based

interfaces

Service Orientated Integration

SOA Maturity – focus on building flexibility. . .

The next stage of integration

SOMA supports SOA

So if SOA is not just about the products and standards that help realize it (for example through Web services), then what additional elements to you need to realize a SOA?

Service-oriented modeling requires additional activities and artifacts that are not found in traditional object-oriented analysis and design (OOAD).

Three key elements of an emerging SOA: services, flows, and components realizing business services.

http://www.redbooks.ibm.com/abstracts/sg246303.html

Banking Transformation

Getting to SOA using SOMA

Service-oriented modeling approaches provides modeling,

analysis, design techniques, and activities to define the

foundations of a SOA. Critical architecture decisions are

made concerning each layer of SOA, which are coupled

with a stream of work that conducts service identification

through leveraging legacy assets and systems through:

❑ Business Modeling

❑ Service Modeling

❑ Component Mapping

❑ Development & SDLC

❑ Deployment into Runtime environments

Business Modeling

❑ Defining the business requirements: identification of

customer needs, automation and human tasks

❑ Depicting the business requirements together in a work

flow indicating performers and actors (use cases and

swim lane diagrams)

❑ Creating workflow models to determine business

prioritization and process improvement opportunities

(runtime modeling with service orchestration)

❑ Business Process Management tooling simplify these

tasks and make models easier to maintain or modify for

future business initiatives.

Service Oriented Modeling & Architecture (SOMA)

KPIsFlows/

Activities

Business Information (IT)

Use Cases OO A&D

MapAttribution

Processes/Components

Patterns/framework

StandardsProgramming

modelServices

BusinessProcess Service

Descriptions

CBM SOASOMA

Service Modeling

© 2015 TxMQ, Inc, 2351 North Forest Rd., Suite 120 Getzville, NY 14068 | 716-636-0070 | www.txmq.com

Service allocation

to componentscomponent layer

Service realization decision

Subsystem

analysis

Component

specification

Service

specification

component flow

specification

information

specification

service flow

specification

message & event

specification

Identification

Specification

Realization

Domain

decomposition

Goal-service

modeling

Existing system

analysis

Application – Component Mapping

❑ Component mapping

▪ N Tiers or services

❑ Environments

▪ Target servers

▪ Servers have roles (web, app, db)

▪ Configuration management

❑ Processes

▪ Coordinates Component processes

Development & SDLC

❑ Since services provide significant decoupling of monolithic applications into smaller and more isolated components which are used by multiple lines of business, development teams can transform roles to implement changes in a SOA.

❑ Activities that are typically conducted by each role (provider or consumer) involve:▪ Service identification

▪ Categorization

▪ Prototyping

Consumers often specify the service they want, and search for it. Once they are convinced of a match, they bind to it and invoke it as needed. Providers, likewise, need to publish services they are willing to support – both in terms of functionality and QoS required by consumers, creating a SLA between consumer and provider.

SOA Roadmap

Deployment to SOA Infrastructure

© 2015 TxMQ, Inc, 1430B Millersport Highway, Amherst, NY 14221 | 716-636-0070 | www.txmq.com

SOMA and SOA Challenges

❑ Security and Other Service Challenges related to:

▪ Sharing more data – more data accessible to more endpoints

▪ Secure exchange of various data types

▪ Legal requirements for Personal, Banking and other sensitive data

❑ Service Access Management Technology Adoption

▪ User ID / Password Authentication

• Distributed systems – Local OS and LDAP

• Mainframe z/OS – Local OAM

▪ Support for Multiple Configurable Certificates

• More flexible options for SSL/TLS authentication and data

encryption

• Security for end-to-end message security, whilst in flight and at rest

waiting for application consumption

© 2015 TxMQ, Inc, 2351 North Forest Rd., Suite 120 Getzville, NY 14068 | 716-636-0070 | www.txmq.com

SOA Additional Concerns - Security

© 2015 TxMQ, Inc, 2351 North Forest Rd., Suite 120 Getzville, NY 14068 | 716-636-0070 | www.txmq.com

Measuring Transformation Progress

❑ Establishing a SOA Maturity Model

❑ Deployment Automation

❑ Continuous Testing – Defect Tracking

❑ Service Level Management Reporting

❑ Achieving higher levels of reuse

❑ Estimation model – taking less time to develop solutions

❑ Performance & Capacity Management

Thank You!!

2351 N. Forest Rd. Suite #120Getzville, NY 14068+1 (716) 636-0070www.txmq.com