Service Description
Definitions
Term: Service Description |
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) |
|||||
Service Infrastructure (KM-SI) |
|||||
Generic (domain independent) |
A service description is an information artifact containing not only a description of the service interfaces. It defines the message formats, datatypes, transport protocols, and transport serialization formats that should be used between the requester agent and the provider agent. It also specifies one or more network locations at which a provider agent can be invoked, and may provide some information about the message exchange pattern that is expected. In essence, the service description represents an agreement governing the mechanics of interacting with that service. [W3C] __ALT__ A Service Description allows the users to access a service regardless of where and whom it is actually offered. It specifies all the information needed to the potential consumers to access and use the service. [PO-JRA-1.1.1] __ALT__ The Service Description is provided by the service provider during the service publication, and it’s used by the service consumer to choose the correct service during the service discovery. [CD-JRA-1.1.2]
|
Competencies
- POLIMI: Adaptive Web Services; http://home.dei.polimi.it/pernici/ws-research.html; Barbara Pernici, Danilo Ardagna, Pierluigi Plebani, Cinzia Cappiello, Marco Comuzzi, Kyriakos Kritikos
- POLIMI: Dependable Evolvable Pervasive SE; http://deepse.dei.polimi.it/; Carlo Ghezzi, Elisabetta Di Nitto, Valentina Mazza, Andrea Mocci, Luca Cavallaro, Daniel Dubois
- UOC: Formal description languages providing enriched service behavior specification primitives (pre-/post-conditions, service invariants, quality of service) with the use of ontologies for complex services; http://www.ics.forth.gr/isl/r-d-activities/soc.html; Dimitris Plexousakis, Kyriakos Kritikos, George Baryannis
- CITY: Service-centric systems engineering; http://hcid.soi.city.ac.uk/research/Secse.html; Neil Maiden, Kos Zachos, Angela Kounkou
- Tilburg: Service Design & Modeling Methodologies; http://www.tilburguniversity.nl/eriss/research/; Vasilios Andrikopoulos, Mike Papazoglou, Michael Parkin
Scenarios
- Original Equipment Automotive Supply Chain (Case Study Solution -> Implementation)
References
- [PO-JRA-1.1.1] "State of the art report on software engineering design knowledge and Survey of HCI and contextual Knowledge"
- [W3C]
Booth D., Haas H., McCabe F., Newcomer E., Champion M., Ferris C.,
Orchard D., Web Services Architecture,
http://www.w3.org/TR/ws-arch/
- [CD-JRA-1.1.2] "Separate Design Knowledge models for software engineering and service-based computing."