[Thesis notes] tracing ing service-oriented system engineering challenges: a systematic literature review (SoC

Source: Internet
Author: User

Time: 5.0 hours
Gu, Q. and P. Lago,Indexing ing service-oriented system engineering challenges: a systematic literature review. Service oriented computing and applications, 2009. 3 (3): p. 171-188.

The author, Qing Gu, is a faculty member at the University of Amsterdam (VU Universiteit). His main research direction is "software ubuntures enabling next-generation services ". most of his papers are from the high level perspective (e.g. review, challenges, guideline ). thesis list:
On service-oriented using tural concerns and viewpoints . In 8th working IEEE/ifip Conference on Software Architecture (wicsa) 2009. Cambridge, UK: IEEE, 4 pages, to appear.
Guiding the service engineering process: the importance of service aspects . In 2nd ifip wg5.8 workshop on enterprise interoperability (iwei 2009). 2009. Valencia, Spain: Springer, 14 pages, to appear.
" Indexing ing service-oriented system engineering challenges: a systematic literature review , "In service oriented computing and application. Springer Verlag, 2009, 28 pages.
SOA demo-making-what do we need to know . Proceedings ICSE Workshop on sharing and reusing relational tural knowledge (shark 2009), IEEE Computer Society, pp 25-32
SOA Process decisions: New Challenges in architectural Knowledge Modeling . 3rd workshop on sharing and reusing linked tural knowledge (shark), co-located with ICSE, Leipzig, Germany, May 2008, 8 pages.
A stakeholder-driven service life cycle model for SOA . In 2nd International Workshop on Service Oriented Software Engineering: in conjunction with the 6th esec/FSE Joint Meeting (Dubrovnik, Croatia, September 03-03,200 7 ). the IW-SOSWE '07. ACM, New York, NY, 1-7.
A model for processing the service-oriented software engineering (Sose) Challenges . 2nd European young researchers Workshop on service oriented computing (yrsoc), June 2007, pp.44-49.

The following are the thesis notes.

1. This article is a summary Article .
Summary type : Systematic literature review
Summary object : Service-Oriented System Engineering (sose) Challenges
Target document time : Jan 2000 ~ July 2008
Target document source : IEEE certificate e, ACM digital library, ISI Web of knowledge, springerlink, sciencedirect, Wiley inter Science Journal Finder
Related Data : 729 publications (examined), 51 publications (selected as primary studies), 400 sose challenges (elicited)
Two classification methods are proposed. : (1) based on themes (or topics) (2) Base on characteristics (or types)
Findings and conclusions :
(1) sose emergence laws (S3)
Continuous expectations: the higher the expectations, the more work is dedicated to identifying challenges
Growing understandablity: the better the challenges are understood, the more work is dedicated to overcome the challenges
(2) more business-related challenges and challeges will SS other domains will emerge in the coming year
(3) The summary shows that few challenges are directly targeted at service discovery, but many challenges are indirectly targeted at service discovery.
(4) data-related sose challenges require more attention
(5) No challenges for QoS or characteristics found in, which may indicate "the QoS challenges have reached their saturation, and focus is being put on engineering solutions.". (s4.3.2)
(6) The author believes that sose challenges is currently in the slope of Enlightnment phase of Gartner Hype cycle. (s4.1)
Application :
(1) By classifying different challenges, we can find the internal connection between challeges of different topics/types.

2. related Concepts
systematic (literature) Review : A Literature Review focused on a single question that tries to identify, appraise, select and synthesize all high quality research evidence relevant to that question. @ Wikipedia: "System Overview"
sose : addresses systematic, disciplined and quantifiable approaches to develop service-oriented systems.
sose challenges : sose-related problems or issues that demand research efforts.

3. (S2) discuss the author's research methods
(S2.1) describes the functions and steps of Systematic Research (Plan-> conducting-> Report)
(S2.2) raised research questions
(S2.3) is the planning step of the author's systematic summary, which includes the following five parts:
(1) determine data sources
(2) Determine search strategy
The author uses the keyword search (SoseAndChallenge), The search statement is as follows:

Search for abstract objects.
(3) filter rules
The author defines several inlucsion and exclusion rules.
(4) Data Extraction
Use endnote to record paper entries and establish a correspondence relationship between the paper and challenges. The challenge is "smallest unit" and cannot be decomposed into small challenge.
(5) data synthesis
Classify challenge by using methods such as "reciprocal translation", "line of argument synthesis", and "grounded theory method ".

4. The author of (S5) discussed the effectiveness of the survey.

5. The author used six academic databases, some of which were first-hand databases (for example, IEEE lead E) and some secondary databases (for example, ISI Web of knowledge ).
Therefore, the search results contain repeated records, which require support from tools or human flesh.
In addition, this document does not use EI village as a data source. I feel that the EI Database may include the most comprehensive content in all databases, but the quality of the indexed articles varies greatly, there are a lot of bad papers.
Most of the papers published by IEEE are indexed by ei. Many of ACM's papers are not indexed by ei. Springer and Elsevier (that is, sciencedirect) are almost all indexed by ei.
If only one database can be selected, EI is the most appropriate choice.

Appendix: List of topics summarized

An overview of the number of sose challenges of each topic each year

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.