This glossary supports the following titles:

SOA Governance

SOA with .NET & Azure


SOA Design Patterns


Web Service Contract Design & Versioning for SOA


SOA Principles of Service Design

Service-Oriented Architecture: Concepts, Technology, and Design

Modern SOA Infrastructure: Technology, Design, and Governance
SOA with REST: Principles, Patterns & Constraints
Next Generation SOA: A Real-World Guide to Modern Service-Oriented Computing
SOA with Java
SOA Security: Practices, Patterns, and Technologies for Securing Services
SOA and Cloud Computing: Practices, Patterns, Technologies

This glossary also supports the SOA Certified Professional (SOACP) program.

For more information, visit: www.soacp.com
and
www.soaschool.com


|
|
|

contract-to-functional coupling

|
Service logic can be dependent on outside business processes, especially when the logic was designed directly in support of these processes. This can result in contract-to-functional coupling whereby the contract expresses characteristics that are specifically related to the parent process logic.


Services based on the task service model are intentionally coupled to a business process, and therefore this form of coupling is expected. However, with agnostic services, contract-to-functional coupling is generally considered a negative type of coupling because it imposes parent process logic details upon service consumer programs that may be affected when the process logic changes.

See also:

- contract-to-logic coupling

- contract-to-implementation coupling

- contract-to-technology coupling

- logic-to-contract coupling

- Service Loose Coupling

- task service

|
|