# Specifying and Reasoning about Contextual Preferences in the   Goal-oriented Requirements Modelling

**Authors:** Khavee Agustus Botangen, Jian Yu, Sira Yongchareon, LiangHuai Yang,, Quan Bai

arXiv: 1905.06437 · 2019-05-17

## TL;DR

This paper introduces a method to specify and analyze how stakeholder preferences change with context in goal-oriented requirements modeling, using quantitative preferences and automated reasoning to evaluate solutions.

## Contribution

It presents a novel approach combining contextual preference specification with Answer Set Programming for automated requirements variability analysis.

## Key findings

- Supports decision-making in requirements engineering
- Automates evaluation of context-dependent preferences
- Enhances goal model flexibility with quantitative preferences

## Abstract

Goal-oriented requirements variability modelling has established the understanding for adaptability in the early stage of software development-the Requirements Engineering phase. Goal-oriented requirements variability modelling considers both the intentions, which are captured as goals in goal models, and the preferences of different stakeholders as the main sources of system behaviour variability. Most often, however, intentions and preferences vary according to contexts. In this paper, we propose an approach for a contextual preference-based requirements variability analysis in the goal-oriented Requirements Engineering. We introduce a quantitative contextual preference specification to express the varying preferences imposed over requirements that are represented in the goal model. Such contextual preferences are used as criteria to evaluate alternative solutions that satisfy the requirements variability problem. We utilise a state-of-the-art reasoning implementation from the Answer Set Programming domain to automate the derivation and evaluation of solutions that fulfill the goals and satisfy the contextual preferences. Our approach will support systems analysts in their decisions upon alternative design solutions that define subsequent system implementations.

---
Source: https://tomesphere.com/paper/1905.06437