IOPE
by
Manuel Carro
—
last modified
Apr 26, 2012 22:26
—
filed under:
KnowledgeModel
Definitions
Term: IOPE |
Domain: Cross-cutting issues | ||||
---|---|---|---|---|---|
Engineering and Design (KM-ED) |
Adaptation and Monitoring (KM-AM) |
Quality Definition, Negotiation and
Assurance (KM-QA) |
Generic (domain independent) |
||
D o m a i n : L a y e r s |
Business Process Management (KM-BPM) |
||||
Service Composition and
Coordination (KM-SC) |
IOPE is an acronym that stands for Input, Output, Precondition and Effects [OWL-S]. It forms part of the functional description of a Web service, which relates the capabilities of the service. Inputs and outputs represent the information transformation performed by a service, describing the information required by a service in order to produce a new set of information as a result of the execution. Preconditions and effects represent the state change that is also performed by the service. The former represent conditions that should be true for the successful execution of the service, while the latter represent the conditions that become true after a successful execution. | ||||
Service Infrastructure (KM-SI) |
|||||
Generic (domain independent) |
Competencies
- UoC: Service Specification; http://www.uoc.gr; George Baryannis, Dimitris Plexousakis.
- UPM: Service Specification; http://www.upm.es; Manuel Carro.
References
- [OWL-S] W3C, OWL-S: Semantic Markup Language, 2004, http://www.w3.org/Submission/OWL-S/