Service Analysis
by
Dinh Khoa Nguyen
—
last modified
Apr 26, 2012 12:24
—
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) |
The service analysis phase is based on a thorough
business case analysis whose main purpose is to identify the
requirements of a SOA-based implementation. This includes reviewing the
business
goals and objectives of an enterprise that drive the development of
business
processes. The analysis phase helps focus SOA initiatives by
creating a high-level process map that identifies business domains and business
processes of particular interest to an enterprise. Business
processes are ranked by criteria related to business value and
impact, reuse and high consumption, feasibility and technical viability
[Marks 2006]. From the process map business analysts can identify
candidate business services that relate to these business
processes. Candidate business services are services that have
potential value for an organization [Marks 2006]. They can be evaluated
based on reuse, business impact, and organizational value, and are
subsequently analyzed to find what kind of business logic should be
encapsulated in each of them and finally designed. Service analysis
helps prioritize business processes and services where
SOA can contribute to improvements and offer business value potential
and helps centre efforts on business domains within an enterprise that
can be mapped to core business processes. Service analysis aims at identifying, conceptualizing and rationalizing business processes as a set of interacting Web services. In particular, the analysis phase places emphasis on identifying and describing the processes and services in a business problem domain and on discovering potential overlaps and discrepancies between processes under construction and available system resources that are needed to realize singular Web services and business processes. It therefore examines the existing services portfolio at the service provider’s side to understand which patterns are in place and which need to be introduced and implemented. [Papazoglou 2007] |
||||
Competencies
- Tilburg: Service Design & Modeling Methodologies; http://www.tilburguniversity.nl/eriss/research/; Willem-Jan van den Heuvel, Khoa Nguyen, Mike Papazoglou
External Competencies
- IBM Zurich: Service-Oriented Analysis and Design; http://www.zurich.ibm.com/~olz/; Olaf Zimmerman
References
- [Marks 2006] E. A. Marks, M.Bell, Service-oriented Architecture: A Planning and Implementation Guide for Business and Technology, John Wiley & Sons, 2006
- [Papazoglou 2007] Michael P. Papazoglou, Web Services: Principles
and Technology, Prentice Hall, 2007
