Journal ArticleDOI
Continuous software engineering: A roadmap and agenda
Brian Fitzgerald,Klaas-Jan Stol +1 more
Reads0
Chats0
TLDR
It is argued a similar continuity is required between business strategy and development, BizDev being the term the authors coin for this, and a number of continuous activities are identified which together are labelled as ‘Continuous * ’ (i.e. Continuous Star) which are presented as part of an overall roadmap for Continuous Software engineering.About:
This article is published in Journal of Systems and Software.The article was published on 2017-01-01. It has received 526 citations till now. The article focuses on the topics: Release management & DevOps.read more
Citations
More filters
Journal ArticleDOI
Continuous engineering for Industry 4.0 architectures and systems
Pablo Oliveira Antonino,Rafael Capilla,Rick Kazman,Thomas Kuhn,Frank Schnicke,T. Treichel,Adam Bachorek,Zai Muller-Zhang,Victor Salamanca +8 more
TL;DR: This research analyzes traditional architecture evaluation methods and Industry 4.0 scenarios, and proposes an approach based on Digital Twins and simulations to continuously evaluate runtime quality aspects of the architecture and systems of industrial production plants.
Book ChapterDOI
Continuous Requirements Engineering in the Context of Socio-cyber-Physical Systems.
TL;DR: In this paper, the authors address complexity, emergence, and fluent borders of systems, the challenges that may occur in continuous requirements engineering in the context of socio-cyber-physical systems.
Market Driven Requirements Engineering Strategy for Startups
Olle Renard,Oscar Bergström +1 more
TL;DR: In this article, the authors investigate the concept of requirements engineering in startups and develop a strategy which they use as a base for finding challenges and practices through interviews at a startup called Trovisio.
Proceedings ArticleDOI
Tell me: Am I going to Heaven? A Diagnosis Instrument of Continuous Software Engineering Practices Adoption
TL;DR: In this article, a diagnosis instrument, called Zeppelin, is presented to help organizations get an overall view of the CSE practices they perform, identify where they are in the continuous software engineering evolutionary path and which areas should be improved.
Book ChapterDOI
Tacit Knowledge in Software Evolution
TL;DR: This chapter describes two perspectives on the identification and externalisation of tacit knowledge, that is expertise that is difficult to verbalise, within long-living and continuously evolving systems.
References
More filters
Journal ArticleDOI
User acceptance of information technology: toward a unified view
TL;DR: The Unified Theory of Acceptance and Use of Technology (UTAUT) as mentioned in this paper is a unified model that integrates elements across the eight models, and empirically validate the unified model.
Journal ArticleDOI
User Acceptance of Computer Technology: A Comparison of Two Theoretical Models
TL;DR: In this article, the authors address the ability to predict peoples' computer acceptance from a measure of their intentions, and explain their intentions in terms of their attitudes, subjective norms, perceived usefulness, perceived ease of use, and related variables.
Book
Open Innovation: The New Imperative for Creating and Profiting from Technology
TL;DR: Open Innovation: The New Imperative for Creating and Profiting From Technology as discussed by the authors is a book by Henry Chesbrough, which discusses the importance of open innovation for creating and profiting from technology.
Journal ArticleDOI
Trust and TAM in online shopping: an integrated model
TL;DR: Research on experienced repeat online shoppers shows that consumer trust is as important to online commerce as the widely accepted TAM use-antecedents, perceived usefulness and perceived ease of use, and provides evidence that online trust is built through a belief that the vendor has nothing to gain by cheating.
Journal ArticleDOI
Understanding information systems continuance: an expectation-confirmation model
TL;DR: The results suggest that users' continuance intention is determined by their satisfaction with IS use and perceived usefulness of continued IS use, and that post-acceptance perceived usefulness is influenced by users' confirmation level.
Related Papers (5)
Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation
Jez Humble,David Farley +1 more
Guidelines for conducting and reporting case study research in software engineering
Per Runeson,Martin Höst +1 more