arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 2203.12409cs.SE
收藏

野外连续软件工程

Continuous Software Engineering in the Wild

Eriks Klotins, Tony Gorschek

摘要:

软件正在成为大多数产品和组织功能的关键组件。持续改进软件的能力决定了组织对市场机会的反应能力。持续的软件工程承诺比基于sprint或计划驱动的开发有许多优点。然而,在现有组织中实现连续的软件工程管道是具有挑战性的。在这份受邀的立场文件中,我们讨论了采用挑战,并主张采用更系统的方法来推动持续工程的采用。我们的讨论是基于正在进行的工作,与几个工业合作伙伴,以及在国家的实践和国家的最先进的经验报告。我们的结论是,采用持续的软件工程主要需要分析的组织,它的目标和限制。一个尺寸不适合所有目的,这意味着持续工程背后的许多原则与大多数组织相关,但实现的水平和好处可能仍然不同。软件持续流动的主要障碍来自次优的组织结构和缺乏一致性。一旦这些被删除,组织可以实现自动化,以进一步改善软件交付。

英文摘要:

Software is becoming a critical component of most products and organizational functions. The ability to continuously improve software determines how well the organization can respond to market opportunities. Continuous software engineering promises numerous advantages over sprint-based or plan-driven development. However, implementing a continuous software engineering pipeline in an existing organization is challenging. In this invited position paper, we discuss the adoption challenges and argue for a more systematic methodology to drive the adoption of continuous engineering. Our discussion is based on ongoing work with several industrial partners as well as experience reported in both state-of-practice and state-of-the-art. We conclude that the adoption of continuous software engineering primarily requires analysis of the organization, its goals, and constraints. One size does not fit all purposes, meaning that many of the principles behind continuous engineering are relevant for most organizations, but the level of realization and the benefits may still vary. The main hindrances to continuous flow of software arise from sub-optimal organizational structures and the lack of alignment. Once those are removed, the organization can implement automation to further improve the software delivery.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