Scribd
Upload
6 views6 pages

Microservice Logical Coupling A Preliminary Validation-Word

This document discusses the concept of Microservice Logical Coupling (MLC) and proposes a metric for measuring it based on version control commits, validated with a dataset of 145 open-source microservices. Future research plans include exploring decoupling events, validating the metric's effectiveness, and identifying common coupling patterns. Additionally, the document outlines a systematic literature review on DevOps practices, challenges, and benefits within organizations, detailing the research methodology and criteria for selecting relevant studies.

Uploaded by

tariq aziz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views6 pages

Microservice Logical Coupling A Preliminary Validation-Word

This document discusses the concept of Microservice Logical Coupling (MLC) and proposes a metric for measuring it based on version control commits, validated with a dataset of 145 open-source microservices. Future research plans include exploring decoupling events, validating the metric's effectiveness, and identifying common coupling patterns. Additionally, the document outlines a systematic literature review on DevOps practices, challenges, and benefits within organizations, detailing the research methodology and criteria for selecting relevant studies.

Uploaded by

tariq aziz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Microservice Logical Coupling: A Preliminary Validation

1. Introduction
Coupling is one of the most frequently mentioned metric in software systems. However, to measure
logical coupling between microservices, runtime information is needed or the availability of
service-log files to analyze the calls between services is required. This work presents our emerging
results, in which we propose a metric to statically calculate logical coupling between microservices
based on commits to versioning systems. We performed an initial validation of the proposed metric
with a dataset containing 145 open-source microservices projects.

Therefore, we defined Microservice Logical Coupling (MLC) as follows:

Let’s m1, m2 two microservices and f1, f2 two files related, respectively,
to m1 and m2, then:

m1⇔MLCm2=def{10if f1 and f2 changed in same commit otherwise

Future Plan
We plan to extend our work into these directions:

1. Expiration of coupling: We intend to explore if there are events that trigger a decoupling
or a decay of the MLC. This would also alleviate the problem of false-positive coupling
scenarios since over time services will not be coupled anymore.

2. Metric validity: This step is composed by two tasks:

a. Number of considered commits: We want to investigate if the used threshold of


five commits respects the representational theory of measurement [1] in
contemporary projects, i.e., if MLC corresponds to what we want to measure.

b. Code changes: We want to investigate how to include the actual code changes to
understand the evolution of coupling.

3. Identification of coupling patterns: Fig. 3 shows that we observed different progressions


of logical coupling over time in different project. We intend to study if we can observe
common patterns in such progression.

2. Literature Review
DevOps was introduced to overcome this issue of misalignment and is concerned with problems
organizations might encounter when releasing software in iterations. A key requirement in
surmounting this misalignment requires organizations to change their culture to involve
collaboration between different capabilities [4]. While DevOps and the practice of continuous
delivery can be used in tandem, DevOps also involves management and the required change in
organizational culture [5].
3. Systematic Literature Review
The present unit follows the rules of Barbara Ann Kitchenham (2004) to accomplish two
different systematic literature reviews (SLR) consuming a procedure. The SLR discovered a
particular area for identifying, analyzing and exploring information. Following is the research
procedure for the identification and checking of critical risks and risk mitigation strategies,
distinctly.

SLR is literature-based research that reflects presence and elimination principles for the
examination of information. It includes three comprehensive stages, the plan, conduct, and
report. The phases under these sets are assented in Table 1.1
SLR Phases Steps

The databases are selected from the sources.

The research questions are formulated by literaturate.


Plan
The inclusion and exclusion criteria is applied on.

The keywords are finalized to explore and the search strings are formulated.

Preliminary study is performed.

Conduct The data is extracted from the sources.

The data is analyzed to select.

Report The specifications are completed and the results are presented.

3.1 Research Planning


3.1.1 Research Questions
To get the primary objective of the research, the following research questions were conducted on
the study.
RQ1: How is DevOps defined in literature?
RQ2 Which DevOps practices have been implemented in an organization?
RQ3 What are the goals of adopting DevOps in an organization?
RQ4 What benefits have been obtained from adopting DevOps in
organization?
RQ5 What challenges have been confronted when adopting DevOps.
in organization

3.2 Data Source

The exploration for this study was a manual of the sources and simply conference and journal
articles are concentrated,
Consequently, we have chosen the most common in research and important databanks were
selected based on the preceding knowledge.
The procedure of classifying the appropriate papers in the field of identifying risk in rapid
application development in Pakistan software industry.
• Google scholar
• ACM
• IEEE Xplore
The above digital libraries are used to perform literature review in mitigate risk in RAP by AI.
The study papers are ranges from practical, theoretical and empirical based on survey, interview
and experiments.

Electronic databases ▪ IEEE Explorer


▪ Science Direct
▪ Springer Link
▪ ACM Digital Library
▪ Google scholar
▪ Other Databases
Searched items ▪ Conference papers, journal

Search applied on ▪ Full text


Language ▪ English

Publication period ▪ From 2018 to 2024

3.3 Source of Data


3.3.1 Inclusion Criteria:
The following points are measured when choosing and completing the studies.
• The language of the article is used to write up English only.
• Publication is a necessity for every article.
• Just a conference, journal and/or a workshop is considered.
• We selected articles related directly to our research questions.
• There should be rectify, culture influences strategies and technique proposed in the
article.

Inclusion Criteria
Papers in which the search terms were found in the title and abstract.
Papers published between 2001 to 2019 in data source
Papers where the full-text is available on the soruce.
Papers written in English.
Papers that are either a research paper, academic paper, or something of a similar nature.

3.3.2 Exclusion Criteria


Following points are considered when rejecting and scrutinizing the studies.
• The language of the article other than English is not used.
• Repetition elimination.
• Web pages, blogs, and Wikipedia articles are not part of present study.
• The unpublished articles are also omitted.
Exclusion Criteria
Duplicates of Papers already included.
Papers published before 2001.
Papers that are other than English Language.
Papers that address Pakistan Software Organization without RE practices.
Papers that use cultural differences to solve standard requirement engineering process

3.4 Search String


The search sequence is outlined by seeing the combination of keywords nominated form research
question which are updated in the searching of applicable studies of the literature. These
searching strings were added into three most common databases.

(risk OR effect OR “behavior” OR impact OR importance)

AND (mitigation OR remove OR identify)

AND (rapid OR Software development OR RDLC OR RAD)

AND (Software OR Software Industry)

AND (Pakistan OR Global))

