Formal reasoning for analyzing goal models that evolve over time

Grubb, Alicia M.; Chećhik, Marsha

doi:10.1007/s00766-021-00350-8

Cited by 12 publications

(3 citation statements)

References 36 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Formal reasoning for analyzing goal models that evolve over time [30]. The study empirically showed that requirements are not elicited in the strict sense but co-created through interviews, with analysts playing a crucial role in the process.…”

Section: Aims Main Contributions Main Limitationsmentioning

confidence: 99%

Understanding the impact of requirements evolution and reaction on evolution of software: a survey and comparison

Ahmed Mahdi Salih,

Mazni Omar,

Mohammed Alyasiri

et al. 2023

J. Appl. Artif. Intell.

View full text Add to dashboard Cite

In software systems, the continuous changing of requirements, known as requirements evolution, is considered one of the significant issues. Requirements' evolution denotes the postـdeployment changes in the requirements. This article reviews the most related requirements evolution approaches. Different approaches have been presented in modelling requirements evolution, managing requirements evolution, and relevant analysis techniques, like inconsistency detection and change impact analysis. The relevant approaches of requirements evolution can be generally classified into the impact of evolution and reaction on evolution. The article also has given a comparison among those approaches. The approaches that have been surveyed in this article exhibited many limitations. These limitations need to be addressed and coped with for the approaches to be more effective in managing the evolution of software requirements. One of the solutions to these limitations is to develop an approach that addresses the reasoning behind software requirements evolution.

show abstract

Section: Aims Main Contributions Main Limitationsmentioning

confidence: 99%

Understanding the impact of requirements evolution and reaction on evolution of software: a survey and comparison

Ahmed Mahdi Salih,

Mazni Omar,

Mohammed Alyasiri

et al. 2023

J. Appl. Artif. Intell.

View full text Add to dashboard Cite

show abstract

“…Thus, the analysts keep working using the collected knowledge and their expertise trying to get closer to the three Cs at every step of the process. Grubb and Chechik [30,32] focus on the early stage of requirements evolution, but they look at the modeling phase. In particular, they propose to use goal model analysis to help stakeholders to answer what if questions to support the evolution of a system considering different scenarios, as well as the customer in understanding trade-offs among different decisions.…”

Section: Early Requirements Evolutionmentioning

confidence: 99%

How do requirements evolve during elicitation? An empirical study combining interviews and app store analysis

2022

View full text Add to dashboard Cite

Requirements are elicited from the customer and other stakeholders through an iterative process of interviews, prototyping, and other interactive sessions. Then, requirements can be further extended, based on the analysis of the features of competing products available on the market. Understanding how this process takes place can help to identify the contribution of the different elicitation phases, thereby allowing requirements analysts to better distribute their resources. In this work, we empirically study in which way requirements get transformed from initial ideas into documented needs, and then evolve based on the inspiration coming from similar products. To this end, we select 30 subjects that act as requirements analysts, and we perform interview-based elicitation sessions with a fictional customer. After the sessions, the analysts produce a first set of requirements for the system. Then, they are required to search similar products in the app stores and extend the requirements, inspired by the identified apps. The requirements documented at each step are evaluated, to assess to which extent and in which way the initial idea evolved throughout the process. Our results show that only between 30% and 38% of the requirements produced after the interviews include content that can be fully traced to initial customer’s ideas. The rest of the content is dedicated to new requirements, and up to 21% of it belongs to completely novel topics. Furthermore, up to 42% of the requirements inspired by the app stores cover additional features compared to the ones identified after the interviews. The results empirically show that requirements are not elicited in strict sense, but actually co-created through interviews, with analysts playing a crucial role in the process. In addition, we show evidence that app store-inspired elicitation can be particularly beneficial to complete the requirements.

show abstract

“…These SRs are related to evolutionary and awareness requirements [59] which need to be implemented before use in design of the software architecture, even though their benefits are only realized in longer-term use. Modelling user acceptance requirements using game paradigms [60] could be used to explore evolution of the impact of SRs over time More formal modeling of SRs and their implications may be developed using the evolutionary intentions framework [61] to explore change in goal dependency models over time. However, the road to formalization of SRs may need to follow a more probabilistic rather than deterministic route since many SR are assumptions which may influence goals (or FRs) to a greater or lesser degree.…”

Section: Soft Requirements and Technology Acceptancementioning

confidence: 99%

The Implications of ‘Soft’ Requirements

Sutcliffe

Sawyer

Bencomo

2022

2022 IEEE 30th International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

A new focus for RE is investigated as 'soft' requirements which extends non-functional requirements / soft goals with a collection of people-oriented phenomena: values, motivations, emotions, and other socio-political issues that may influence the requirements specification. The convergence of RE with user experience (HCI) and technology acceptance from the information systems literature is reviewed from a temporal perspective: pre-use, through initial to longer-term use. A taxonomy of soft requirements is proposed that extends non-functional requirements and soft-goal concepts to direct attention towards user characteristics and beliefs that may have implications for functional as well as system support requirements, such as training, help, explanation and trust in software. A timeline model of soft and hard (functional) requirements is presented with a focus on customization, adaptation and other soft requirements to, improve product acceptance and persuade users to take appropriate action. The paper concludes with a research agenda for soft requirements to improve the probability of system acceptance and the effectiveness of applications that aim to influence people's decisions and behaviour in internet apps and other discretionary-use applications.

show abstract

Formal reasoning for analyzing goal models that evolve over time

Cited by 12 publications

References 36 publications

Understanding the impact of requirements evolution and reaction on evolution of software: a survey and comparison

Understanding the impact of requirements evolution and reaction on evolution of software: a survey and comparison

How do requirements evolve during elicitation? An empirical study combining interviews and app store analysis

The Implications of ‘Soft’ Requirements

Contact Info

Product

Resources

About