Agile methods have provided significant contributions to Software Engineering. This work presents a new process for Software Requirements Specification, integrating Agile Properties and regulated environments, such as aviation, medical, nuclear and automotive, among others. The Software in Regulated Environments (SRE) involves plan-driven methods with needed documentation to ensure safety, reliability, security, and discipline. This paper proposes a balance between agile and plan-driven methods. We define a new process, which explores and investigates the usage of agile methods in SRE. The scope of this paper is Requirements Engineering, which is considered as a set of activities involved in the management, elicitation, documentation, and maintenance of requirements. The Adile Requirements Specification (ARES) process contains four methods, 13 activities, and some required artifacts to ensure compliance with the following six relevant Software Standards for regulated environments: RTCA DO-178C, IEC 62304:2015, ECSS-E-ST-40C, IEC 61508-3, ISO/IEC/IEEE 12207, and IAEA SSG-39. The process evaluation was performed using two experiments: a Cockpit Display System (CDS) and a Healthcare Information System (HIS). These experiments were measured with appropriate metrics to ensure improvements in Software Requirements Specification and traceability among artifacts. The experimental results revealed that the ARES process works better than the original Scrum for Software in Regulated Environments. The ARES process can also be integrated with traditional software life cycles (Waterfall, V, and Incremental and Iterative), when applied in the Requirements Engineering phase.

中文翻译：

---

ARES：受监管环境的敏捷需求规范流程

敏捷方法为软件工程做出了重大贡献。这项工作提出了一个新的软件需求规范流程，将敏捷属性和受监管的环境（如航空、医疗、核能和汽车等）集成在一起。受监管环境中的软件 (SRE) 涉及计划驱动的方法和所需的文档，以确保安全性、可靠性、安全性和纪律性。本文提出了敏捷方法和计划驱动方法之间的平衡。我们定义了一个新流程，探索和调查敏捷方法在 SRE 中的使用。本文的范围是需求工程，它被认为是涉及管理、获取、文档和维护需求的一组活动。Adile 需求规范 (ARES) 流程包含四种方法，13 项活动和一些必需的工件，以确保符合以下六种受监管环境的相关软件标准：RTCA DO-178C、IEC 62304:2015、ECSS-E-ST-40C、IEC 61508-3、ISO/IEC/IEEE 12207和 IAEA SSG-39。过程评估使用两个实验进行：驾驶舱显示系统 (CDS) 和医疗保健信息系统 (HIS)。这些实验是用适当的度量来衡量的，以确保软件需求规范的改进和工件之间的可追溯性。实验结果表明，ARES 流程比原始 Scrum for Software 在受监管的环境中工作得更好。当应用在需求工程阶段时，ARES 过程还可以与传统的软件生命周期（瀑布、V 以及增量和迭代）集成。以及一些必需的工件，以确保符合以下六种受监管环境的相关软件标准：RTCA DO-178C、IEC 62304:2015、ECSS-E-ST-40C、IEC 61508-3、ISO/IEC/IEEE 12207 和 IAEA SSG-39。过程评估使用两个实验进行：驾驶舱显示系统 (CDS) 和医疗保健信息系统 (HIS)。这些实验是用适当的度量来衡量的，以确保软件需求规范的改进和工件之间的可追溯性。实验结果表明，ARES 流程比原始 Scrum for Software 在受监管的环境中工作得更好。当应用在需求工程阶段时，ARES 过程还可以与传统的软件生命周期（瀑布、V 以及增量和迭代）集成。以及一些必需的工件，以确保符合以下六种受监管环境的相关软件标准：RTCA DO-178C、IEC 62304:2015、ECSS-E-ST-40C、IEC 61508-3、ISO/IEC/IEEE 12207 和 IAEA SSG-39。过程评估使用两个实验进行：驾驶舱显示系统 (CDS) 和医疗保健信息系统 (HIS)。这些实验是用适当的度量来衡量的，以确保软件需求规范的改进和工件之间的可追溯性。实验结果表明，ARES 流程比原始 Scrum for Software 在受监管的环境中工作得更好。当应用在需求工程阶段时，ARES 过程还可以与传统的软件生命周期（瀑布、V 以及增量和迭代）集成。