<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Designing Software Architecture to Support Continuous Delivery and DevOps: A Systematic Literature Review</title>
  </titleInfo>
  <name type="personal">
    <namePart>Robin Bolscher</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
    <role>
      <roleTerm type="text">author.</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Maya Daneva</namePart>
    <role>
      <roleTerm type="text">author.</roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <genre authority="">Review articles.</genre>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">xx</placeTerm>
    </place>
    <dateIssued encoding="marc">2019</dateIssued>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <extent>1 online resource (1 article).</extent>
  </physicalDescription>
  <abstract>This paper presents a systematic literature review of software architecture approaches that support the implementation of Continuous Delivery (CD) and DevOps. Its goal is to provide an understanding of the state-of-the-art on the topic, which is informative for both researchers and practitioners. We found 17 characteristics of a software architecture that are beneficial for CD and DevOps adoption and identified ten potential software architecture obstacles in adopting CD and DevOps in the case of an existing software system. Moreover, our review indicated that micro-services are a dominant architectural style in this context. Our literature review has some implications: for researchers, it provides a map of the recent research efforts on software architecture in the CD and DevOps domain. For practitioners, it describes a set of software architecture principles that possibly can guide the process of creating or adapting software systems to fit in the CD and DevOps context.</abstract>
  <note type="statement of responsibility">Robin Bolscher; Maya Daneva.</note>
  <note>Publication type: Review article.</note>
  <note>Linked open-access copy: published version.</note>
  <note>Open access; no subscription required for the linked open-access version. Unrestricted online access star</note>
  <note xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://openalex.org/W2968843250">Creative Commons Attribution-NonCommercial-NoDerivatives (licence family recorded by the source; version not supplied in metadata). https://openalex.org/W2968843250</note>
  <note>In English.</note>
  <subject>
    <topic>software architecture</topic>
  </subject>
  <subject>
    <topic>continuous delivery</topic>
  </subject>
  <subject>
    <topic>DevOps</topic>
  </subject>
  <subject>
    <topic>microservices</topic>
  </subject>
  <subject>
    <topic>architectural style</topic>
  </subject>
  <subject>
    <topic>B. Sc. Software Engineering</topic>
  </subject>
  <subject>
    <topic>UMUN open access collection</topic>
  </subject>
  <subject>
    <topic>DevOps</topic>
  </subject>
  <relatedItem type="host">
    <titleInfo>
      <title>International Conference on Software Technologies (ICSOFT)</title>
    </titleInfo>
    <part>
      <text>(2019), pages/article 27-39</text>
    </part>
  </relatedItem>
  <identifier type="uri">https://doi.org/10.5220/0007837000270039</identifier>
  <location>
    <url displayLabel="Read open-access publication">https://doi.org/10.5220/0007837000270039</url>
  </location>
  <accessCondition type="restrictionOnAccess">Open access; no subscription required for the linked open-access version.</accessCondition>
  <accessCondition type="useAndReproduction">Creative Commons Attribution-NonCommercial-NoDerivatives (licence family recorded by the source; version not supplied in metadata).</accessCondition>
  <recordInfo>
    <recordContentSource authority="marcorg">local</recordContentSource>
    <recordCreationDate encoding="marc">261005</recordCreationDate>
    <recordChangeDate encoding="iso8601">20261005174820.0</recordChangeDate>
    <recordIdentifier source="local">UMUN-OA-20261005-SE-030</recordIdentifier>
    <languageOfCataloging>
      <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
    </languageOfCataloging>
  </recordInfo>
</mods>
