Mapping Service-Orientation to TOGAF 9 Part IV: Applying Service-Orientation to TOGAF s Service Contracts
|
|
- Beverly Thompson
- 6 years ago
- Views:
Transcription
1 Mapping Service-Orientation to TOGAF 9 Part IV: Applying Service-Orientation to TOGAF s Service Contracts by Filippos Santas, Credit Suisse Private Banking in Switzerland In this series of articles we examine the correspondence and synergies of service-orientation and The Open Group Architecture Framework. In parts I and II of this article we went through the phases related to architecture definition, service design and implementation, architecture adoption and vision, the main roles, and the implementation and governance of multiple service inventories using hierarchies of the TOGAF ADM. In the process, we also examined the synergies between the two methodologies. In the last article of this series we examine the level of abstraction that is necessary to apply service contracts in TOGAF, using service-orientation principles and patterns. Service Contracts in SOA and TOGAF One of the primary focal points of the service-orientation paradigm is the design and standardization of service contracts. In TOGAF and in SOA, the contracts are important in communicating and enforcing functionality, policy/structure requirements, and constraints between different pieces of heterogeneous software. The favorite metaphor used for describing the ability of service contracts to provide a healthy provider/consumer relationship, is the way in which business contracts establish an agreement and maintain trust in a commercial relationship between parties. The difference between service-orientation and TOGAF is how detailed this agreement is, and how the provider and consumer interact. Service-orientation recommends a high level of abstraction for the information provided in the contract. This is because one service should be used by many different kinds of consumers (Service Reusability principle). In order to accomplish the desired level of abstraction without compromising the precision or usefulness of the information in the contract, service-orientation applies principles such as the Standardized Service Contract and the Service Loose Coupling early in the analysis process. On the other hand, TOGAF considers contracts to be unique to a specific provider/consumer relationship, and they act as the container for both formal policies, as well as agreements that are unique to the parties. This implies that the contract published by the service provider is coupled to the consumer. Technical Interfaces, SLAs and Capabilities In service-orientation the technical interface is the part of the service contract. The technical interface provides the following: meta information about the service requirements (used by service consumers) for interacting with the service. A technical interface includes a set of service capabilities (or operations). Each capability offers a subset of the functionality of the service. Service consumers invoke the capabilities in order to gain access to the desired functionality. Additionally, the service contract includes a Service Level Agreement (SLA) with quality-of-service features, behaviors, limitations and potentially other human-readable documents. 1
2 TOGAF distinguishes between two kinds of contracts: Operational contracts which specify the actual communication protocols and message formats. Governance contracts between two business entities. These specify what interaction is needed, inputs, outputs, SLAs, OLAs, and KPIs. Governance contracts are the main concern at architectural level. An important observation is that the operational contract in TOGAF corresponds to the requirements for interacting with the service in service-orientation. The technical contract in SOA also includes information about input and output structures, policies and operations. That is, the technical contract combines operational and governance aspects. Furthermore, the technical contract is not restricted to apply only between two business entities: the technical contract specifies the required interaction, inputs, outputs and policies for many consumers of the service. Something similar can be said for the SLA and other human readable documents. In service-orientation, the SLA provided by the service applies to more than one consumer. Service-Orientation Principles for Service Contracts The application of service-orientation principles on the contract design ensures that service contracts (and services) can be used by many consumers, resulting in service reuse. There are eight design principles [REF- 1, REF-2] 1. Standardized Service Contract: Services within the same service inventory are in compliance with the same contract design standards. 2. Service Loose Coupling: Service contracts impose low consumer coupling requirements and are themselves decoupled from the surrounding environment. 3. Service Abstraction: Service contracts only contain essential information and information about services is limited to what published in service contracts. 4. Service Reusability: Services contain and express agnostic logic that can be positioned as reusable enterprise assets. 5. Service Autonomy: Services exercise a high level of control over their underlying runtime execution environment. 6. Service Statelessness: Services minimize resource consumption by deferring the management of state information when necessary. 7. Service Discoverability: Services are supplemented with communicative meta data by which they can be effectively discovered and interpreted. 8. Service Composability: Services are effective composition participants, regardless of the size and complexity of the composition. All of these principles, except for the Service Statelessness principle, contribute to the formation of the service contract. In particular, the two first principles, help to standardize and decouple the technical contract of each service, allowing for the Contract First design. In the following sections we will see how they can be applied in the service contracts in TOGAF. 2
3 Service Profiles Detailed analysis and design specification about a service is provided in standardized service profiles. Each service has one service-level profile and one capability profile for each of its capabilities. The attributes that correspond to these two profiles are provided in Tables 1 and 2. Service Profile Description Service Name (Short) (Detailed) Service Model Keywords Version Status Custodian A concise, one sentence description of the service context and purpose. A full explanation of the service context and its functional boundary with as many details as necessary. Entity, Utility, Task, Orchestrated Task, or a custom variation. Words ideally taken from an official service inventory-level taxonomy or vocabulary. The version number of the service currently being documented The development status of the service is expressed in this field using standard terms identifying a project lifecycle stage, such as analysis, contract design, development, or production. How to reach the official service custodian or owner, as well as others that contributed to this documentation. Table 1 Service Profile s 3
4 Capability Profile Description Capability Name (Short) Logic Description Input/Output Composition Role Composition Member Capabilities Keywords Version Status Custodian A concise explanation of the capability s overall purpose and functional context (short description) A step-by-step description of the logic carried out by the capability. Definitions of a capability s allowable input and/or output value(s) and associated constraints. The execution of capability logic can place a service into various temporary runtime roles, depending on its position within service composition configurations. A list of service capabilities composed by the capability logic. This provides a cross-reference to other service capabilities the current capability has formed dependencies on. Similar to Service Keywords Capabilities may be versioned with a number or with the version number appended to the capability name. Same lifecycle identifiers used for services Usually (but not always) this is (one of) the service custodian(s) Table 2 Capability Profile s Much of the information available in a service profile should remain hidden from potential service consumers, in order to avoid undesirable coupling of the consumers to the service design and implementation. Therefore service contracts typically contain only a subset of the data in a service profile. More specifically, the attribute: Detailed...of the service profile, and the attributes: Logic Description Composition Role, and Composition Member Capabilities...of the capability profile (marked with red in the above tables) violate the Service Abstraction and Service Loose Coupling principles, and therefore should not be included in the service contract. Furthermore, certain considerations should be made for choosing the appropriate values for the following attributes in service and capability profiles: 4
5 Service Name (Short) Keywords Capability Name Typically these attributes are parts of a service contract, and therefore they should respect the Service Abstraction and Service Loose Coupling principles, and they should facilitate the discoverability of services. Guidelines for putting appropriate values in the above attributes should be provided by applying the Standardized Service Contract principle. Concluding the discussion about Service and Capability Profiles it is important to note that service-orientation recommends the use of Centralized Schemas for describing the types and structure of input and output messages. Centralized Schemas have direct impact on the following attributes: Input/Output Version A new version of the schema may result in new versions for the service contracts. The propagation of versions from the schema to the contracts should be consistent (Service Standardization). Additionally, the Input/Output attribute references the required objects from the centralized schema, therefore, the Service Abstraction, Service Loose Coupling and Standardized Service Contract principles should apply to the schema as well. Generic s for All Meta Model Objects in TOGAF The service contract template includes all the attributes that TOGAF defines for service contracts in a SOA [REF-3]. The attributes of the service contracts are also defined in the TOGAF content meta model [REF-3]. All objects in the meta model, including service contracts have a common set of attributes. These attributes are provided in Table 3. The same considerations discussed previously for attributes of service profiles apply also to the attributes of the service contract template. Although among the common attributes there are no forbidden attributes, the values for the attributes: Reference Name Description...must satisfy the requirements of the following principles: Service Abstraction Standardized Service Contract Service Loose Coupling Service Discoverability 5
6 NOTE Although not specific to Service Contacts, the selection of the type of the service should not describe its implementation. For example, a service type Entity is proper, but service types such as Java or My Vendor Platform violate both the Service Abstraction and the Service Loose Coupling principles in the contract, and therefore should be avoided. TOGAF ID (or Reference) Description Type (or Category) Source Owner Definition A unique identifier within the architecture information for crossreference, clarity, and differentiation from other similar artifacts. The name of the service should indicate in general terms what it does, but should not be the only definition. The description is a narrative of what the artifact is, what it does, and its relevance to the architecture. The type of the service to help distinguish it in the layer in which it resides; e.g., data, process, functionality, presentation, functional. The source of the artifact, which may be a person or a document, along with a date to support traceability of the architecture. The owner of the artifact is the name (person or group) who validates the details of this artifact; the person/team in charge of the service. SOA Profile - (short) Service Model Custodian Table 3 Common s for all Metamodel Objects and Mapping to SOA Other General and Business s The Business attributes in the service contract demonstrate that service contracts are between two entities in TOGAF. That is, if a service provider is used by N consumers, then it may have N contracts. Service-orientation considers this approach the exception, rather than the rule. Agnostic Services should serve multiple consumers with the same contract. Nevertheless, the Concurrent Contracts pattern enables one body of service logic to expose multiple service contracts. This pattern is often used to accommodate different types of service consumers without having to convolute a single service contract. 6
7 TOGAF Definition SOA Profile Version The version of the service contract. Version RACI Responsible/Accountable/Consulted/Informed. Custodian Service Name Caller Service Name Called Functional Requirements Importance to the Process Quality of Information Required Contract Control Requirements Result Control Requirements Name of the consuming service. Name of the provider service. The functionality in specific bulleted items of what exactly this service accomplishes. The language should be such that it allows test cases to prove the functionality is accomplished. What happens if the service is unavailable. Accuracy and Completeness of information. The quality that is expected from the service consumer in terms of input, and what quality is expected from the service provider in terms of output. Level of governance and enforcement applied to the contractual parameters for overall service. Measures in place to ensure that each service request meets contracted criteria. Capability: Composition Role (Detailed) Capability: Logic Description Input/Output - - Quality of Service Allowable failure rate. - Service Level Agreement Amount of latency the service is allowed to have to perform its actions. - Table 4 Business s for TOGAF Service Contracts and Mapping to SOA Another observation is that in TOGAF the service contract resembles a combination of service and capability profile. It includes much information that often violates the Service Abstraction and Service Loose Coupling principles. In particular the values of the attributes: Caller, Called, Functional Requirements, Importance to the Process...describe either run-time roles or are specific to a particular process. Agnostic services do not know anything about the processes in which they are invoked, and therefore, cannot provide the information required in these fields. Additionally, detailed description of the functional requirements in the service contract introduces undesirable 7
8 coupling between the service contract and the functions defined within the service. A better approach is to list the capabilities provided by the service, along with a short description for each of them, instead of describing the functional requirements. The control requirements are part of the overall requirements for the service and should probably be standardized across the entire service inventory. The Domain Inventory pattern is here preferable instead of providing such information in the service contract. Handling of the attributes Quality of Service and Service Level Agreement will be discussed in the following section. s for Non-Functional Requirements In order to satisfy non-functional requirements similar to those in Table 5, service designers usually apply the Service Autonomy principle. If the service is agnostic, then all non-functional requirements should be considered and the implementation should support the load predicted in the future and during the peak periods. If the service cannot satisfy these requirements, then it cannot support the Service Reusability principle. However, quality of service information needs to be reduced to reasonable levels by applying the Service Abstraction principle. Making promises on unrealistic levels such as availability close to may result in implementations that do not allow for the service to evolve. TOGAF Definition SOA Profile Throughput Volume of transactions estimated; e.g., 100,000 Throughput Period Growth Growth Period Service Times Peak Profile Short Term Peak Profile Long Term Security Requirements (or Security Characteristics) Response Requirements The period in which those transactions are expected, e.g., 100,000 per day. The growth rate of transactions over time The period in which the growth is estimated to occur; e.g., 10,000 per year. The available hours/days the service is needed; for example, daily, 9 to 5 (excluding Holidays). The profile of the short-term level of peak transactions; for example, 50% increase between hours of 10 to 12 am. The profile of the long-term level of peak transactions; for example, 50% increase at month end. Can execute this service in terms of roles or individual partners, etc. and which invocation mechanism they can invoke. The level and type of response required. Response times that the service provider must meet for particular operations. (Detailed) Typically found in an SLA Table 5 s for Non-Functional Requirements 8
9 s for Technical Information s with technical information correspond to elements of a technical interface. In more detail: The different invocation mechanisms provided for a single service are supported by the Concurrent Contracts pattern. The invocation mechanism is always part of the technical interface. On the other hand, strict invocation preconditions may result in services that cannot be reused in many contexts. Such preconditions are typically not adequate for agnostic services, but can be enforced by compositions or validation at the orchestration level. The Service Abstraction principle should be applied in order to eliminate validations that may be restrictive for the reusability of the service. The Business Objects attribute can refer to the centralized schemas and is a mandatory attribute for every service contract. Finally, the attribute Behavior Characteristics violate the Service Abstraction and Service Loose Coupling principles: the contract depends on the implementation. This attribute should not be part of the contract for an agnostic service. On the other hand, architectures may put a limit on the depth of service compositions in order to satisfy Service Autonomy. In such case, it may be necessary to know if the invoked service is a composition. TOGAF Invocation Invocation Preconditions Definition This includes the URL, interface, etc. There may be multiple invocation paths for the same service. There may be the same functionality for an internal and an external client, each with a different invocation means and interface. Any pre-conditions that must be met by the consumer (authentication, additional input, etc.) SOA Profile Part of the Technical Interface Input/Output Business Objects Business objects transferred by the service. Input/Output Behavior Characteristics The criteria and conditions for successful interaction and any dependencies (on other service interactions, etc.). This should include any child services that will be invoked/spawned by this service (in addition to dependencies on other services). Composition Member Capabilities Table 6 Other s The content meta model in TOGAF [REF-3] defines additional attributes for service contracts. These attributes involve primarily non-functional requirements and can be classified in three groups: Group 1: Service quality characteristics, Availability characteristics, Manageability characteristics (control of state information), Serviceability characteristics, Performance characteristics, Reliability characteristics, Recoverability characteristics, 9
10 Group 2: Localability characteristics (Ability of a system to be found when needed), Group 3: Privacy characteristics (data protection), Integrity characteristics, Credibility characteristics, Localization characteristics, Internationalization characteristics, Interoperability characteristics, Scalability characteristics, Portability characteristics, Extensibility characteristics, Capacity characteristics. The requirements of Group 1 are typically satisfied by applying the Service Autonomy and Service Statelessness principles. As mentioned earlier, application of the Service Abstraction principle is mandatory in order to allow more room to the service for evolvement. The Localability attribute in Group 2, is accomplished by the Service Discoverability principle. The attributes in Group 3 are not specific to service-orientation, but their satisfaction by the service implementation contributes to the Service Reusability. Conclusions In this document we reviewed the attributes of the service contracts and profiles in service-orientation and TOGAF 9. The principles of Service Abstraction and Service Loose Coupling need to be applied to several attributes in TOGAF s service contracts. Some of the attributes do not respect service-orientation, and couple the service contract to other contexts. References [REF-1] SOA Principles of Service Design, Thomas Erl, Prentice Hall/PearsonPTR, [REF-2] Understanding Service-Orientation - Part II: The Principles. [REF-3] TOGAF Version 9. The Open Group,
11 Filippos Santas Filippos is an IT Architect for Credit Suisse Private Banking in Switzerland and a SOASchool. com Certified SOA Trainer, Analyst, Architect, Consultant, and Security Specialist. Additionally, he is certified by The Open Group on TOGAF 9 and by IBM on the Rational Unified Process V7.0. In the last 10 years, Filippos has been the lead for the analysis and architecture of a number of successful SOA projects and for transforming legacy architectures to serviceoriented architectures, primarily in the financial sector. His achievements include the conceptual and physical design of the international insurance claims service network that connects insurance policies, customer companies and state authorities in 44 countries across the globe, combining legislation, business processes, business rules, business objects, knowledge bases and different platforms. Filippos recent work with Credit Suisse has been as an SOA Architect, combining the profitable and established functionality of legacy systems with centralized business process services, decentralized business rule services, domain specific BOMs and entity services and end-to-end traceability to business requirements and processes. Contributions Mapping Service-Orientation to TOGAF 9 - Part IV: Applying Service-Orientation to TOGAF s Service Contracts Mitigating Service-Orientation Risks with RUP Mapping Service-Orientation to TOGAF 9 - Part III: SOA Governance Models for Service Inventories in TOGAF Mapping Service-Orientation to TOGAF 9 - Part II: Architecture Adoption, Service Inventories and Hierarchies Mapping Service-Orientation to TOGAF 9 - Part I: Methodology, Processes, Steps, Principles 11
Chapter 15. Supporting Practices Service Profiles 15.2 Vocabularies 15.3 Organizational Roles. SOA Principles of Service Design
18_0132344823_15.qxd 6/13/07 4:51 PM Page 477 Chapter 15 Supporting Practices 15.1 Service Profiles 15.2 Vocabularies 15.3 Organizational Roles Each of the following recommended practices can be considered
More informationSOA, Service-Orientation & Cloud Computing: The Connection Points
SOA, Service-Orientation & Cloud Computing: The Connection Points Thomas Erl SOA Systems Inc. Prentice Hall Service-Oriented Computing Series Started in 2003 Text Books are an Official Part of the SOACP
More informationMark Bailey Senior System Consultant Security, Government, & Infrastructure 2008 Intergraph Corporation
Principles of Service Oriented Architecture Mark Bailey Senior System Consultant Security, Government, & Infrastructure mark.bailey@intergraph.com 2008 Intergraph Corporation Agenda Motivation for Service
More informationService-Oriented Architecture: Making the most of SOA What, Why and How
Service-Oriented Architecture: Making the most of SOA What, Why and How Coenie Vermaak Solutions Architect Britehouse Automotive 15 October 2018 2015 1 The benefit potential offered by SOA can only be
More informationSOA Analyst Certification Self-Study Kit Bundle
SOA Analyst Certification Bundle A Certified SOA Analyst specializes in carrying out the analysis and definition of service inventory blueprints and the modeling and definition of service candidates, service
More informationAn Approach for Assessing SOA Maturity in the Enterprise
An Approach for Assessing SOA Maturity in the Enterprise by Andrzej Parkitny, Enterprise Architect, Telus Abstract: As a large organization grows, system integration becomes an important aspect of the
More informationCurrently a service can be built and implemented as : Web service REST Component
Currently a service can be built and implemented as : Web service REST Component Service-orientation is a design paradigm intended for the creation of solution logic units that are individually shaped
More informationService Oriented Architecture. Reference MIDDLEWARE & ENTERPRISE INTEGRATION TECHNOLOGIES By
Service Oriented Architecture Reference MIDDLEWARE & ENTERPRISE INTEGRATION TECHNOLOGIES By G. SUDHA SADASIVAM, RADHA SHANKARMANI 1 COMPILED BY BJ What is Service-Oriented Architecture? Service-Oriented
More informationIn Pursuit of Agility -
In Pursuit of Agility - BPM and SOA within the Boeing Company Ahmad R. Yaghoobi Associate Technical Fellow Enterprise Architect ahmad.r.yaghoobi@boeing.com Randy Worsech Business Architect Randall.a.worsech@boeing.com
More informationUnderstanding Reuse and Composition: Working with the Service Reusability and Service Composability Principles
Understanding Reuse and Composition: Working with the Service Reusability and Service Composability Principles by Thomas Erl, Arcitura Education Inc. Introduction This article is a modest collection of
More informationPRINCIPLES OF SERVICE ORIENTATION
PRINCIPLES OF SERVICE ORIENTATION Service Orientation and the enterprise 2 / 20 Enterprise Logic Business logic - documented implementation of the business requirements Application logic - automated implementation
More informationSOA Security Certification Self-Study Kit Bundle
SOA Security Certification Bundle A Certified SOA Security Specialist has comprehensive knowledge of common threats and vulnerabilities associated with service-oriented solutions and modern service technologies,
More informationSOA Principles of Service Design
SOA Principles of Service Design Thomas Erl 0 0 PRENTICE HALL UPPER SADDLE RIVER, NJ BOSTON INDIANAPOLIS SAN FRANCISCO PRENTICE HALL NEW YORK «TORONTO MONTREAL LONDON MUNICH PARIS MADRID CAPETOWN SYDNEY
More informationSOA Exam S90-01A Fundamental SOA & Service-Oriented Computing Version: 6.1 [ Total Questions: 100 ]
s@lm@n SOA Exam S90-01A Fundamental SOA & Service-Oriented Computing Version: 6.1 [ Total Questions: 100 ] https://certkill.com SOA S90-01A : Practice Test Question No : 1 Which of the following statements
More informationService Oriented Architecture
Service Oriented Architecture Part I INTRODUCING SOA Service Oriented Architecture- Presented by Hassan.Tanabi@Gmail.com 2 Fundamental SOA 1. The term "service-oriented" has existed for some time, it has
More informationSOA Principles of Service Design
00_0132344823_FM.qxd 6/13/07 5:11 PM Page ix SOA Principles of Service Design Thomas Erl PRENTICE HALL UPPER SADDLE RIVER, NJ BOSTON INDIANAPOLIS SAN FRANCISCO NEW YORK TORONTO MONTREAL LONDON MUNICH PARIS
More informationRESOLVING APPLICATION DEVELOPMENT ISSUES USING SOA Y. KIRAN KUMAR 1, G.SUJATHA 2, G. JAGADEESH KUMAR 3
RESOLVING APPLICATION DEVELOPMENT ISSUES USING SOA Y. KIRAN KUMAR 1, G.SUJATHA 2, G. JAGADEESH KUMAR 3 1 Asst Professor, Dept of MCA, SVEC, A. Rangampet. ykkumar83@gmail.com, sujatha229@gmail.com,com 148
More informationExam Questions OG0-091
Exam Questions OG0-091 TOGAF 9 Part 1 https://www.2passeasy.com/dumps/og0-091/ 1. According to TOGAF, Which of the following are the architecture domains that are commonly accepted subsets of an overall
More informationSOA Concepts. Service Oriented Architecture Johns-Hopkins University
SOA Concepts Service Oriented Architecture Johns-Hopkins University 1 Lecture 2 Goals To learn the basic concepts behind SOA The roots of SOA: the history from XML to SOA, and the continuing evolution
More informationSOA principles applied in current methodologies. Describing guidelines for using RUP and AIM for implementing SOA solutions
SOA principles applied in current methodologies Describing guidelines for using RUP and AIM for implementing SOA solutions Version control Version Date Short description changes 0.1 13-12-07 Start Rapport/Whitepaper
More informationSERVICE ORIENTED ARCHITECTURE (SOA)
International Civil Aviation Organization SERVICE ORIENTED ARCHITECTURE (SOA) ICAO APAC OFFICE BACKGROUND SOA not a new concept. Sun defined SOA in late 1990s to describe Jini. Services delivered over
More informationService Oriented Architecture
2 Service Oriented Architecture An Overview for the Enterprise Architect 2006 IBM Corporation Agenda IBM SOA Architect Summit Introduction SOA Reference Architecture SOA Roadmap SOA Governance Summary
More informationTOGAF 9 Training: Foundation
TOGAF 9 Training: Foundation Part I: Basic Concepts Document version control information Document Name Document Status Document Owner Part I: Basic Concepts Final IT Management Group TOGAF Lead Trainer
More informationSOA Enabled Workflow Modernization
Abstract Vitaly Khusidman Workflow Modernization is a case of Architecture Driven Modernization (ADM) and follows ADM Horseshoe Lifecycle. This paper explains how workflow modernization fits into the ADM
More informationService-oriented architecture (SOA)
Service-oriented architecture (SOA) Introduction Two definitions for SOA are as follows: SOA establishes an architectural model that aims to enhance the efficiency, agility, and productivity of an enterprise
More informationWEB SERVICES AND XML,M.INDUMATHY AP/IT YEAR & SEM:IV & VII UNIT-II
UNIT-II Roots of SOA Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures Anatomy of SOA- How components in an SOA interrelate -Principles of service orientation
More information1. INTRODUCTION BACKGROUND ENTERPRISE SOA BENEFITS AND TECHNOLOGIES AN ENTERPRISE SOA FRAMEWORK...6
1. INTRODUCTION...1 2. BACKGROUND...3 3. ENTERPRISE SOA BENEFITS AND TECHNOLOGIES...4 4. AN ENTERPRISE SOA FRAMEWORK...6 5. ALIGNING IT WITH BUSINESS...7 6. CONCLUSION...8 Whitepaper Page 2 What is Enterprise
More informationSOA S90-04A. SOA Project Delivery & Methodology. Download Full Version :
SOA S90-04A SOA Project Delivery & Methodology Download Full Version : https://killexams.com/pass4sure/exam-detail/s90-04a QUESTION: 90 Individual(s) assuming the role for an agnostic service will often
More informationTOGAF Foundation Exam
TOGAF Foundation Exam TOGAF 9 Part 1 (ESL) Time Limit 90 minutes Number of questions 40 Pass-through 22 1. Which of the following best describes the meaning of "Initial Level of Risk" in Risk Management?
More informationSOA Principles of Service Design
00_0132344823_FM.qxd 6/13/07 5:11 PM Page ix SOA Principles of Service Design Thomas Erl PRENTICE HALL UPPER SADDLE RIVER, NJ BOSTON INDIANAPOLIS SAN FRANCISCO NEW YORK TORONTO MONTREAL LONDON MUNICH PARIS
More informationOn demand operating environment solutions To support your IT objectives Transforming your business to on demand.
On demand operating environment solutions To support your IT objectives Transforming your business to on demand. IBM s approach to service-oriented architecture Doing business in the on demand era Technological
More informationMTAT Enterprise System Integration
MTAT.03.229 Enterprise System Integration Lecture 5: Service-Oriented Architectures Marlon Dumas marlon. dumas ät ut. ee Service-Oriented Architecture (SOA) SOA is a paradigm for organizing and utilizing
More informationThe Open Group Exam OG0-091 TOGAF 9 Part 1 Version: 7.0 [ Total Questions: 234 ]
s@lm@n The Open Group Exam OG0-091 TOGAF 9 Part 1 Version: 7.0 [ Total Questions: 234 ] https://certkill.com Topic break down Topic No. of Questions Topic 1: Volume A 100 Topic 2: Volume B 134 2 https://certkill.com
More informationThe Business Side of SOA. Challenge: Inertia in the Organization
The Business Side of SOA Ron Schmelzer ZapThink, LLC Take Credit Code: NOBIZ Copyright 2006, ZapThink, LLC 1 Challenge: Inertia in the Organization Architecture doesn t have features and business executives
More informationCIS 8090 Intro. Setting the stage for the semester Arun Aryal & Tianjie Deng
CIS 8090 Intro Setting the stage for the semester Arun Aryal & Tianjie Deng Cognitive Map of 8090 IS Architectures as Strategy Books: Weill, Ross & Robertson, Enterprise Architecture as Strategy & Fenix
More informationSOA, Microservices and Service Orientation:
SOA, Microservices and Service Orientation: The Samurai Way OGhTech Experience 17 Sandra Flores @sandyfloresmx 武 士道 Introduction SOA has been in action for a long time, even though many people are not
More informationChapter 1 Web Services Basics
Slide 1.1 Web Serv vices: Princ ciples & Te echno ology Mike P. Papazoglou mikep@uvt.nl Chapter 1 Web Services Basics Slide 1.2 Topics Introduction definitions Software as a service Where can services
More information1. Comparing Service Characteristics. (by Mark Richards) 2. Analysis and Modeling with Web Services and Microservices(by Thomas Erl)
1. Comparing Service Characteristics (by Mark Richards) 2. Analysis and Modeling with Web Services and Microservices(by Thomas Erl) Comparing Service Characteristics ServiceTaxonomy The term service taxonomy
More informationIN the inaugural issue of the IEEE Transactions on Services Computing (TSC), I used SOA, service-oriented consulting
IEEE TRANSACTIONS ON SERVICES COMPUTING, VOL. 1, NO. 2, APRIL-JUNE 2008 62 EIC Editorial: Introduction to the Body of Knowledge Areas of Services Computing Liang-Jie (LJ) Zhang, Senior Member, IEEE IN
More informationBIAN with BPS Design Methodology
IBM Industry Models Development BIAN with BPS Design Methodology SOA Industry Models v.8.8 IBM Industry Models 4-13-2016 Table of Contents BIAN with BPS Design Methodology...2 1.1 BIAN...2 1.1.1 BIAN Service
More informationThe role of the service-oriented architect
Copyright Rational Software 2003 http://www.therationaledge.com/may_03/f_bloomberg.jsp The role of the service-oriented architect by Jason Bloomberg Senior Analyst ZapThink LLC Web services have moved
More informationSOA Workshop - SOMA. Service Oriented Methodology & Architecture SOMA
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
More informationSOA Best Practices & Framework Services in Order to Invoice Enterprise Application Integrations
SOA Best Practices & Framework Services in Order to Invoice Enterprise Application Integrations By Raman D. Singh Consulting Manager, SOA Practice Protégé Software Services Booth# 1426 Agenda Today Protégé
More informationService Oriented Realization of The HTNG Reference Architecture
Oriented Realization of The HTNG Reference Architecture Version 0.6 Revision History Date Version Description Author June 24, 2008 0.1 First Draft with Structure Chris Laffoon (IBM) August 20, 2008 0.2
More informationService oriented architecture solutions White paper. IBM SOA Foundation: providing what you need to get started with SOA.
Service oriented architecture solutions White paper IBM SOA Foundation: providing what you need to get started with SOA. September 2005 Page 2 Contents 2 Executive summary 2 SOA: the key to maximizing
More informationTOGAF 9.1 Phases E-H & Requirements Management
TOGAF 9.1 Phases E-H & Requirements Management By: Samuel Mandebvu Sources: 1. Primary Slide Deck => Slide share @ https://www.slideshare.net/sammydhi01/learn-togaf-91-in-100-slides 1. D Truex s slide
More informationSlide 1. Slide 2. Slide 3. Objectives. Who Needs Interoperability? Component 9 Networking and Health Information Exchange
Slide 1 Component 9 Networking and Health Information Exchange Unit 8 Enterprise Architecture Models This material was developed by Duke University, funded by the Department of Health and Human Services,
More informationMTAT Enterprise System Integration. Lecture 6 Service-Oriented Architecture Basic Concepts
MTAT.03.229 Enterprise System Integration Lecture 6 Service-Oriented Architecture Basic Concepts Marlon Dumas marlon. dumas ät ut. ee Where are we? We have seen technology and architectural styles for
More informationPaul Lipton. Abstract. Speaker. SOA is Naturally Diverse. The New SOA Synergy: How Runtime Governance, Triage, and Security Must Work Together
Abstract The New SOA Synergy: How Runtime Gnance, Triage, and Must Work Together Sr. Architect, Office of the CTO, CA Inc. paul.lipton@ca.com We will consider how the unique architectural characteristics
More informationSOA Design Patterns. Thomas Erl. (with additional contributors) PRENTICE HALL UPPER SADDLE RIVER, NJ BOSTON INDIANAPOLIS SAN FRANCISCO
SOA Design Patterns Thomas Erl (with additional contributors) E PRENTICE HALL UPPER SADDLE RIVER, NJ BOSTON INDIANAPOLIS SAN FRANCISCO NEW YORK TORONTO MONTREAL LONDON MUNICH PARIS MADRID CAPETOWN SYDNEY
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2008 Vol. 7, No. 1, January-February 2008 The Year of the Globally Integrated Enterprise Mahesh
More informationInformation Architecture: Leveraging Information in an SOA Environment. David McCarty IBM Software IT Architect. IBM SOA Architect Summit
Information Architecture: Leveraging Information in an SOA Environment David McCarty IBM Software IT Architect 2008 IBM Corporation SOA Architect Summit Roadmap What is the impact of SOA on current Enterprise
More informationRealization of Supply Chain Reference Architecture
633 Realization of Supply Chain Reference Architecture Eugene Moses R, CPIM, TOGAF, Gururaman Subramanian Abstract In today s global economy, businesses collaborate across multiple organizations that include
More informationCloud Computing Lectures SOA
Cloud Computing Lectures SOA 1/17/2012 Service Oriented Architecture Service Oriented Architecture Distributed system characteristics Resource sharing - sharing of hardware and software resources Openness
More informationEnterprise Services Repository
Enterprise Services Repository An overview Rathish Balakrishnan SAP NW Product Management SOA Middleware The Approach: Service Oriented Architecture SOA is essential but missing business semantics WEB
More informationIBM EXAM QUESTIONS & ANSWERS
IBM 000-669 EXAM QUESTIONS & ANSWERS Number: 000-669 Passing Score: 800 Time Limit: 120 min File Version: 36.6 http://www.gratisexam.com/ IBM 000-669 EXAM QUESTIONS & ANSWERS Exam Name: SOA Fundamentals
More informationSERVICE ORIENTED ARCHITECTURE SOA INTRODUCTION
SERVICE ORIENTED ARCHITECTURE SOA INTRODUCTION SECTOR / IT NON-TECHNICAL & CERTIFIED TRAINING COURSE In this SOA training course, you learn how to create an effective SOA by modeling, designing, and orchestrating
More informationPassit4Sure.OG Questions. TOGAF 9 Combined Part 1 and Part 2
Passit4Sure.OG0-093.221Questions Number: OG0-093 Passing Score: 800 Time Limit: 120 min File Version: 7.1 TOGAF 9 Combined Part 1 and Part 2 One of the great thing about pass4sure is that is saves our
More informationSOMF at a Glance. Methodologies Corporation:
SOMF at a Glance Service-Oriented Modeling Framework (SOMF) - A modeling platform for Enterprise Architecture, Business Architecture, Application Architecture, service-oriented architecture (SOA), and
More informationArchitecting Web Service Applications for the Enterprise
Architecting Web Service Applications for the Enterprise Michael Rosen Chief Enterprise Architect mike.rosen@iona.com March 5, 2002 Copyright IONA Technologies 2002 Slide 1 END 2 ANYWHERE Basic Web Service
More information23. Service-Oriented Architectures
23. Service-Oriented Architectures Slide 1 Acknowledgements: Material on Service-Oriented Architectures Based on a tutorial by Grace Lewis et al. + Slides by Michael Brodie (with minor adaptations) Slide
More informationSOA S Fundamental SOA & Service-Oriented Computing. Download Full Version :
SOA S90-01 Fundamental SOA & Service-Oriented Computing Download Full Version : https://killexams.com/pass4sure/exam-detail/s90-01 services that can provide the logic required to automate the new business
More informationThe Rational Unified Process for Systems Engineering PART II: Distinctive Features
The Rational Unified Process for Systems Engineering PART II: Distinctive Features by Murray Cantor Principal Consultant Rational Software Corporation In Part I of this article, published in last month's
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2007 Vol. 6, No. 1, January-February 2007 Where s the (Business) Beef? Mahesh H. Dodani, IBM
More informationWork Product Dependency Diagram
Work Product Dependency Diagram Project Definition System Context Subject Area Model Architectural Decisions Requirements Matrix Use Case Model Service Model Non Functional Requirements Component Model
More informationConnectivity & Application Integration. Colin Gniel WebSphere Software IBM Software Group Australia/New Zealand
Connectivity & Application Integration Colin Gniel WebSphere Software IBM Software Group Australia/New Zealand The Planet is Getting Smarter Smarter Planet instrumented interconnected intelligent people
More informationSolution Architecture Training: Enterprise Integration Patterns and Solutions for Architects
www.peaklearningllc.com Solution Architecture Training: Enterprise Integration Patterns and Solutions for Architects (3 Days) Overview This training course covers a wide range of integration solutions
More informationService Oriented Architecture for Architects
www.peaklearningllc.com Service Oriented Architecture for Architects (5 Days) Overview This five day training course for architects delves deep into various architectural aspects of SOA. It starts with
More informationn Real-world Case Study of how LIPA are using a Model-Driven approach, leveraging an Enterprise Semantic Model (ESM) to:
Topics! Real-world Case Study of how LIPA are using a Model-Driven approach, leveraging an Enterprise Semantic Model (ESM) to: Implement Semantic Integration Implement Persistent Data Stores (e.g. for
More informationCIM Forum Charter Dated
CIM Forum Charter Dated 2018-12-18 The information provided below is subject to change and reflects the current state of the CIM Forum charter within the DMTF. Management Problem(s) and Environment The
More informationThe Information Integration Platform
The Information Integration Platform IIS Product and Technology Vision & Roadmap Bob Zurek Director, Advanced Technologies and Product Strategy Information Integration Solutions IBM Software Group IBM
More informationwhite paper: soa and Web Services The Performance Paradox CA Wily Technology
white paper: soa and Web s The Performance Paradox SOA and Web s The Performance Paradox august 2007 CA Wily Technology Table of Contents section 1 3 Introduction section 2 4 Web s and the Problem of SOA
More informationTOGAF 9.1 in Pictures
TOGAF 9. in Pictures The TOGAF ADM Cycle Stage Set up an EA team and make sure it can do its work The ADM is about understanding existing architectures and working out the best way to change and improve
More informationSOA Research Agenda. Grace A. Lewis
Workshop SOA Research Agenda Grace A. Lewis Workshop Approach Broadened the scope of the research agenda to show that we are interested in more than just SOA as an architectural style Performed an extensive
More informationTOGAF Foundation. Part I: Basic Concepts 1 /
TOGAF Foundation Part I: Basic Concepts 1 / Enterprise and Enterprise Architecture An Enterprise is any collection of organizations that has a common set of goals, for example: Government agency Whole
More informationInformation Sharing Environment Interoperability Framework (I 2 F)
Information Sharing Environment Interoperability Framework (I 2 F) Making Interoperability Common Presented to Collaboration and Transformation SIG Getting on the Same Page (Definitions) What is Information
More informationThe Role of the Architect. The Role of the Architect
The Role of the Architect Jason Bloomberg Senior Analyst ZapThink, LLC Take Credit Code: ROLEARCH Copyright 2006, ZapThink, LLC 1 The Role of the Architect Design Governance Project Management Organizational
More informationToolbox for Architecture Framework Discussions at The Open Group. SKF Group, February 2018
Toolbox for Architecture Framework Discussions at The Open Group SKF Group, February 2018 Toolbox Overview Components in our Enterprise Architecture Management: APPROACH FRAMEWORK CONTENT TOOLBOX Architecture
More informationService Orientation for the Design of HLA Federations
Service Orientation for the Design of HLA Federations Anthony Cramp, Tom van den Berg, Wim Huiskamp TNO Oude Waalsdorperweg 63 2597 AK The Hague The Netherlands {anthony.cramp, tom.vandenberg, wim.huiskamp}@tno.nl
More informationzapnote Analyst: Ronald Schmelzer
zapthink zapnote ZAPTHINK ZAPNOTE Doc. ID: ZTZN-1201 Released: Oct. 6, 2006 SOA SOFTWARE EXPANDING THE BREADTH OF SOA INFRASTRUCTURE Analyst: Ronald Schmelzer Abstract Throughout the past year, the pace
More informationRational Unified Process (RUP) in e-business Development
Rational Unified Process (RUP) in e-business Development Jouko Poutanen/11.3.2005 2004 IBM Corporation Agenda Characteristics of e-business Development Business Modeling with RUP and UML Rational Tools
More informationChapter 6. A Look at Service-Driven Industry Models
Chapter 6 A Look at Service-Driven Industry Models The Enterprise Service Model The Virtual Enterprise Model The Capacity Trader Model The Enhanced Wholesaler Model The Price Comparator Model The Content
More informationSOA Maturity Assessment using OSIMM
SOA Maturity Assessment using OSIMM Presented by: Andras R. Szakal IBM Distinguished Engineer VP & CTO, IBM US Federal SWG SOA Tutorial - Architecture Slide 1 of 28 What You Will Learn The Open Group SOA
More informationIBM s SOA Quality Management Strategy with Rational and Tivoli Terry Goldman Technical Evangelist Rational Software IBM ASEAN/SA
IBM s SOA Quality Management Strategy with Rational and Tivoli Terry Goldman Technical Evangelist Rational Software IBM ASEAN/SA IBM Rational Software Development Conference 2007 2007 IBM Corporation What
More informationService Identification: BPM and SOA Handshake
Service Identification: Srikanth Inaganti & Gopala Krishna Behara Abstract Service identification is one of the first steps in the Service Oriented Development life cycle. This has been challenging to
More informationThe Annotated SOA Manifesto
Chinese Dutch English French German Portuguese Russian Spanish The Annotated SOA Manifesto Commentary and Insights about the SOA Manifesto from Thomas Erl Service orientation is a paradigm that frames
More informationCHAPTER 7 SOA DEVELOPMENT LIFECYCLE SE 458 SERVICE ORIENTED ARCHITECTURE
CHAPTER 7 SOA DEVELOPMENT LIFECYCLE SE 458 SERVICE ORIENTED ARCHITECTURE Assist. Prof. Dr. Volkan TUNALI Faculty of Engineering and Natural Sciences / Maltepe University Topics 2 SOA Design & Development
More informationIT6801 / Service Layers/ A.Kowshika SERVICE LAYERS
1 SERVICE LAYERS Service-orientation and contemporary SOA 2 / 19 Contemporary SOA is a complex and sophisticated architectural platform that offers significant potential to solve many historic and current
More informationCONVERGENCE OF CLOUD COMPUTING, SERVICE ORIENTED ARCHITECTURE AND ENTERPRISE ARCHITECTURE
CONVERGENCE OF CLOUD COMPUTING, SERVICE ORIENTED ARCHITECTURE AND ENTERPRISE ARCHITECTURE Susan Sutherland (nee Rao) University of Canberra PO Box 148, Jamison Centre, ACT 2614, Australia Susan.sutherland@canberra.edu.au
More informationService-Oriented Architecture Trends. Business Constant: Change
Service-Oriented Architecture Trends Jason Bloomberg Senior Analyst ZapThink, LLC Take Credit Code: SOATIBM Business Constant: Change Competition Changing Marketplace Customer Demands Mergers & Acquisitions
More informationAndrew Macdonald ILOG Technical Professional 2010 IBM Corporation
The value of IBM WebSphere ILOG BRMS Understanding the value of IBM WebSphere ILOG Business Rule Management Systems (BRMS). BRMS can be used to implement and manage change in a safe and predictable way
More informationبﻟﺎطﻣ ﯽﻠﮐ لﺻﻓ رﺳ Se rvice O r ien t A rch it ec t SOA Workshop: A. Mahjoorian, Session
- معماری سرویس گرا (SOA) قسمت ھفتم - مرداد 86 امیر رضا مهجوریان دوره آموزشی شرکت... سر فصل کلی مطالب معرفی معماری سرویس گرا کاربرد معماری سرویس گرا شناخت تفصیلی ادبیات کسب و کار پروتکل ھای معماری سرویس
More informationPresented at the 2009 ISPA/SCEA Joint Annual Conference and Training Workshop - Making the Case for SOA Arlene F.
Making the Case for SOA Arlene F. Minkiewicz Introduction A Service Oriented Architecture (SOA) is a computing environment in which applications are composed, rather than developed, through a set of standard
More informationzapnote CYSIVE Briefing Date: May 29, 2002 Analyst: Ronald Schmelzer
zapthink zapnote -`````````````````````````````````````` ZAPTHINK ZAPNOTE Doc. ID: ZTZN-0307-1D Released: July 15, 2002 CYSIVE SIMPLIFYING THE INTERACTION WITH WEB SERVICES Briefing Date: May 29, 2002
More informationData and Information. Work session for Non-Practitioners
Data and Information Work session for Non-Practitioners Eight Dimensions of an Organisation Strategy Governance Investment Policy Standards Performance Business Data and Information Application and Software
More informationBusiness Process Management with SAP NetWeaver. Thomas Volmering Senior Product Manager SAP NetWeaver BPM & BAM SAP AG
Business Process with SAP NetWeaver Thomas Volmering Senior Product Manager SAP NetWeaver BPM & BAM SAP AG BUSINESS PROCESS MANAGEMENT Motivation SAP AG 2004, BPM / Volmering / 2 Why Business Process?
More informationAnalyze, Design, and Develop Applications
Analyze, Design, and Develop Applications On Demand Insurance Problems 1. We lose customers because we process new policy applications too slowly. 2. Our claims processing is time-consuming and inefficient.
More informationSOA Best Practices & Framework Services in Order to Invoice Enterprise Application Integrations
SOA Best Practices & Framework Services in Order to Invoice Enterprise Application Integrations A White Paper Oracle Collaborate, April 2008 By Raman D. Singh Consulting Manager, SOA Practice Protégé Software
More informationService Virtualization
Service Virtualization A faster, more efficient and less costly way to develop and test enterprise-class applications As cloud and mobile computing gain rapid acceptance, IT departments are expected to
More informationEnhancing. PeopleSoft Applications With Oracle Fusion Middleware
Enhancing PeopleSoft Applications With Oracle Fusion Middleware Page 1 of 6 Introduction Changing markets, increasing competitive pressures, and evolving customer needs are placing greater pressure on
More information