Home > SOA Glossary > Functional Expression Standardization

Functional Expression Standardization

Service contracts delivered or extended by different projects and at different times are naturally shaped by the various architects and developers that are required to work with them. The manner in which the service context and the service's individual capabilities are defined and expressed through the contract syntax can therefore vary. Some may use overly verbose conventions, while others may use a terse and highly technical format. Furthermore, the actual terms used to express common or similar capabilities may vary across services.

Because services are positioned as enterprise resources, it is fully expected that other project teams will need to discover and interpret the contract in order to be understand how they can use the service.

Inconsistencies in how technical service contracts are expressed undermine these efforts by introducing a constant risk of misinterpretation on a technical level. The proliferation of these inconsistencies furthermore places a convoluted face on a service inventory, increasing the effort to effectively navigate various contracts to study possible composition design options.


Standardized naming conventions can be applied to the delivery of all services so as to ensure the consistent expression of service contexts and capabilities. This approach is referred to as functional expression standardization.

See also: