SOA Workshop - SOMA. Service Oriented Methodology & Architecture SOMA

Transcription

1 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

2 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.

3 SOMA and Banking Transformation Banking Transformation has an Asis 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 TxMQ, Inc, 2351 North Forest Rd., Suite 120 Getzville, NY

4 SOMA Agility across projects 1. Select (next) project scope 2. Select a project 5. Review result 4. Execute 3. Assess and address capability gaps with each project delivering immediate and long-term value

5 SOMA Supports SOA Lifecycle.. Discover Construct & Test Compose Integrate people Integrate processes Manage and integrate information Gather requirements Model & Simulate Design Financial transparency Business/IT alignment Process control Manage applications & services Manage identity & compliance Monitor business metrics 5

6 IBM SOMA Tools Part of a broader portfolio to meet your SOA needs IIB Developer Toolkit Rational Application Developer IBM Business Process Manager IBM Integration Bus IBM Business Modeler Rational Software Architect IBM Business Monitor Tivoli Composite Application Manager Tivoli Identity & Access Manager 6

7 SOMA Refinement within a Project with each project delivering immediate and long-term value

8 SOMA Lifecycle

9 SOMA Inputs & Outputs

10 SOA Maturity focus on building flexibility... The next stage of integration Messaging Backbone Enterprise Application Integration (EAI) Service Orientated Integration Point-to-Point connection between applications Simple, basic connectivity EAI connects applications via a centralized hub Easier to manage larger number of connections Integration and choreography of services through an Enterprise Service Bus Flexible connections with well defined, standards-based interfaces As Patterns Have Evolved, So Has IBM 10

11

12 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.

13 Banking Transformation

14 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

15 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.

16 Service Oriented Modeling & Architecture (SOMA) CBM SOMA SOA KPIs Flows/ Activities Use Cases OO A&D Business Business Process Service Descriptions Information (IT) Map Attribution Processes/ Components Services Patterns/ framework Standards Programming model

17 Service Modeling Identification Domain decomposition Goal-service modeling Existing system analysis Specification component flow specification information specification Subsystem analysis Component specification Service specification service flow specification message & event specification Service realization decision Realization Service allocation to components component layer 2015 TxMQ, Inc, 2351 North Forest Rd., Suite 120 Getzville, NY

18 Application Component Mapping Component mapping N Tiers or services Environments Target servers Servers have roles (web, app, db) Configuration management Processes Coordinates Component processes

19 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.

20 SOA Roadmap

21 Deployment to SOA Infrastructure 2015 TxMQ, Inc, 1430B Millersport Highway, Amherst, NY

22 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

23 SOA Additional Concerns - Security 2015 TxMQ, Inc, 2351 North Forest Rd., Suite 120 Getzville, NY

24 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

25 2351 N. Forest Rd. Suite #120 Getzville, NY (716) Thank You!!