Interoperability and Service Oriented Architecture an Enterprise Architect's approach
|
|
- Henry O’Connor’
- 5 years ago
- Views:
Transcription
1 Interoperability and Service Oriented Architecture an Enterprise Architect's approach Peter Bernus and Ovidiu Noran 1 Griffith University, Nathan (Brisbane) Queensland 4111, Australia P.Bernus@griffith.edu.au, O.Noran@griffith.edu.au Abstract. The paper presents a business model for creating and sustaining networked organisations, as well as the principles, policies, processes and information deemed necessary to achieve interoperability. The business model not only includes business units, but also the supporting infrastructure, business- and technology development programmes, as well as projects to perform the developments needed to achieve intra- and inter-organisational interoperability. In particular, the conditions are discussed under which a service oriented architecture (SOA) approach can support interoperability, applied both as an organisational design principle and as a way to structure the IT infrastructure. Finally, the forces that limit the use of this approach are also mentioned. Keywords: Interoperability, Service Oriented Architecture, Enterprise Architecture. 1 Introduction Interoperability as a condition has always been necessary for business, and the concept itself is not related to information technology. The authors define interoperability as the ability of two entities to access, exchange, and correctly interpret information provided to one another. Effectively this condition allows two entities to jointly participate in business processes and thus act together (or interoperate). If entities (companies) want to exchange information through automated means then there is an obvious need for technical interoperability (with the associated multitude of standards in the multi-layered stack of communication) however, correct interpretation is only possible if the structure and the meaning of the exchanged information is mutually known (which is the condition called semantic interoperability [1]). The existence of languages and techniques to define standards for technical and semantic interoperability is only an enabler because the conditions for interoperability need to be created through social and business intentions, and sometimes through legislation. There are forces in business and government that favour the development of interoperability standards (e.g. without interoperability standards certain markets would not be able to exist), but competitive forces can also
2 work against interoperabilty, because the lack of interoperability can exclude entrants to markets and can be a protection of monopolies and work against the interests of Small and Medium sized Enterprises. Therefore, a generic business model that defines the scope of the interoperability problem also needs to include the roles of government (regulatory bodies) and industry associations. For a considerable amount of time practitioners concentrated on the technical aspects of interoperability (including semantic interoperability), and kept predicting practically the same breakthrough results every five years or so. However, the social and business conditions have not been addressed with equal vigour, and it is only recently that these conditions (and what to do about them) have been given serious attention. For the reasons given above, this article develops a dynamic business model that maps the scope of the interoperability problem and gives equal coverage to technical, business and regulatory aspects. 1 (a) 1. Identification (a) of the entity and its role in the business 2 (b) 2. The Concept of the entity: Mission, vision, strategic objectives, policies, principles and values (b) (c) 3 (e) (m) (i) 4 (k) (g) (d) (f) (j) (n) (h) (l) 3. Requirements (functional and non-functional, such as resource capability, reliability, availability, cost, size, location, etc): - Definition of the (c) mission fulfilment tasks, and (d) management and control tasks of the entity and associated non functional reqs. - Requirements specification of (e) the entity s mission fulfilment, and of (f) management & control (complete and consistent statement of functions, information, and non functional requirements for resources and the organisation of the entity) 4. Preliminary (or Architectural) design: definition of structure of the entity and a mapping of this structure to the requirements specification - Human roles (competencies, skills) in (g) mission fulfilment, and (h) management & control - Human roles (instructions, policies & procedures) in (i) mission fulfilment and (j) management & control - Hardware components (manufacturing, logistics, info and communicationn technology) for (k) mission fulfilment, and (l) management & control - Software components (application programs, database schemata, control software) of the above: (m) for mission fulfilment, (n) for management and control Fig. 1. Entity Life Cycle scope (from Identification to Architectural design) (cf ISO1504:2000)
3 2 Generic Business Model for Networked Organisations The Business Model proposed below is of a special type: entities are represented together with their life cycle and life cycle relationships. The life cycle representation follows ISO15705:2000 [2] / GERAM [5],. According to this standard the life cycle consist of life cycle activity types identification, concept definition, requirements definition, preliminary design, detailed design, implementation (release into operation), operation and decommissioning. There is no implication that this list of activities is performed in the above temporal order (in fact feedback loops exist among these activity types). Note that the way instances of these activity types are performed in time can be represented on the timeline (for example using a GANTT chart.) Figure 1 represents the scope of life cycle activities of an entity and it will be important to read any subsequent figures (Fig 2., etc) with this scope coverage in mind. (NB the scope of the life cycle diagram is not explicitly illustrated in Fig.1 for the detailed design, release to operation, operation and decommissioning phases, but this detail is available for the interested reader in ISO15704:2000). The scope of Identification is the definition of the entity and its role in the business (why it exists, what it does). The Concept definition of the entity must describe: the mission of the entity (what is it that the entity is intended to deliver to its customers), the vision of the entity (if there is a future imagined state of the entity then it needs to be described together with the reason why it is necessary to achieve that state). Furthermore, the Concept definition must include strategic objectives consistent with the vision, as well as policies, principles and values that guide choices in the future development of the entity. Some of the latter can be externally controlled, meaning that the entity does not have a choice whether to adopt them or not (e.g. relevant legislation, social rules, etc), while some others are internal in the sense that it is the entity s choice to adopt them (compliance with some industry standards, human resource principles, manufacturing-, logistic- and information technology principles, financial / asset management principles, process principles, etc). Requirements definition extends to two kinds of requirement statement: the definition of the tasks of the entity and the requirements specification of the entity. What is being called here the tasks of the entity covers both service tasks and management & control tasks, and each of these need to include functional requirements as well as non-functional requirements (such as resource capability, reliability, availability, cost, size, location, etc). The requirements specification of the entity is a complete and consistent statement of the entity s functions, the information that links between these functions, together with all non functional requirements, regarding resources and the organisation of the entity. Importantly, there must be a traceable link between the requirements specification, the tasks, and the elements of the Concept of the entity. The Preliminary (or architectural) design of the entity covers the identification of a structure for the entity (definition of human roles and the definition of automated / hardware and software components, such as for manufacturing, logistics, control system and other information technology) and a mapping of this structure to the requirements specification. Importantly, architectural design decisions must be
4 traceable not only to show that the requirements specification is satisfied, but also to show that these decisions are compatible with all elements of the Concept level description of the entity (compliance with design policies & principles and values). It is relevant to discuss at this point the relationship between policies, principles & values, and the architecture of the entity developed by the preliminary design activity. Any policy, principle or value (henceforth, for simplicity, we just use principle to mean these three) can be satisfied by an entity in two (and only two) ways. An entity can satisfy the principle by design, meaning that after implementation every operational state of the entity automatically complies with the principle. Alternatively, an entity can satisfy a principle by control, meaning that the stated principle is introduced as control information to every relevant activity in the operation of the entity, thus the entity could operate in violation of the principle if it chose to do so. It is during preliminary design that the decision is made to build compliance with a principle into the design or to leave it as a control, and there are important consequences of this when discussing interoperability. E.g. if the designer of the entity decides that compliance with a selected interoperability standard is a principle to be upheld, then there is an architectural design choice regarding how to satisfy this principle. 1) One can design and build the entity entirely out of components that were developed to implement the given interoperability standard. In this case the entity will be locked-in with the standard, implementation cost may be reduced (through the use of off the shelf products) but future changes can become costly. This choice is acceptable if the return on investment of such a dedicated system is likely to be shorter than the expected frequency of change in what the preferred standards are in the given industry. 2) One can build the entity in such a way that only one, or few, small components are compliant with the standard by design, and the rest of the system is only compliant by control. This second choice is typically achieved using some type of middleware, able to translate from a company-internal standard data representation to the external standard. Notice that the decomposition of an entity into its constituents (human roles, hardware and software component systems) is a recursive activity, therefore the compliance with a principle may be enforced by design in one component system while it may be enforced as control in another component. Through this decomposition hierarchy it is possible to find the right level of component system which can be made dedicated to the standard of the day : above this level the system uses the principle (to follow a given standard) as control, whereupon below this level there is at least one component that is dedicated to the given standard and other components can be existing legacy systems, for example. The ability to use the interoperability principle as control (rather than as a design property of the entity in question) is also constrained by the theoretical limitations of information translatability (sometimes the information schema of a company must change otherwise the company can no longer interchange information with supply chain partners). As a result, the compatibility with interoperability standards is more important on the requirements specification level than it is on the architectural or detailed design level., because provided an entity complies with standard information schemata and a standard process nomenclature, the translation between internal and external representations is always achievable through relatively small middleware
5 components. Notice the terminology we used above: an information schema is not necessarily a database schema, thus two companies with compatible information schemata can easily interoperate even though their level of automation (and therefore their database schemata) may be different. Figure 2 represents a business model that includes the company as an entity, other companies (supply chain partners and competitors), a self-regulatory environment (such as an industry alliance, or network) and a governing entity (such as a regulatory body) that provides outside regulation to the given industry (and is not aligned to a select set of companies). We believe that this is a minimal set of players that need to be differentiated according to their role in having an effect on interoperability. 3 Life Cycle Relationships and Feedback Loops Directed arrows in Figure 2 show two types of relationship between entities. If an arrow starts in the operation of an entity and ends in the operation of another entity, then the arrow represents operational interactions. Forms of operational interaction are the exchange of information or material, the participation of an entity in the other entity s process (e.g. through the provision of service). If an arrow starts in the operation of entity A and ends on a life cycle activity of another entity B (except the operation of B), then the interaction is called generative, because A participates in the creation (or change / transformation) of B. For example, an Industry association participates in the work of a Regulatory Body (e.g. industry representatives are members of relevant committees), but the Regulatory Body eventually defines policies and principles (including legislated ones) that define, limit, or otherwise direct the processes or the organisation of the Industry association. This feedback loop is labeled Z in Fig.2. Many additional feedback loops or paths exist in this business model. Some loops are straightforward (like Z ), but some have multiple steps of action. Take for example the path Y V. An Industry Association (representing its members) participates in the operation of a Standards Body. The Standards Body creates standards that can be used (adopted) by supply chain partners as Reference Models (of processes and / or information). These standards in turn influence the way supply chain partners operate; finally, supply chain partners as they operate operationally support Industry Associations thereby closing the loop. To create a successful interoperability standard these feedback loops must be thoroughly understood and the lack of good governance (e.g. through which an Industry Association can voice its members opinions regarding the endorsement (or otherwise) of an interoperability standard is likely to create standards that will not become generally accepted by the given industry. One important role of Regulatory Bodies is (or at least would be) to define principles that govern the participation of industry users, industry associations and of vendors in standards creation, to ensure that standards are not hijacked by special interest groups to the exclusion of others.
6
7 This is not to say that competing standards will not exist at any one moment in time, because existing and emerging new standards are able to create similar divisions. However, Regulatory Bodies can enforce policies that require interoperability standards to be open, allowing open source or in-house implementations, in addition to proprietary ones. Reference models for interoperability include Requirements level models. Requirements level interoperability models further include the definition of typical process building blocks (e.g., Partner Interface Processes defined by Rosettanet [6]), from which building blocks various complete business transactions (processes) may be built. Requirements level interoperability standards also include information models (expressed, for example. as Entity-relationship or UML Class diagrams) and state transition diagrams (determining the relationship between activities in the process model and states of objects in the information model). As noted in Section 2, it is the adoption of such requirements level interoperability standards that make joint operation (or co-operation) between business entities possible. However, efficient joint operation typically also needs comparable levels of automation (see C4ISR/LISI Interoperability Levels [3]). The design level specification of the same standards may be expressed as a translation of the requirements level interoperability standard to workflows (for process standards) and as XML schemata (for information standards). The difference between preliminary design and detailed design level descriptions of these standards are minimal, and concern potential language bindings or other physical schema related information, referring to particular product modules that implement the mentioned process building blocks. However, it is not an interoperability requirement that supply chain partners use the same building blocks in their respective implementations of these standards. Partner interface processes and associated information schemata define reference models for the Application- and Data Services respectively. It is therefore the task of the Business Process management and execution services to invoke either local or remote functions as application services. 4 The Relation Between Service Orientation and Interoperability Implementing application functions as published services has the advantage that supply chain partners are able to define new business processes relying on existing local- and partner functions, rather than local functions alone (see Fig.2, support by Application Services of B i to Business Process Execution Service of entity A ). Notice that each application service has two sides to it (just as any other entity does, as explained in Fig.1): the left hand side refers to the service provided, while the right hand side refers to the management and control of the service. Given that management has strategic, tactical, operational and real time levels, if a business entity (either the company of interest or its partner) wishes to include an application function in a new business process, then that needs to be negotiated with the management of the respective application service. The negotiation includes the definition of the required quality of service, the definition of a service level agreement, the planning for potentially needed resource upgrade, or detailed design
8 change (e.g. database tuning), and the scheduling and supervision of such change (including the supervision of the design, implementation / release into test operation, testing, quality assurance, and final release into operation). Recent experiences with the implementation of Service Oriented Architecture suggest that the above service management and the assurance of the performance and quality of service is essential [4], otherwise the desired business process characteristics can not be guaranteed. As the above discussion shows: the fact that two businesses are interoperable (because of adhering to the same process and information standards) has almost nothing to do with whether these businesses use a Service Oriented Architecture or not! At the same time, to reap the benefits of interoperability technology is needed (on the detailed design level) that allows the interoperability potential to be quickly turned into reality, and SOA technology is one such technology platform which can achieve this. I.e., if supply chain partners implement business functions as published services (using SOA technology) and they are interoperable, then there is a potential for fast configuration of new business processes, which property leads to agility both on the level of the individual company and on the level of the complete supply chain. The use of SOA technology without interoperability standards is possible, but that limits the reuse of application functions to a single company (Company of Interest in Fig.2). Notice also that fast configuration (mentioned above) is not the same as dynamic (or on-demand) configuration, and to the authors knowledge there is no technology available at present for dynamic configuration that would be able to guarantee performance (speed, availability, gracious degradation). Thus interoperability standards and SOA technology are two separate means of improving supply chain integration, but used in combination have the potential of fostering agility and business innovation. 5 Conclusion This short article has demonstrated, through the use of a generic business model, the forces that influence interoperability in the supply chain. The role of regulatory and Standards bodies has been discussed and related to the role of Industry Associations, Major Vendors, and companies (such as SMEs). Various feedback loops in the development of interoperability standards has been discussed and it was argued that the design of the processes behind these feedback loops is essential for the achievement of truly open interoperability standards. The article also concluded that Service Oriented Architecture as a technology is an enabler, which can help members of the supply chain to reap the benefits of interoperability standards and implement agile and innovative business processes.
9 References 1 Grace A. Lewis, G.A., Wrage,L. : Approaches to Constructive Interoperability, CMU/SEI TR-020 Software Engineering Institute, Carnegie-Mellon University (2004). 2 ISO 15704:2000 Industrial Automation Systems -- Requirements for Enterprise Reference Architectures and Methodologies. Geneva : International Standards Organisation (2000) 3 C4ISR Interoperability Working Group: Levels of Information Systems Interoperability (LISI). Department of Defense. Washington, D.C. (1998). 4 Isaacson, C.: High Performance SOA with Software Pipelines. SOA Magazine Issue V, (March 2007) pp1-8 [on-line article published at 5 IFIP-IFAC Task Force, GERAM The Generalised Enterprise Reference Architecture and Methodology. in P. Bernus, L.Nemes and G.Schmidt (Eds) Handbook on Enterprise Architecture. Berlin : Springer Verl. pp RosettaNet Program Office : Overview Clusters, Segments, and PIPS (Version ). Lawrenceville, NJ : Rosettanet (April 2008)
SOC for cybersecurity
April 2018 SOC for cybersecurity a backgrounder Acknowledgments Special thanks to Francette Bueno, Senior Manager, Advisory Services, Ernst & Young LLP and Chris K. Halterman, Executive Director, Advisory
More informationUSA HEAD OFFICE 1818 N Street, NW Suite 200 Washington, DC 20036
US-China Business Council Comments on The Draft Measures for Security Review of Online Products and Services March 6, 2017 On behalf of the more than 200 members of the US-China Business Council (USCBC),
More informationThe below represents a summary of Section 1 of Chapter 9 of the National Integrated ICT Policy White Paper.
Opening Access: Infrastructure and supply-side issues The below represents a summary of Section 1 of Chapter 9 of the National Integrated ICT Policy White Paper. Contents Introduction... 1 Goals... 1 What
More informationIT123: SABSA Foundation Training
IT123: SABSA Foundation Training IT123 Rev.002 CMCT COURSE OUTLINE Page 1 of 8 Training Description: SABSA is the world s leading open security architecture framework and methodology. SABSA is a top-tobottom
More informationEXAM PREPARATION GUIDE
EXAM PREPARATION GUIDE PECB Certified ISO/IEC 38500 Lead IT Corporate Governance Manager The objective of the PECB Certified ISO/IEC 38500 Lead IT Corporate Governance Manager examination is to ensure
More informationISO 55001: 2014 Asset Management System 5-Day Training Course (IAM Certified)
ISO 55001: 2014 Asset Management System 5-Day Training Course (IAM Certified) TÜV SÜD Introduction ISO 55001: 2014 is a newly released best practice standard for asset management. This standard helps to
More informationAddressing interoperability in e-health: an Australian approach
Addressing interoperability in e-health: an Australian approach Zoran Milosevic Deontik Pty Ltd Brisbane, Australia. zoran@deontik.com Abstract This paper describes the use of the ISO ODP family of standards
More informationNATIONAL GUIDELINES ON CLOUD COMPUTING FOR GOVERNMENT, MINISTRIES, DEPARTMENTS AND AGENCIES
NATIONAL GUIDELINES ON CLOUD COMPUTING FOR GOVERNMENT, MINISTRIES, DEPARTMENTS AND AGENCIES DOCUMENT DETAIL Security Classification Unclassified Authority National Information Technology Authority - Uganda
More informationToward Horizon 2020: INSPIRE, PSI and other EU policies on data sharing and standardization
Toward Horizon 2020: INSPIRE, PSI and other EU policies on data sharing and standardization www.jrc.ec.europa.eu Serving society Stimulating innovation Supporting legislation The Mission of the Joint Research
More informationISO/IEC/ IEEE INTERNATIONAL STANDARD. Systems and software engineering Architecture description
INTERNATIONAL STANDARD ISO/IEC/ IEEE 42010 First edition 2011-12-01 Systems and software engineering Architecture description Ingénierie des systèmes et des logiciels Description de l'architecture Reference
More informationGovernment of Ontario IT Standard (GO ITS)
Government of Ontario IT Standard (GO ITS) GO-ITS Number 56.3 Information Modeling Standard Version # : 1.5 Status: Approved Prepared under the delegated authority of the Management Board of Cabinet Queen's
More informationOptimisation drives digital transformation
January 2017 Executive summary Forward-thinking business leaders are challenging their organisations to achieve transformation by harnessing digital technologies with organisational, operational, and business
More informationEUROPEAN ICT PROFESSIONAL ROLE PROFILES VERSION 2 CWA 16458:2018 LOGFILE
EUROPEAN ICT PROFESSIONAL ROLE PROFILES VERSION 2 CWA 16458:2018 LOGFILE Overview all ICT Profile changes in title, summary, mission and from version 1 to version 2 Versions Version 1 Version 2 Role Profile
More informationNext Generation Policy & Compliance
Next Generation Policy & Compliance Mason Karrer, CISSP, CISA GRC Strategist - Policy and Compliance, RSA Core Competencies C33 2013 Fall Conference Sail to Success CRISC CGEIT CISM CISA Introductions...
More informationVdTÜV Statement on the Communication from the EU Commission A Digital Single Market Strategy for Europe
Author Date VdTÜV-WG Cybersecurity October, 3 rd 2015 VdTÜV Statement on the Communication from the EU Commission A Digital Single Market Strategy for Europe VdTÜV e.v. welcomes the Communication on a
More informationContents. List of figures. List of tables. 5 Managing people through service transitions 197. Preface. Acknowledgements.
Contents List of figures List of tables Foreword Preface Acknowledgements v vii viii 1 Introduction 1 1.1 Overview 3 1.2 Context 6 1.3 ITIL in relation to other publications in the Best Management Practice
More informationREPORT 2015/149 INTERNAL AUDIT DIVISION
INTERNAL AUDIT DIVISION REPORT 2015/149 Audit of the information and communications technology operations in the Investment Management Division of the United Nations Joint Staff Pension Fund Overall results
More informationChapter 2 Overview of the Design Methodology
Chapter 2 Overview of the Design Methodology This chapter presents an overview of the design methodology which is developed in this thesis, by identifying global abstraction levels at which a distributed
More informationSNIA/DMTF Work Register. Version 1.4
Page 1 of 5 Background and Purpose SNIA/DMTF Work Register Version 1.4 The SNIA has been working on the development of Storage related standards based upon DMTF technologies for several years. Much of
More informationOASIS BPEL Webinar: Frank Leymann Input
OASIS BPEL Webinar: Frank Leymann Input (OASIS Webinar, March 12th, 2007) Prof. Dr. Frank Leymann Director, Institute of Architecture of Application Systems Former IBM Distinguished Engineer BPEL s Role
More informationGovernment of Ontario IT Standard (GO ITS) GO-ITS Number 56.3 Information Modeling Standard
Government of Ontario IT Standard (GO ITS) GO-ITS Number 56.3 Information Modeling Standard Version # : 1.6 Status: Approved Prepared under the delegated authority of the Management Board of Cabinet Queen's
More information"Charting the Course... Certified Information Systems Auditor (CISA) Course Summary
Course Summary Description In this course, you will perform evaluations of organizational policies, procedures, and processes to ensure that an organization's information systems align with overall business
More informationModule 7 TOGAF Content Metamodel
Module 7 TOGAF Content Metamodel V9 Edition Copyright January 2009 All Slide rights reserved 1 of 45 Published by The Open Group, January 2009 TOGAF Content Metamodel TOGAF is a trademark of The Open Group
More informationSNIA/DMTF Work Register. Version 1.3
Page 1 of 5 Background and Purpose SNIA/DMTF Work Register Version 1.3 The SNIA has been working on the development of Storage related standards based upon DMTF technologies for several years. Much of
More informationCitation for published version (APA): Berthing, H. H. (2014). Vision for IT Audit Abstract from Nordic ISACA Conference 2014, Oslo, Norway.
Aalborg Universitet Vision for IT Audit 2020 Berthing, Hans Henrik Aabenhus Publication date: 2014 Document Version Early version, also known as pre-print Link to publication from Aalborg University Citation
More informationData Governance Central to Data Management Success
Data Governance Central to Data Success International Anne Marie Smith, Ph.D. DAMA International DMBOK Editorial Review Board Primary Contributor EWSolutions, Inc Principal Consultant and Director of Education
More informationData Center Management and Automation Strategic Briefing
Data Center and Automation Strategic Briefing Contents Why is Data Center and Automation (DCMA) so important? 2 The Solution Pathway: Data Center and Automation 2 Identifying and Addressing the Challenges
More informationInformation technology Service management. Part 10: Concepts and vocabulary
Provläsningsexemplar / Preview INTERNATIONAL STANDARD ISO/IEC 20000-10 First edition 2018-09 Information technology Service management Part 10: Concepts and vocabulary Technologies de l'information Gestion
More informationSOME TYPES AND USES OF DATA MODELS
3 SOME TYPES AND USES OF DATA MODELS CHAPTER OUTLINE 3.1 Different Types of Data Models 23 3.1.1 Physical Data Model 24 3.1.2 Logical Data Model 24 3.1.3 Conceptual Data Model 25 3.1.4 Canonical Data Model
More informationALC ONLINE COMPLIANCE TOOL REASONABLE ENQUIRY USER GUIDE
ALC ONLINE COMPLIANCE TOOL REASONABLE ENQUIRY USER GUIDE Document Version: v3 Oct 2015 TABLE OF CONTENTS Introduction...3 Software Requirements...4 Reasonable Enquiries...6 Creating a Reasonable Enquiry...7
More informationCyber Security Guidelines for Defining NIAP Scope Statements
Cyber Security Guidelines for Defining NIAP Scope Statements Version 1.1 Author: Cyber Security Policy and Standards Document Published Date: June 2018 Document History: Version Description Date 1.0 Published
More informationNOW IS THE TIME. to secure our future
NOW IS THE TIME to secure our future A FRAMEWORK FOR UNITING THE CANADIAN ACCOUNTING PROFESSION VISION FOR THE PROFESSION To be the pre-eminent, internationally recognized Canadian accounting designation
More informationWeb Services. Chirag Mehta
Web Services Chirag Mehta Web Service From W3C A Web service is a software system identified by a URI, whose public interfaces and bindings are defined and described using XML. Its definition can be discovered
More informationASSURING DATA INTEROPERABILITY THROUGH THE USE OF FORMAL MODELS OF VISA PAYMENT MESSAGES (Category: Practice-Oriented Paper)
ASSURING DATA INTEROPERABILITY THROUGH THE USE OF FORMAL MODELS OF VISA PAYMENT MESSAGES (Category: Practice-Oriented Paper) Joseph Bugajski Visa International JBugajsk@visa.com Philippe De Smedt Visa
More informationMaking hybrid IT simple with Capgemini and Microsoft Azure Stack
Making hybrid IT simple with Capgemini and Microsoft Azure Stack The significant evolution of cloud computing in the last few years has encouraged IT leaders to rethink their enterprise cloud strategy.
More information10 Steps to Building an Architecture for Space Surveillance Projects. Eric A. Barnhart, M.S.
10 Steps to Building an Architecture for Space Surveillance Projects Eric A. Barnhart, M.S. Eric.Barnhart@harris.com Howard D. Gans, Ph.D. Howard.Gans@harris.com Harris Corporation, Space and Intelligence
More informationISO/IEC/ IEEE Systems and software engineering Content of life-cycle information items (documentation)
This is a preview - click here to buy the full publication INTERNATIONAL STANDARD ISO/IEC/ IEEE 15289 Second edition 2015-05-15 Systems and software engineering Content of life-cycle information items
More informationThe Bank of Russia Standard FINANCIAL MESSAGES IN THE NPS
The Bank of Russia Standard STO BR NPS-1.0-2017 FINANCIAL MESSAGES IN THE NPS GENERAL TERMS Introduction date: 2017-03-20 Official publication Moscow 2017 Preamble 1. ACCEPTED AND ENACTED by The Bank of
More informationWhen Communities of Interest Collide: Harmonizing Vocabularies Across Operational Areas C. L. Connors, The MITRE Corporation
When Communities of Interest Collide: Harmonizing Vocabularies Across Operational Areas C. L. Connors, The MITRE Corporation Three recent trends have had a profound impact on data standardization within
More informationCritical Information Infrastructure Protection Law
Critical Information Infrastructure Protection Law CCD COE Training 8 September 2009 Tallinn, Estonia Maeve Dion Center for Infrastructure Protection George Mason University School of Law Arlington, Virginia.
More informationThe Analysis and Proposed Modifications to ISO/IEC Software Engineering Software Quality Requirements and Evaluation Quality Requirements
Journal of Software Engineering and Applications, 2016, 9, 112-127 Published Online April 2016 in SciRes. http://www.scirp.org/journal/jsea http://dx.doi.org/10.4236/jsea.2016.94010 The Analysis and Proposed
More information# 47. Product data exchange using STEP
# 47 Product data exchange using STEP C. Demartini, S. Rivoira, A. Valenzano CENS and Dip. di Automatica e Informatica, Politecnico c.so Duca degli Abruzzi, 24 10129 Torino (Italy) tel. +39-11-5647016,
More informationProposed Revisions to ebxml Technical Architecture Specification v ebxml Business Process Project Team
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 Proposed Revisions to ebxml Technical Architecture Specification v1.0.4 ebxml Business Process Project Team 11
More informationDesigning a System Engineering Environment in a structured way
Designing a System Engineering Environment in a structured way Anna Todino Ivo Viglietti Bruno Tranchero Leonardo-Finmeccanica Aircraft Division Torino, Italy Copyright held by the authors. Rubén de Juan
More informationIntroduction to ISO/IEC 27001:2005
Introduction to ISO/IEC 27001:2005 For ISACA Melbourne Chapter Technical Session 18 th of July 2006 AD Prepared by Endre P. Bihari JP of Performance Resources What is ISO/IEC 17799? 2/20 Aim: Creating
More informationI D C T E C H N O L O G Y S P O T L I G H T
I D C T E C H N O L O G Y S P O T L I G H T P ow e ring Digital Transfor m a t i o n T h r ough the C l o u d - R e a d y E n t e r p rise September 2016 Adapted from Developing a Cloud Strategy for Digital
More informationISO/IEC INTERNATIONAL STANDARD. Information technology Software asset management Part 1: Processes and tiered assessment of conformance
INTERNATIONAL STANDARD This is a preview - click here to buy the full publication ISO/IEC 19770-1 Second edition 2012-06-15 Information technology Software asset management Part 1: Processes and tiered
More informationThe Open Group SOA Ontology Technical Standard. Clive Hatton
The Open Group SOA Ontology Technical Standard Clive Hatton The Open Group Releases SOA Ontology Standard To Increase SOA Adoption and Success Rates Ontology Fosters Common Understanding of SOA Concepts
More informationHierarchy of knowledge BIG DATA 9/7/2017. Architecture
BIG DATA Architecture Hierarchy of knowledge Data: Element (fact, figure, etc.) which is basic information that can be to be based on decisions, reasoning, research and which is treated by the human or
More informationBCS Practitioner Certificate in Integrating Off-the-shelf Software Solutions Syllabus
BCS Practitioner Certificate in Integrating Off-the-shelf Software Solutions Syllabus Version 2.5 April 2017 This qualification is not regulated by the following United Kingdom Regulators - Ofqual, Qualification
More informationISO/IEC/ IEEE INTERNATIONAL STANDARD
This is a preview - click here to buy the full publication INTERNATIONAL STANDARD ISO/IEC/ IEEE 26531 First edition 2015-05-15 Systems and software engineering Content management for product lifecycle,
More informationProposed Revisions to ebxml Technical. Architecture Specification v1.04
Proposed Revisions to ebxml Technical Architecture Specification v1.04 Business Process Team 11 May 2001 (This document is the non-normative version formatted for printing, July 2001) Copyright UN/CEFACT
More informationGOVERNANCE, RISK MANAGEMENT AND COMPLIANCE TRENDS BY FCPAK ERIC KIMANI
GOVERNANCE, RISK MANAGEMENT AND COMPLIANCE TRENDS BY FCPAK ERIC KIMANI CONTENTS Overview Conceptual Definition Implementation of Strategic Risk Governance Success Factors Changing Internal Audit Roles
More informationStandard Setting and Revision Procedure
Better Cotton Initiative Standard Setting and Revision Procedure BCI-PRO-01 (V2-0) EN Title: Document reference code: Standard Setting and Revision Procedure BCI-PRO-01-V2 Approval : BCI Council, January
More informationE-Commerce Integration Meta-Framework Introduction (ECIMF-Intro) CEN/ISSS/WS-EC/ECIMF. Draft, version 0.3 November 28, 2001
1 E-Commerce Integration Meta-Framework Introduction (ECIMF-Intro) CEN/ISSS/WS-EC/ECIMF Draft, version 0.3 November, 001 1 0 3 3 3 3 0 1. Background and the Goal Statement There have been many standardization
More informationMemorandum of Understanding
Memorandum of Understanding between the European Commission, the European Union Agency for Railways and the European rail sector associations (CER, EIM, EPTTOLA, ERFA, the ERTMS Users Group, GSM-R Industry
More informationProtect Your End-of-Life Windows Server 2003 Operating System
Protect Your End-of-Life Windows Server 2003 Operating System Your guide to mitigating risks in your Windows Server 2003 Systems after the end of support End of Support is Not the End of Business When
More informationConference for Food Protection. Standards for Accreditation of Food Protection Manager Certification Programs. Frequently Asked Questions
Conference for Food Protection Standards for Accreditation of Food Protection Manager Certification Programs Frequently Asked Questions Q. What was the primary purpose for the Conference for Food Protection
More informationClosing the Hybrid Cloud Security Gap with Cavirin
Enterprise Strategy Group Getting to the bigger truth. Solution Showcase Closing the Hybrid Cloud Security Gap with Cavirin Date: June 2018 Author: Doug Cahill, Senior Analyst Abstract: Most organizations
More informationEnterprise Data Architecture: Why, What and How
Tutorials, G. James, T. Friedman Research Note 3 February 2003 Enterprise Data Architecture: Why, What and How The goal of data architecture is to introduce structure, control and consistency to the fragmented
More informationVendor: The Open Group. Exam Code: OG Exam Name: TOGAF 9 Part 1. Version: Demo
Vendor: The Open Group Exam Code: OG0-091 Exam Name: TOGAF 9 Part 1 Version: Demo QUESTION 1 According to TOGAF, Which of the following are the architecture domains that are commonly accepted subsets of
More informationAustralian Standard. Records Management. Part 2: Guidelines AS ISO ISO TR
AS ISO 15489.2 2002 ISO TR 15489-2 AS ISO 15489.2 Australian Standard Records Management Part 2: Guidelines [ISO title: Information and documentation Records management Part 2: Guidelines] This Australian
More informationUnofficial Comment Form Project Operating Personnel Communications Protocols COM Operating Personnel Communications Protocols
Project 2007-02 Operating Personnel Communications Protocols COM-002-4 Operating Personnel Communications Protocols Please DO NOT use this form. Please use the electronic comment form to submit comments
More informationDATA PROCESSING TERMS
DATA PROCESSING TERMS Safetica Technologies s.r.o. These Data Processing Terms (hereinafter the Terms ) govern the rights and obligations between the Software User (hereinafter the User ) and Safetica
More informationDefining the Challenges and Solutions. Resiliency Model. A Holistic Approach to Risk Management. Discussion Outline
Resiliency Model A Holistic Approach to Risk Management Discussion Outline Defining the Challenges and Solutions The Underlying Concepts of Our Approach Outlining the Resiliency Model (RM) Next Steps The
More informationPrivacy Policy. In this data protection declaration, we use, inter alia, the following terms:
Last updated: 20/04/2018 Privacy Policy We are very delighted that you have shown interest in our enterprise. Data protection is of a particularly high priority for the management of VITO (Vlakwa). The
More informationHCL GRC IT AUDIT & ASSURANCE SERVICES
HCL GRC IT AUDIT & ASSURANCE SERVICES Overview The immense progress made in information and communications technology offers enterprises outstanding benefits. However this also results in making the risk
More informationFive Key Considerations for Selecting Cloud Recovery Services
Five Key Considerations for Selecting Cloud Recovery Services Looking for a cloud-based solution for backup and recovery? Here are some important things to keep in mind when interviewing providers. By
More informationTaming Rave: How to control data collection standards?
Paper DH08 Taming Rave: How to control data collection standards? Dimitri Kutsenko, Entimo AG, Berlin, Germany Table of Contents Introduction... 1 How to organize metadata... 2 How to structure metadata...
More informationDRAFT. Cyber Security Communications between Control Centers. March May Technical Rationale and Justification for Reliability Standard CIP-012-1
DRAFT Cyber Security Communications between Control Centers Technical Rationale and Justification for Reliability Standard CIP-012-1 March May 2018 NERC Report Title Report Date I Table of Contents Preface...
More informationInformation Bulletin
Application of Primary and Secondary Reference Documents Version 1.1 Approved for release July 2014 Table of Contents 1.0 Purpose statement... 3 2.0 Audience... 3 3.0 BCA requirements and referenced documents...
More informationA2A EAI. Overview and recommendations Data Transport. Jerome CAPIROSSI. people are keen to argue since they find themselves to be affected.
. EAI A2A EAI Overview and recommendations Jerome CAPIROSSI Abstract Since customers or corporate users get various terminals (Phone, PDAs, Web, Workstation, ) and therefore various channels for connecting
More informationPrinciples for a National Space Industry Policy
Principles for a National Space Industry Policy Commonwealth of Australia 2011 DIISR 11/144 This work is copyright. Apart from any use as permitted under the Copyright Act 1968, no part may be reproduced
More informationMutual Recognition Agreement/Arrangement: General Introduction, Framework and Benefits
Conformity and Interoperability Training for SADC Region on Type Approval testing for Mobile Terminals, Homologation Procedures and Market Surveillance Mutual Recognition Agreement/Arrangement: General
More informationSeven Requirements for Successfully Implementing Information Security Policies and Standards
Seven Requirements for Successfully Implementing and Standards A guide for executives Stan Stahl, Ph.D., President, Citadel Information Group Kimberly A. Pease, CISSP, Vice President, Citadel Information
More informationSubmission. to the. Australian Communications and Media Authority. on the. Cellular mobile repeaters a proposed regulatory approach
Submission to the Australian Communications and Media Authority on the Cellular mobile repeaters a proposed regulatory approach Submission by: Australian Mobile Telecommunications Association and Communications
More informationAccelerate Your Enterprise Private Cloud Initiative
Cisco Cloud Comprehensive, enterprise cloud enablement services help you realize a secure, agile, and highly automated infrastructure-as-a-service (IaaS) environment for cost-effective, rapid IT service
More informationSOLUTION BRIEF RSA ARCHER IT & SECURITY RISK MANAGEMENT
RSA ARCHER IT & SECURITY RISK MANAGEMENT INTRODUCTION Organizations battle growing security challenges by building layer upon layer of defenses: firewalls, antivirus, intrusion prevention systems, intrusion
More informationDeliver robust products at reduced cost by linking model-driven software testing to quality management.
Quality management White paper September 2009 Deliver robust products at reduced cost by linking model-driven software testing to quality management. Page 2 Contents 2 Closing the productivity gap between
More informationATTACHMENT C. Workforce Innovation and Opportunity Act SAMPLE Memorandum of Understanding Template
This Sample Memorandum of Understanding (MOU) Template is intended to be a technical assistance tool rather than a required template; it should be used in whatever way best fits the needs of the Local
More informationelements) and on the structure and representation of the information (i.e. the message format).
Introduction to MDMI The global financial industry exchanges huge amounts of electronic information. Differences in understanding and interpretation of exchanged electronic information form an important
More informationProposal for Business Transaction Protocol Version 1.0
Proposal for Business Transaction Protocol Version 1.0 Sanjay Dalal (sanjay.dalal@bea.com) Pal Takacsi-Nagy (pal.takacsi@bea.com) Abstract Long lasting business transactions spanning multiple enterprises
More informationcameo Enterprise Architecture UPDM / DoDAF / MODAF / SysML / BPMN / SoaML USER GUIDE version 17.0
cameo Enterprise Architecture UPDM / DoDAF / MODAF / SysML / BPMN / SoaML USER GUIDE version 17.0 No Magic, Inc. 2010 All material contained herein is considered proprietary information owned by No Magic,
More informationEvents Will Transform Application Servers
Technology, Y. Natis Research Note 8 July 2003 Events Will Transform Application Servers Today's application servers can act as simple "event servers." To handle complex events, application servers will
More informationAudit Considerations Relating to an Entity Using a Service Organization
An Entity Using a Service Organization 355 AU-C Section 402 Audit Considerations Relating to an Entity Using a Service Organization Source: SAS No. 122; SAS No. 128; SAS No. 130. Effective for audits of
More informationBest Practices for Deploying Web Services via Integration
Tactical Guidelines, M. Pezzini Research Note 23 September 2002 Best Practices for Deploying Web Services via Integration Web services can assemble application logic into coarsegrained business services.
More informationFundamentals to Creating Architectures using ISO/IEC/IEEE Standards
Fundamentals to Creating Architectures using ISO/IEC/IEEE Standards What to Architect? How to Architect? IEEE Goals and Objectives Chartered by IEEE Software Engineering Standards Committee to: Define
More informationCustomer Functions Service Provider Role Paper
Background Customer Functions Service Provider Role Paper One of the General Policy Principles in all jurisdictions for small customers was to ensure that all parties who provide access to enable provision
More informationEnterprise models for enterprise architecture and ISO9000:2000
Annual Reviews in Control 27 (2003) 211 220 Enterprise models for enterprise architecture and ISO9000:2000 Peter Bernus School of Computing and Information Technology, Griffith University, Nathan, Qld
More informationOPPORTUNITY TO ACCELERATE MOMENTUM
OPPORTUNITY TO ACCELERATE MOMENTUM Pierre-Paul Allard Chief Customer Officer Juniper Networks CAUTIONARY STATEMENTS Forward-Looking Statements. This presentation contains forward-looking statements within
More informationDATACENTER SERVICES DATACENTER
SERVICES SOLUTION SUMMARY ALL CHANGE React, grow and innovate faster with Computacenter s agile infrastructure services Customers expect an always-on, superfast response. Businesses need to release new
More informationDeveloping Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach
Developing Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach Ninat Wanapan and Somnuk Keretho Department of Computer Engineering, Kasetsart
More informationInformation technology Security techniques Guidance on the integrated implementation of ISO/IEC and ISO/IEC
Provläsningsexemplar / Preview INTERNATIONAL STANDARD ISO/IEC 27013 Second edition 2015-12-01 Information technology Security techniques Guidance on the integrated implementation of ISO/IEC 27001 and ISO/IEC
More informationArchitecture and Standards Development Lifecycle
Architecture and Standards Development Lifecycle Architecture and Standards Branch Author: Architecture and Standards Branch Date Created: April 2, 2008 Last Update: July 22, 2008 Version: 1.0 ~ This Page
More informationICB Industry Consultation Body
ICB Industry Consultation Body Evolution of network management 17/11/2016 Issue Position Paper Long-term evolution of Network Management This position paper is intended to form the basis of advice to the
More informationArtop (AUTOSAR Tool Platform) Whitepaper
Artop (AUTOSAR Tool Platform) Whitepaper Updated version: March 2009 Michael Rudorfer 1, Stefan Voget 2, Stephan Eberle 3 1 BMW Car IT GmbH, Petuelring 116, 80809 Munich, Germany 2 Continental, Siemensstraße
More informationAdaptive Internet Data Centers
Abstract Adaptive Internet Data Centers Jerome Rolia, Sharad Singhal, Richard Friedrich Hewlett Packard Labs, Palo Alto, CA, USA {jar sharad richf}@hpl.hp.com Trends in Internet infrastructure indicate
More information6. The Document Engineering Approach
6. The Document Engineering Approach DE + IA (INFO 243) - 11 February 2008 Bob Glushko 1 of 40 Plan for Today's Class Modeling Methodologies The Document Engineering Approach 2 of 40 What Modeling Methodologies
More informationIntegrating TOGAF, Zachman and DoDAF Into A Common Process
Integrating TOGAF, Zachman and DoDAF Into A Common Process Rolf Siegers Senior Principal Software Systems Engineer The Open Group Architecture Practitioner s Conference October 2003 Customer Success Is
More informationContribution of France Telecom to the public consultation of the ERG. IP interconnection. November 2006
Contribution of France Telecom to the public consultation of the ERG on IP interconnection November 2006 General comments France Telecom welcomes the opportunity to contribute to ERG s consultation on
More information