<!-- copy5c29e9b479c74d99a66577483b7e9586 -->
# Glossary for Integration Assessment
<table>
<tr>
<th valign="top">
Term
</th>
<th valign="top">
Definition
</th>
</tr>
<tr>
<td valign="top">
Application
</td>
<td valign="top">
A software solution \(SaaS or on-premise\) used in the integration landscape.
</td>
</tr>
<tr>
<td valign="top">
Business solution request
</td>
<td valign="top">
A business solution request represents the key entity for an integration requirement from a business standpoint.
</td>
</tr>
<tr>
<td valign="top">
Deployment model
</td>
<td valign="top">
Identifies how the software is hosted, for example, in the public cloud or on-premise.
For example, the deployment mode *public cloud* applies when the software is provisioned to multiple customers for open use via the Internet.
</td>
</tr>
<tr>
<td valign="top">
Integration domain
</td>
<td valign="top">
Area in a hybrid landscape where integration is needed, for example, on-premise-to-cloud or cloud-to-cloud integration.
Identifying integration domains provides the entry point into SAP Integration Solution Advisory Methodology.
Integration domains are technology-agnostic and therefore help to create a blueprint for a hybrid integration platform consisting of multiple integration services and technologies \(SAP or non-SAP\).
You can do an assessment of your integration architecture by specifying the integration domains that are relevant for your organization or that you want to further evaluate.
See: [Integration Domains](integration-domains-e8360d2.md)
</td>
</tr>
<tr>
<td valign="top">
Integration Areas
</td>
<td valign="top">
A combination of integration domain and integration style.
You can do an assessment of your integration architecture by specifying the integration patterns that are relevant for your organization or that you might want to further evaluate.
</td>
</tr>
<tr>
<td valign="top">
Integration policy
</td>
<td valign="top">
Rule that describes how to use an integration technology in a dedicated context.
SAP Integration Solution Advisory Methodology foresees various levels of recommendation degrees that you can assign to integration technologies or services in your organization. This allows you to define integration guidelines for your organization, including default recommendations, reasonable alternatives, possible exceptions, or techniques that you would like to avoid in your organization.
For each integration technology, the supported integration domains are also indicated.
</td>
</tr>
<tr>
<td valign="top">
Integration style
</td>
<td valign="top">
Basic integration category or type, for example, process integration or the integration with things.
Integration styles are the key pillar of ISA-M. Each integration style has specific characteristics and can be refined with use case patterns. All integration styles are technology-agnostic and are applicable within multiple integration domains. You can do an assessment of your integration architecture by adding the integration styles that are relevant for your organization or that you like to evaluate further.
See: [Integration Styles and Integration Use Case Patterns](integration-styles-and-integration-use-case-patterns-770909d.md)
</td>
</tr>
<tr>
<td valign="top">
Integration technology
</td>
<td valign="top">
Middleware component that helps you solve your integration challenge.
Integration Assessment comes with a predefined list of SAP integration technologies. You can also specify custom integration technologies.
</td>
</tr>
<tr>
<td valign="top">
Integration use case pattern
</td>
<td valign="top">
Frequently found integration use cases in enterprise landscapes.
Integration use case patterns refine the integration styles identified for your organization's integration strategy.
You can do an assessment of your integration architecture by adding the integration use case patterns that are relevant for your organization or that you want to evaluate. You can also remove integration use case patterns that are not relevant in your organization.
See: [Integration Styles and Integration Use Case Patterns](integration-styles-and-integration-use-case-patterns-770909d.md)
</td>
</tr>
<tr>
<td valign="top">
Interface request
</td>
<td valign="top">
An interface request represents the key entity for an integration requirement from a technical standpoint.
</td>
</tr>
<tr>
<td valign="top">
Key characteristic
</td>
<td valign="top">
Help enterprise architects and integration architects to map integration styles to relevant capabilities of integration technologies.
You can use the listed criteria as a starting point for discussion. You can further refine these criteria in your specific context.
See: [Key Characteristics](key-characteristics-c16258e.md)
</td>
</tr>
<tr>
<td valign="top">
SAP Integration Solution Advisory Methodology
\(ISA-M\)
</td>
<td valign="top">
Methodology that helps you to blueprint an integration reference architecture for your organization in a structured way.
ISA-M provides you with a structured approach that helps you to assess your integration strategy.
See: [SAP Integration Solution Advisory Methodology](sap-integration-solution-advisory-methodology-a2e17f3.md)
</td>
</tr>
</table>
