Personal tools
You are here: Home Knowledge Model REPOSITORY of Terms S Service Design

Service Design

by Dinh Khoa Nguyen last modified Apr 26, 2012 12:24
— filed under:

Definitions

Term:
<term>
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)
Designing a service-oriented application requires developers to define related well documented interfaces for all conceptual services identified by the analysis phase prior to constructing them. The service design phase encompasses the steps of singular service specification, business process specification, and policy specification for both singular services as well as business processes. Service design is based on a twin- track design approach that provides two production lines one along the logical part and one along the physical part of the SOA abstraction layers. The purpose of logical service design is to define singular services and assemble (compose) services out of reusable singular service constellations. This calls for a business process model that forces developers to determine how services combine and interact jointly to produce higher level services. The physical design trajectory focuses on how to design component implementations that implement services at an acceptable level of granularity. Physical design is based on techniques for leveraging legacy applications and component-based development techniques.

[Papazoglou 2007]



 

Competencies

External Competencies

 

References

  • [Papazoglou 2007] Michael P. Papazoglou, Web Services: Principles and Technology, Prentice Hall,  2007
Document Actions
  • Send this
  • Print this
  • Bookmarks

The Plone® CMS — Open Source Content Management System is © 2000-2017 by the Plone Foundation et al.