Aug 2026· IEEE International Requirements Engineering Conference· pp. 580-584· 0 citations· 27 references
Abstract
With the increasing use of LLMs, requirements engineering has changed significantly. Tasks that were previously conducted by or with stakeholders are now performed by or with LLMs. Consequently, requirements engineers, developers, and the like are increasingly relinquishing their autonomy. To counteract this trend, stakeholders' values should be given greater consideration. Human values have always been a focus in certain areas, such as healthcare and entertainment, but they are relevant to all areas. They shed light on people's basic needs and can reveal the core objectives underlying requirements. In addition to value-sensitive design and IEEE standards, other methods exist for integrating values into the software engineering process. However, few methods incorporate human values throughout the process, from elicitation to documentation. This work aims to implement a process that includes the necessary methods for eliciting, prioritizing, and translating human values into requirements in the context of software development. To achieve this goal, a series of empirical studies will be conducted through surveys, interviews, and workshops, in which the process or individual methods are applied. Similarly, the impact of integrating human values on software quality will be evaluated. The implementation and examination of such a process could help establish a framework to place greater emphasis on human values in software development without significant additional effort.
LLMs are increasingly used for RE activities, including stakeholder tasks (e.g., requirements identification, negotiation, or prioritization). To avoid shifting the focus to LLMs and their requirements, human values should be given greater consideration. Project-specific values provide rationales for requirements, whic...
Elisa Schmid, Marc Herrmann, Michael Mircea et al.· 2026 IEEE 34th International...· 0 citations
Well known requirements engineering methodologies are presented and the degree of the user involvement in the process of requirements negotiation is discussed and the system called TeamRooms, provides a persistent work space suitable for synchronous and asynchronous collaboration.
User Stories are key artifacts in Requirement and Software Engineering. Despite their wide adoption, their writing in industrial contexts tends to diverge from the principles initially stated in Agile methodologies. In this context, sets of metrics such as INVEST or QUS emerged to qualify these items. In this paper, we...
M. Ortega, Hassan Imhah, N. Mellouli et al.· Proceedings of the ACM on So...· 0 citations