Socio-technical resilience in software development (STRIDE)

这个项目（STRIDE）处理的问题是如何使软件开发对技术、人员、方法、需求、期望、法规等的不断变化更有弹性。这个项目的具体问题是描述如何最好地利用自动化来提高社会技术弹性。基于跨学科研究的解决方案将是：为组织提供评估其弹性的工具；以及案例研究、最佳实践、指导和具体示例（来自自动化故障定位），以了解人类和工具如何最好地协同工作。此外，我们将倡导软件工程的积极形象。因此，STRIDE将调查支持软件开发的社会技术系统中的弹性和自动化，该系统包括人员（工程师、用户、管理人员）、技术基础设施（工具、开发环境）、过程（精益、需求引出）和工件（代码、wiki、编码标准）。社会技术系统的故障可能会造成重大破坏，而弹性工程旨在通过强调有效的方法来避免它们，从而保持弹性。从这个角度来看，弹性被定义为稳定与变化之间的生产张力，始终以生产“安全”的系统为目标。这种社会技术系统的观点与现代软件工程相关，其中变化已经成为地方性的：随着需求的变化、先进的技术、复杂的基础设施和新的安全威胁。除了不断变化的环境之外，软件生产越来越自动化，这需要不断地重新平衡这种紧张关系。但是弹性和自动化之间的关系是什么？虽然自动化带来的软件开发的改进对于保持软件的安全性至关重要，但自动化并不是灵丹妙药。据说，“让一个系统更安全，需要将人类的能力与他们使用的技术结合起来，这样他们就能保持控制”。这对软件开发意味着什么？作为软件开发过程的一部分，是否有一些基本的人类需要保留？如果是这样的话，在不断增加自动化的背景下，如何在人类控制和自动化之间保持富有成效和弹性的平衡？如何使用自动化来提高社会技术弹性，不同水平的自动化对弹性的影响是什么？STRIDE旨在解决这些问题和相关问题。该项目将确定并实施表明软件开发的社会技术弹性（STR）的因素，借鉴社会心理学和弹性工程，并将研究扎根于自动化故障定位的具体开发任务中。我们将与两个开发人员社区的代表进行接触：商业软件工程师和代表两种不同开发环境的专业最终用户开发人员。这项工作将对改进STR以及软件开发生命周期中自动化的速度和性质有特殊的影响。

This project (STRIDE) addresses the issue of how to make software development more resilient to constant changes of technology, staff, methods, requirements, expectations, regulations and more. The specific problem for this project is to characterise how automation can best be used to improve socio-technical resilience. The solution, based on interdisciplinary research, will be to provide: instruments for organisations to assess their resilience; and case studies, best practices, guidance and a concrete example (from automated fault localisation) to understand how humans and tools can best work together. In addition, we will advocate for a positive image for software engineering.So, STRIDE will investigate resilience and automation in the socio-technical system that supports software development, a system that includes people (engineers, users, managers), technical infrastructure (tools, development environments), processes (lean, requirements elicitation) and artefacts (code, wiki, coding standards). Breakdowns in socio-technical systems can cause significant disruption and Resilience Engineering aims to avoid them by emphasising what works, so that resilience can be preserved. From this perspective, resilience is defined as the productive tension between stability and change, always with the aim of producing systems that are "safe". This view of socio-technical systems is pertinent to modern software engineering where change has become endemic: with changing requirements, advanced technologies, complex infrastructure and new security threats. In addition to the constantly changing environment, software production is increasingly being automated, which requires repeated re-balance of this tension. But what is the relationship between resilience and automation?While improvements to software development brought by automation are vital to keeping software safe and secure, automation is not a silver bullet. It is said that "Making a system safer involves coupling the capabilities of humans with the technology they work with so that they can stay in control". What does that mean for software development? Is there something fundamentally human that needs to be retained as part of the software development process? And if so, how can a productive and resilient balance between human control and automation be maintained in the context of constantly increasing automation? How can automation be used to increase socio-technical resilience and what will be the impact on resilience of different levels of automation?STRIDE aims to address these and related questions. The project will determine and operationalise factors that indicate socio-technical resilience (STR) of software development, drawing on social psychology and resilience engineering, and grounding the research in the concrete development task of automated fault localisation. We will engage with representatives of two developer communities: commercial software engineers and professional end user developers who represent two different development environments. This work will have particular implications for improving STR and the pace and nature of automation in the software development lifecycle.