Service Identification Methods: A Systematic Literature Review <s> Web service (WS) <s> Service-oriented system engineering (SOSE) has drawn increasing attention since service-oriented computing was introduced in the beginning of this decade. A large number of SOSE challenges that call for special software engineering efforts have been proposed in the research community. Our goal is to gain insight into the current status of SOSE research issues as published to date. To this end, we conducted a systematic literature review exploring SOSE challenges that have been claimed between January 2000 and July 2008. This paper presents the results of the systematic review as well as the empirical research method we followed. In this review, of the 729 publications that have been examined, 51 were selected as primary studies, from which more than 400 SOSE challenges were elicited. By applying qualitative data analysis methods to the extracted data from the review, we proved our hypotheses about the classification scheme. We are able to conclude that the SOSE challenges can be classified along two dimensions: (a) based on themes (or topics) that they cover and (b) based on characteristics (or types) that they reveal. By analyzing the distribution of the SOSE challenges on the topics and types in the years 2000–2008, we are able to point out the trend in SOSE research activities. The findings of this review further provide empirical evidence for establishing future SOSE research agendas. <s> BIB001 </s> Service Identification Methods: A Systematic Literature Review <s> Web service (WS) <s> Thank you for reading service oriented architecture soa compass business value planning and enterprise roadmap. As you may know, people have look hundreds times for their chosen books like this service oriented architecture soa compass business value planning and enterprise roadmap, but end up in harmful downloads. Rather than enjoying a good book with a cup of coffee in the afternoon, instead they cope with some malicious bugs inside their desktop computer. <s> BIB002 </s> Service Identification Methods: A Systematic Literature Review <s> Web service (WS) <s> Thank you for downloading service oriented architecture concepts technology and design. Maybe you have knowledge that, people have look numerous times for their chosen readings like this service oriented architecture concepts technology and design, but end up in malicious downloads. Rather than enjoying a good book with a cup of tea in the afternoon, instead they are facing with some malicious virus inside their laptop. <s> BIB003
A service that is implemented using the web service technology. This type is orthogonal to the other types S1,S2,S4,S5,S20,S30 7 Partner service (PS) A service that is offered to external partners. S3,S16,S17,S26,S29 5 On the other hand, it is worth noticing that the numbers of SIMs for identifying IT services and partner services is relatively low and lower than we expected. Business-IT alignment is recognized as a research challenge BIB001 and the need of integrating technical architecture (e.g. IT infrastructure, data models) with business architecture (e.g. business models, organizational structure) has been widely agreed BIB002 BIB003 . As shown in Table 2 , all 9 SIMs that do consider IT services also identify business services and more importantly, they pay specific attention to the integration of business and IT. This alignment should, in our opinion, be supported by all the SIMs, which points out a gap in those SIMs lacking support for IT services. As for partner services, we see that only 5 SIMs lead to services that explicitly consider their service providers (SPs) and consumers (SCs). Services are designed, developed, provided, maintained and owned by SPs. The task of SCs is to discover and compose services fulfilling their needs. SI for SPs entails how to identify services that are potentially useful to others. For SCs, it, instead, entails how to identify services for integration purposes. Because of this difference, a SIM should explicitly indicate which role it supports. Unfortunately, most of the SIMs fail to highlight this difference. Despite that the separation of SPs and SCs is considered as one of the main characteristics of SOA, these two roles are often not explicitly considered in service engineering in general, as found by a survey of SOA methodologies that we reported in  . Further, 7 SIMs explicitly aim at identifying web services without describing any of the types described above. That is why we regard web service as a special type, orthogonal to the others. Interestingly, nearly all of these SIMs (except for S1) rely on legacy systems. Types of output format. Different SIMs also describe the identified services in multiple ways and in multiple levels of detail. Some SIMs describe their output in terms of a list of services with short descriptions; whereas some others illustrate their output in terms of a model describing the relation between services and sometimes with other artifacts of the system. To understand better the outputs of the SIMs, we analyzed the ways that the SIMs describe their identified services. As a result, five different ways of describing services have been identified, as summarized in Table 3 . 