SOA Glossary - functional expression standardization

Arcitura IT Certified Professionals (AITCP) International SOA & Cloud Symposium Series Prentice Hall Service-Oriented Computing Series Arcitura IT Certified Professionals (AITCP) International SOA & Cloud Symposium Series Prentice Hall Service-Oriented Computing Series Arcitura IT Certified Professionals (AITCP) International SOA & Cloud Symposium Series Prentice Hall Service-Oriented Computing Series Arcitura YouTube Channel

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

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.