Menu

You are here

Home » Enterprise Technology Dictionary » Find Terms by Theme » Find Terms by Theme: Integration and Interoperability

Find Terms by Theme: Integration and Interoperability

Application

Definition:

A computer program or set of programs that meet a defined set of business needs.  A program or group of programs designed for end users. These programs are divided into two classes: system software and application software. While system software consists of low-level programs that interact with computers at a basic level, application software resides above system software and includes applications such as database programs, word processors and spreadsheets. Application software may be grouped along with system software or published alone. For the purposes of integration applications consume an integration service such as a web service or API.

Application Integration

Definition:
Enterprise application integration EAI use of software and computer systems architectural principles to integrate a set of enterprise computer applications, furthermore, the process of keeping redundant copies of data (in independently designed applications) consistent, or enabling end-users to access data and functionality from independently designed applications on a single user interface.
Context:
Integration

Application Programming Interface

Definition:
A set of protocols, routines, functions and/or commands that programmers use to develop software or facilitate interaction between distinct systems. APIs are available for both desktop and mobile use, and are typically useful for programming graphic user interface components, as well as allowing a software program to request and accommodate services from another program. This definition explicitly excludes any "API" that relies on local binding (e.g. via loading a DLL) to function.
Context:
Integration

Data Integration

Definition:
The practices, architectural techniques and tools for achieving the consistent access and delivery of data across the spectrum of data subject areas and data structure types in the enterprise to meet the data consumption requirements of all applications and business processes.
Context:
Integration

Deprecation

Definition:
Act of including Formal notification of the intent to retire some or all components of an Integration service such as API or web service, made some period ahead of time in order to allow consumers the opportunity to update consuming applications.
Context:
Integration

Developer Portal

Definition:
A user-facing web interface that provides a list of available APIs and is a repository for: Documentation, Example requests and output, Specifications Interactive tools (test client) Terms of use Contact information
Context:
Integration

Enterprise Search

Definition:
Enterprise Search includes Query capabilities, Precision / Recall Ranking, Classification and Pattern Matching
Context:
IT Business Function

Extensible Markup Language

Definition:
A simple, very flexible text format derived from SGML. Originally designed to meet the challenges of large-scale electronic publishing, XML is also playing an increasingly important role in the exchange of a wide variety of data on the Web and elsewhere.
Context:
Integration

File Transfer

Definition:
Is the process of copying or moving a file from one computer to another over a network or Internet connection. It enables sharing, transferring or transmitting a file or a logical data object between different users and/or computers both locally and remotely.
Context:
Integration

Graph QL

Definition:
A query language for APIs and a runtime for fulfilling those queries with your existing data. Graph QL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.
Context:
Integration

Information Discovery

Definition:
Information Discovery consists of all activities used to obtain information that is not readily obtainable
Context:
IT Business Function

Information Exchange and Transformation

Definition:
Information Exchange and Transformation - The tools and systems used to search, link, analyze, share and transport information such as reports or critical mission data. Transformation includes the set of capabilities to support the removal of incorrect or unnecessary characters and data from a data source
Context:
IT Business Function

Integration

Definition:
Technology-centric term primarily concerned with connecting IT systems.
Context:
Integration

Integration Hub

Definition:
A flexible architectural pattern that allows for a reuse and reduction in the number of interfaces, reducing and/or eliminating point-to-point integration.  A hub also allows for centralization of data and functionality.
Context:
Integration

Integration Layer

Definition:
Provides a level of indirection between the consumer of functionality and its provider. A service consumer interacts with the service provider via the Integration Layer. Hence, each service interface is only exposed via the Integration Layer (e.g., ESB), never directly and point-to-point integration is done at the Integration Layer instead of consumers/requestors doing it themselves. Consumers and providers are decoupled; this decoupling allows integration of disparate systems into new solutions.
Context:
Integration

Integration Service Catalog

Definition:
A user-facing web interface that provides a list of available APIs and is a repository for: Documentation, Example requests and output, Specifications Interactive tools (test client) Terms of use Contact information
Context:
Integration

Interface

Definition:
Shared boundary between two functional units, defined by various characteristics pertaining to the functions, physical interconnections, signal exchanges, and other characteristics, as appropriate.
Context:
Integration

Interface Library

Definition:
A user-facing web interface that provides a list of available APIs and is a repository for: Documentation, Example requests and output, Specifications Interactive tools (test client) Terms of use Contact information
Context:
Integration

Interoperability

Definition:
A business-centric term regarding the interconnection of business processes. Imply exchanges between a range of products, or similar products from several different vendors, or even between past and future revisions of the same product. Interoperability may be developed post-facto, as a special measure between two products, while excluding the rest, by using Open standards.
Context:
Integration

IT System Development / Integration Support

Definition:

IT System Development / Integration Support includes the software services enabling elements of distributed business applications to interoperate and the software development necessary to facilitate such integration. These elements can share function, content, and communications across heterogeneous computing environments

JavaScript Object Notation

Definition:

A lightweight data-interchange format. It is a language independent text format that is easy for humans to read and write. It is easy for machines to parse and generate.

Context:
Integration

Modularity

Definition:

Modularity refers to the extent to which a software/Web application may be divided into smaller modules. Software modularity indicates that the number of application modules are capable of serving a specified business domain. Allows typical applications to be divided into modules, as well as integration with similar modules, which helps developers use prewritten code. Modules are divided based on functionality, and programmers are not involved with the functionalities of other modules. Thus, new functionalities may be easily programmed in separate modules. It is a practical application of the principle of "Separation of Concerns" by dividing a complex system into simpler and more manageable modules that will work together Modularization can take place in two ways: The Composition or bottom-up approach takes modules and puts them together to form a larger system The alternative approach is to take a complete system and decompose it into its modules. This approach is known as the decomposition or top-down approach. Modules are technically connected to one another. The measure of inter-module relation is known as coupling. Design goals require modules to have low-coupling and high cohesion. Cohesion is a measure of the inter-relatedness of elements (statements, procedures, declarations) within a module. A module is said to have high cohesion if all the elements in the module are strongly connected with one another. Tight coupling of modules makes analysis, understanding, modification and testing of modules difficult. Reuse of modules is also hindered. Modularity enhances the understandability of software systems and change process. Developers need not have to understand the entire system for changes to be made as details are localized into components; modularity separates concerns down to the modules and is thus a direct realization of the principle of "Separation of Concerns"

Context:
Integration

Open API

Definition:

An open source specification to define a standard, language-agnostic interface to REST APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a minimal amount of implementation logic.

Context:
Integration

Representational State Transfer API

Definition:

A distributed system framework that uses Web protocols and technology. The REST architecture involves client and server interactions build around the transfer of resources. Systems that conform to REST principles are referred to as RESTful.

Context:
Integration

Secure File Transfer Protocol (SFTP) (FTP over SSH)

Definition:

A secure version of File Transfer Protocol (FTP), which facilitates data access and data transfer over a Secure Shell (SSH) data stream. It is part of the SSH Protocol. This term is also known as SSH File Transfer Protocol.

Context:
Integration

Service Consumer (Consumer)

Definition:

A requestor that consumes or uses an automated IT Service provided by a Service Provider. Entities (systems, people, and organizations) that needs to make use of services offered by providers.

Synonyms:
Context:
Integration

Service Metadata

Definition:

Computer application readable description of capabilities, requirements, general characteristics, abstract message operations, concrete network protocols, endpoint addresses, and structure and content of messages received by and sent by the service.

Context:
Integration

Service Orchestration

Definition:

The coordination and arrangement of multiple services exposed as a single aggregate service. Developers utilize service orchestration to support the automation of business processes by loosely coupling services across different applications and enterprises and creating "second-generation," composite applications. In other words, service orchestration is the combination of service interactions to create higher-level business services.

Context:
Integration

Service Oriented Architecture

Definition:

Style of software design where services are provided to the other components by application components, through a communication protocol over a network. The basic principles of service-oriented architecture are independent of vendors, products and technologies. A service is a discrete unit of functionality that can be accessed remotely and acted upon and updated independently, such as retrieving a credit card statement online. According to TOGAF, under the terms of an SOA, a service has four properties: It logically represents a business activity with a specified outcome. It is self-contained. It is a black box for its consumers. It may consist of other underlying services.

Context:
Integration

Service Providers (Provider)

Definition:

Entities (systems, people, and organizations) that offer capabilities and act as service providers. An authoritative/trusted organization that offers an automated IT Service to a Service Consumer by means of one of its Provided Service Interfaces.

Context:
Integration

Service Reusability

Definition:

A service-oriented architecture design principle for creating services that can be used for business purposes beyond those initially specified in requirements. Reusable services are designed so their solution logic is independent of any particular business process or technology.

Context:
Integration

Simple Object Access Protocol API

Definition:

A protocol for implementing Web Services. SOAP features guidelines that allow communication via the Internet between two programs, even if they run on different platforms, use different technologies and are written in different programming languages.

Context:
Integration

SOA Backplane

Definition:

Shared, common infrastructure for lifecycle management such as a services registry, policies, business analytics; routing/addressing, quality of service, communication; Development Tools for security, management, and adapters.

Context:
Integration

SOA-based Services

Definition:

Modular, swappable functions, separate from, yet connected to an application via well-defined interfaces to provide agility. Often referred to as 'services' they: Perform granular business functions such as "get customer address" or larger ones such as 'process payment.' Are loosely coupled to a new or existing application. Have capability to perform the steps, tasks and activities of one or more business processes. Can be combined to perform a set of functions - referred to as 'orchestration.'

Context:
Integration

Web Service

Definition:

A software service used to communication between two devices on a network. More specifically, a Web service is a software application with a standardized way of providing interoperability between disparate applications. It does so over HTTP using technologies such as XML, SOAP, WSDL, and UDDI.

Context:
Integration

Web Services Description Language

Definition:

An XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint.

Context:
Integration

Web Services Federation Language

Definition:

An OASIS specification that defines mechanisms to allow different security realms to federate, such that authorized access to resources managed in one realm can be provided to security principles whose identities and attributes are managed in other realms. This includes mechanisms for brokering of identity, attribute, authentication and authorization assertions between realms, and privacy of federated claims.

Context:
Integration

Web Services Security

Definition:

An OASIS specification that proposes a standard set of SOAP extensions that can be used when building secure Web services to implement message content integrity and confidentiality.

Context:
Integration