Academia.eduAcademia.edu

Figure 3 – uploaded by Hafedh Mili

See full PDFdownloadDownload figure
Table 9: Validation results of the service-identification taxonomy 7.3. Validation Results

Table 9 Validation results of the service-identification taxonomy 7.3. Validation Results

Related Figures (3)

Table 1: Inputs of Service Identification Approaches(SC for Source Code, DB for Database, LogT for Log Traces, UAI for User Application Interaction, BPM for Business Process Model, UC for Use Case, AD for Activity diagram, DFD for Data Flow Diagram, SMD for State Machine Diagram, Ont for Ontology, Hu.Exp for Human Expertise, Doc for documentation)
Table 1: Inputs of Service Identification Approaches(SC for Source Code, DB for Database, LogT for Log Traces, UAI for User Application Interaction, BPM for Business Process Model, UC for Use Case, AD for Activity diagram, DFD for Data Flow Diagram, SMD for State Machine Diagram, Ont for Ontology, Hu.Exp for Human Expertise, Doc for documentation)
Table 2: Targeted techniques of SIAs
Table 2: Targeted techniques of SIAs
7.1.2. Selection of the Participants to identify broad issues related to legacy-to-SOA migration in general and SIAs in particular. We then performed an axial coding to identify relationships among the identified issues. We identified major issues related to our taxonomy using meta-codes, which we then used to code manually the data of all the interviewees [7]. We targeted developers with an industrial experience in SOA migration. Identifying and soliciting such developers was challenging. We relied on (1) information about com- panies that offer modernization services, (2) online pre- sentations and webinars made by legacy-to-SOA migra- tion experts, and (3) search queries on LinkedIn profiles: “legacy migration OR legacy modernization OR SOA ar- chitect OR SOA migration OR Cloud migration OR ser- vice migration OR service mining”. We attempted neither to be exhaustive in our search for participants nor to cover different strata of developers working on SOA migration. As such, our sample is a random sample of convenience.
7.1.2. Selection of the Participants to identify broad issues related to legacy-to-SOA migration in general and SIAs in particular. We then performed an axial coding to identify relationships among the identified issues. We identified major issues related to our taxonomy using meta-codes, which we then used to code manually the data of all the interviewees [7]. We targeted developers with an industrial experience in SOA migration. Identifying and soliciting such developers was challenging. We relied on (1) information about com- panies that offer modernization services, (2) online pre- sentations and webinars made by legacy-to-SOA migra- tion experts, and (3) search queries on LinkedIn profiles: “legacy migration OR legacy modernization OR SOA ar- chitect OR SOA migration OR Cloud migration OR ser- vice migration OR service mining”. We attempted neither to be exhaustive in our search for participants nor to cover different strata of developers working on SOA migration. As such, our sample is a random sample of convenience.
Related topics:
Information SystemsComputer ScienceSoftware EngineeringUsabilitySystems Software
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved