Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Continuous Software Engineering: Introducing an Industry Readiness Model
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0002-1987-2234
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0002-3646-235x
Ericsson AB, Sweden.
2023 (English)In: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 40, no 4, p. 77-87Article in journal (Refereed) Published
Abstract [en]

Software is becoming essential for most products, manufacturing processes, and back-office functions. The speed of delivering new features and refining the product is critical to remaining competitive. Software organizations may adopt continuous engineering practices to become more efficient. However, retrofitting an organization with a pipeline is challenging. Importantly, the most significant challenges and opportunities, are related to, but stem from outside the engineering realm and require rethinking customer relationships and business models. This paper presents a hierarchy of continuous engineering benefits and challenges. It is aimed to guide the adoption of continuous practices in an organization to determine the current and target level of adoption, given organizational context, ambitions, and domain constraints. IEEE

Place, publisher, year, edition, pages
IEEE Computer Society, 2023. Vol. 40, no 4, p. 77-87
Keywords [en]
Automation, Companies, Investment, Pipelines, Software, Software engineering, Testing, Public relations, Software testing, Back office, Continuous software engineerings, Customer relationships, Engineering practices, Manufacturing process, Product manufacturing, Readiness models, Relationship model, Software organization
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-24486DOI: 10.1109/MS.2023.3263190ISI: 001032645500012Scopus ID: 2-s2.0-85153369631OAI: oai:DiVA.org:bth-24486DiVA, id: diva2:1755149
Part of project
SERT- Software Engineering ReThought, Knowledge FoundationAvailable from: 2023-05-05 Created: 2023-05-05 Last updated: 2023-08-11Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full textScopus

Authority records

Klotins, EriksGorschek, Tony

Search in DiVA

By author/editor
Klotins, EriksGorschek, Tony
By organisation
Department of Software Engineering
In the same journal
IEEE Software
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 28 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf