Application Deployment and Management in the Cloud

Miglierina, Marco

doi:10.1109/synasc.2014.63

Cited by 10 publications

(9 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The larger number of challenges, eg, C01, C02, C03, C04, C05, C06, C08, C09, C13, C14, C17, C18, C19, C22, C24, C25, C27, C28, C29, C30, C31, C32, C33, C34, C35, C36, C38, and 41 are about DevOps adoption. ()…”

Section: Resultsmentioning

confidence: 99%

“…In particular, lack of tools for automation, as one of the central DevOps principles (Pr2), has been mentioned as a barrier to implement DevOps. Miglierina specifies that while automation in deployment, maintenance, and monitoring is the main requirement of DevOps, there is a series of downsides (eg, lack of infrastructure to bring the developers and operators closer) that hinders full automation (C34, C35, and C36).…”

Section: Resultsmentioning

confidence: 99%

“…Lack of consistent definition (C18), KPIs (C08), standards (C09), maturity model for DevOps (C19), and lack of training and skill to implement DevOps (C31) have also stressed a shortage of infrastructure to adopt DevOps.…”

Section: Resultsmentioning

confidence: 99%

“…Also, it is claimed that adopting DevOps reduces the time to market, as it helps to achieve improved deployment frequency. () (CB04) Scalability. Virmani claims that the use of IaaC (infrastructure as a code) in DevOps ensures that the entire automation is scalable. (CB05) Portability.…”

Section: Resultsmentioning

confidence: 99%

“…DevOps speeds up the processes from development to operation. () Bruneo et al say DevOps can promote collaboration between developers and operational teams that leads to shortening the loop between software development, deployment, and operation. (CB14) Flexible software development. DevOps enables development and operations teams to be more flexible by providing close collaboration in implementing customer requirements.…”

Section: Resultsmentioning

confidence: 99%

See 4 more Smart Citations

Towards a benefits dependency network for DevOps based on a systematic literature review

Jabbari

Ali

Petersen

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

DevOps as a new way of thinking for software development and operations has received much attention in the industry, while it has not been thoroughly investigated in academia yet. The objective of this study is to characterize DevOps by exploring its central components in terms of principles, practices and their relations to the principles, challenges of DevOps adoption, and benefits reported in the peer-reviewed literature. As a key objective, we also aim to realize the relations between DevOps practices and benefits in a systematic manner. A systematic literature review was conducted. Also, we used the concept of benefits dependency network to synthesize the findings, in particular, to specify dependencies between DevOps practices and link the practices to benefits. We found that in many cases, DevOps characteristics, ie, principles, practices, benefits, and challenges, were not sufficiently defined in detail in the peer-reviewed literature.In addition, only a few empirical studies are available, which can be attributed to the nascency of DevOps research. Also, an initial version of the DevOps benefits dependency network has been derived. The definition of DevOps principles and practices should be emphasized given the novelty of the concept. Further empirical studies are needed to improve the benefits dependency network presented in this study. KEYWORDSbenefits and values, challenges, development and operations, DevOps, principles and practices, systematic literature review

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Resultsmentioning

confidence: 99%