Service Realization Strategy
by
Dinh Khoa Nguyen
—
last modified
Apr 26, 2012 12:25
—
filed under:
KnowledgeModel
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) |
Service providers consider the following
four realization options (which may be mixed in various combinations)
to develop new business processes [Brittenham
2001]: 1. Green-field development: This step involves describing how a new interface for a singular Web service will be created on the basis of the Web service implementation. Green field development assumes that first a service is implemented and subsequently the service interface is derived from the new Web service implementation. 2. Top-down development: Using this realization option a new singular service can be developed that conforms to an existing service interface. This type of service interface is usually part of an industry standard that can be developed by any number of service providers. Processes are usually deployed in a top-down fashion from a business level process blueprint. [Graham 2005]. 3. Bottom-up development: SOA implementation strategy rarely starts on a green field and almost always integrates existing systems. Using this option a new singular service interface is developed for an existing application. This option usually involves creating a Web service interface from the API of the application that implements the Web service. . 4. Meet-in-the-middle- development: This option is used when an already existing Web service interface - for which an implementation already exists – is partially mapped onto a new service or process definition. This option involves service realizations that mix services and service-enabled implementations. This approach may thus involve creating a wrapper for the existing applications that need to be service-enabled and that are to be combined with the already existing Web service interface. [Papazoglou 2007] |
||||
Competencies
- Tilburg: Service Design & Modeling Methodologies; http://www.tilburguniversity.nl/eriss/research/; Willem-Jan van den Heuvel, Khoa Nguyen, Mike Papazoglou
References
- [Brittenham 2001] P. Brittenham, F. Curbera, D. Ehnebuske, and S.
Graham, "Understanding WSDL in a UDDI Registry", IBM developerWorks,
September 2001
- [Graham 2005] S. Graham et al, Building Web Services with Java, 2nd
Edition, SAMS Publishing, 2005
- [Papazoglou 2007] Michael P. Papazoglou, Web Services: Principles
and Technology, Prentice Hall, 2007
