论文标题
非常大的敏捷系统工程中建模需求的各个方面
Aspects of Modelling Requirements in Very-Large Agile Systems Engineering
论文作者
论文摘要
尽管总体上广泛使用了基于模型的工程，但在系统工程中使用模型进行工程（RE）并不常见。缺乏使用的原因之一是，正式模型与敏捷开发方法的趋势不太匹配。尽管存在研究在系统工程中采用需求建模和敏捷方法中挑战的工作，但缺乏研究在敏捷系统工程中使用需求建模的成功方法。为了解决这一差距，我们进行了一项案例研究，调查了瑞典电信公司爱立信AB的应用模型的应用。我们研究了一个使用要求模型来弥合敏捷开发和计划驱动发展方面的部门。我们发现模型用于了解需求相互关系，并跟踪产品的发展。为了应付随着时间的推移维护模型的努力，研究参与者建议依靠基于文本的符号，这些符号使模型更接近开发人员并允许将其集成到现有的软件开发工作流程中。这会导致工具权衡，例如，失去控制图布局的可能性。
Using models for requirements engineering (RE) is uncommon in systems engineering, despite the widespread use of model-based engineering in general. One reason for this lack of use is that formal models do not match well the trend to move towards agile developing methods. While there exists work that investigates challenges in the adoption of requirements modeling and agile methods in systems engineering, there is a lack of work studying successful approaches of using requirements modelling in agile systems engineering. To address this gap, we conducted a case study investigating the application of requirements models at Ericsson AB, a Swedish telecommunications company. We studied a department using requirements models to bridge agile development and plan-driven development aspects. We find that models are used to understand how requirements relate to each other, and to keep track with the product's evolution. To cope with the effort to maintain models over time, study participants suggest to rely on text-based notations that bring the models closer to developers and allow integration into existing software development workflows. This results in tool trade-offs, e.g., losing the possibility to control diagram layout.
