Difference between revisions of "Services-SAIF"
m (Created page with "'''Service-aware''' Service-aware includes the inclusion of services, such as business processes, in the HL7 interoperability standard, as well as the exchange of [[Message-SAIF...") |
m |
||
| Line 1: | Line 1: | ||
| − | ''' | + | '''Services''' |
| + | |||
| + | Services are on- or-more series of activities of intangible nature that normally, but not necessarily, take place in interactions between customers and service employees and/or physical resources or goods and/or systems of the service provider, which are provided as solutions to customer problems [Gronroos, 1990]. Services are a means of organizing a set of resources according to business-oriented priorities. A service thus provide a primary means of integration between two organization’s business processes and/or data in a controlled, managed, and well-defined (contract-based) manner. A service is an abstract specification that explicitly defines both the static (“payload”) and dynamic (“functional and behavioral”) semantics necessary to unambiguously support a testable, enforceable contract between two enterprise-level components. | ||
| − | |||
[[Category:SAIF Glossary]] | [[Category:SAIF Glossary]] | ||
[[User:Ajulian|Tony Julian]] 21:07, 20 April 2011 (UTC) | [[User:Ajulian|Tony Julian]] 21:07, 20 April 2011 (UTC) | ||
Latest revision as of 21:07, 20 April 2011
Services
Services are on- or-more series of activities of intangible nature that normally, but not necessarily, take place in interactions between customers and service employees and/or physical resources or goods and/or systems of the service provider, which are provided as solutions to customer problems [Gronroos, 1990]. Services are a means of organizing a set of resources according to business-oriented priorities. A service thus provide a primary means of integration between two organization’s business processes and/or data in a controlled, managed, and well-defined (contract-based) manner. A service is an abstract specification that explicitly defines both the static (“payload”) and dynamic (“functional and behavioral”) semantics necessary to unambiguously support a testable, enforceable contract between two enterprise-level components.
Tony Julian 21:07, 20 April 2011 (UTC)
