This document provides standards to agency architects, developers, and system integrators regarding the modeling and description of services.
The concept of a service is fundamental to the state's overall approach to system integration, as defined in the Conceptual Integration Technical Reference Architecture ([TRA]†). A service is the way in which the provisioner of a capability (for example, an agency that owns and maintains an information system) makes that capability available to others.
By making capabilities available through services, rather than making the capabilities directly available to others, agencies avoid introducing technical dependencies between systems that make them difficult to change.
The [TRA] provides a complete definition and discussion of these concepts; the reader should interpret and understand the standards in this document within the context of the [TRA].
An architect, developer, or system integrator who wishes to use a service to access a capability must have a detailed description of the service. This description must include:
A complete and detailed description of the effect of using the service; that is, what (in business terms) can be accomplished by using the service to access the capability A description of the actions supported by the service (that is, how does the developer use the service to accomplish the effect?)
A definition of the information exchanged during interaction with the service The purpose of the standards in this document is to promote consistency in these descriptions across the state enterprise. The rationale section of the document below identifies the benefits expected to result from this consistency in documentation.