Without a specific functional context, non-functional requirements can only be approached as cross-cutting concerns and treated uniformly across all features of an application. This neglects, however, the heterogeneity of non-functional requirements that arises from stakeholder interests and the distinct functional scopes of software systems, which mutually influence how these non-functional requirements have to be satisfied. Earlier studies showed that the different types and objectives of non-functional requirements result in either vague or unbalanced specification of non-functional requirements. We propose a task analytic approach for eliciting and modeling user tasks to approach the stakeholders' pursued interests towards the software product. Stakeholder interests are structurally related to user tasks and each interest can be specified individually as a constraint of a specific user task. These constraints support DevOps teams with important guidance on how the interest of the stakeholder can be satisfied in the software lifecycle sufficiently. We propose a structured approach, intertwining task-oriented functional requirements with non-functional stakeholder interests to specify constraints on the level of user tasks. We also present results of a case study with domain experts, which reveals that our task modeling and interest-tailoring method increases the comprehensibility of non-functional requirements as well as their impact on the functional requirements, i.e., the users' tasks.
翻译:没有具体的功能环境,非职能性要求只能作为跨领域问题处理,在应用的所有特点中予以统一处理。但是,这种忽视忽视了来自利益攸关方利益和软件系统不同功能范围的不同功能性要求的不功能性要求,这些要求相互影响如何满足这些不功能性要求,早期的研究显示,不功能性要求的不同类型和目标导致对不功能性要求作出模糊或不平衡的具体规定。我们建议采用任务分析方法,以激发和模拟用户任务,将利益攸关方追求的利益与软件产品联系起来。利害关系方利益与用户任务有结构上的关系,每个利益都可以单独确定,作为具体用户任务的制约。这些制约因素支持DevOps小组,就利益攸关方在软件生命周期中如何充分满足这些不功能性要求提供重要指导。我们提出一种结构化的方法,将面向任务的职能性功能性要求与不起作用的利益攸关方利益联系起来,以具体说明对用户任务水平的限制。我们还向域专家介绍了一项案例研究的结果,其中显示,我们的任务性建模和利害关系性要求在结构上都与用户要求不相容。