Databases Total Title Abstract Complete Text category filter and n Final
used Papers Filtration Filtration Remove duplicate Selected
Articles
Google 1200 680 38 11 6
Scholar
ACM 300 60 20 8 4
IEEE Xplore 1000 200 320 6 4

4. Experimental Research Design


There are many types of research designs, and not all of them are experimental. Choosing the
most appropriate research approach depends on many factors, including the nature of the
investigation, the goals of the study, and access to subjects or materials.
Exploratory: To know whether a research question is exploratory, a researcher needs to find out
what has already been learned about that topic. If a little research has been done, then an
exploratory study might be appropriate to generate new information about the topic.
Descriptive: Descriptive studies typically answer questions about "How." A descriptive study
could be done to describe how people feel after a particular experience.
4.1 Key Components of Experimental Study Design:
4.1.1 Hypothesis:
1. To find the challenges or issues in terms of adopting DevOps practices in the industry
2. To overcome the challenges identified in processes in adopting DevOps culture.
Discussion: There should be cause and effect relationship between timeline and quality, security
and system design in rapid application development. As the development is fast to overcome
timeline, quality must be considered.
4.1.2 Independent variables:
Timeline and quality are independent variables. Timeline and quality are cause and effect
variables.
4.1.3 Dependent variables:
Efficiency and cost effectiveness are the effect of the change in timeline and quality in
independent variables as response variable.

References
T Offerman1, R Blinde1, C.J Stettina1 and J Visser1. (2023). A Study of Adoption and Effects of
DevOps Practices. IEEE.
A Bijwe,P Shankar. (2023). Challenges of Adopting DevOps Culture on the Internet of Things
Applications - A Solution Model. IEEE
R Grande, A Vizcaíno, F. García .(2023) . Is it worth adopting DevOps practices in Global
Software Engineering? Possible challenges and benefits. IEEE
L. Giamattei, A. Guerriero, R. Pietrantuono. (2023). Monitoring tools for DevOps and
microservices: A systematic grey literature review. IEEE
Nasreen Azad , (2022). Understanding DevOps critical success factors and organizational
practices, IEEE
M Arsecularatne, R Wickramarachchi , (2023). The Adoptability of Chaos Engineering with
Devops to Stimulate the Software Delivery Performance: A Systematic Literature Review, IEEE

You might also like