2016
DOI: 10.1007/978-3-319-46397-1_42
|View full text |Cite
|
Sign up to set email alerts
|

Requirements Evolution and Evolution Requirements with Constrained Goal Models

Abstract: Abstract. We are interested in supporting software evolution caused by changing requirements and/or changes in the operational environment of a software system. For example, users of a system may want new functionality or performance enhancements to cope with growing user population (changing requirements). Alternatively, vendors of a system may want to minimize costs in implementing requirements changes (evolution requirements). We propose to use Constrained Goal Models (CGMs) to represent the requirements of… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
17
0

Year Published

2016
2016
2024
2024

Publication Types

Select...
4
2

Relationship

4
2

Authors

Journals

citations
Cited by 11 publications
(17 citation statements)
references
References 9 publications
0
17
0
Order By: Relevance
“…[1] has offered a formalization of the next adaptation problem that chooses a next adaptation for an adaptive software system that minimizes the degree of failure over existing requirements. And [30] has exploited CGMs to capture evolution requirements, such as "System evolution shall minimize implementation costs" and showed how to conduct scalable reasoning over models that include such requirements.…”
Section: Discussionmentioning
confidence: 99%
“…[1] has offered a formalization of the next adaptation problem that chooses a next adaptation for an adaptive software system that minimizes the degree of failure over existing requirements. And [30] has exploited CGMs to capture evolution requirements, such as "System evolution shall minimize implementation costs" and showed how to conduct scalable reasoning over models that include such requirements.…”
Section: Discussionmentioning
confidence: 99%
“…Close to our work, some methods use a goal-oriented approach to support requirement elicitation and organization. Language and methodology like KAOS [17], i* [7] and globally all the Goal-oriented Requirements Languages (GRL) tackle challenges like evolution of requirements but also internal practices with a goal-oriented approach [20] and also are focused on accreditation client requirements [19]. All these goal modeling languages focus on who and what, but they do not try to capture the why.…”
Section: Related Workmentioning
confidence: 99%
“…Here we consider a variant of the problem of computing a lexicographically-optimum realization of a constrained goal model [60,59]. In this comparison, the three PB/MAXSMT objectives appearing in the original set of formulas are normalized so that their respective range is equal to [0, 1] and combined in a single max-min goal rather than lexicographically optimized.…”
Section: Cgms With Max-min Goal + Pb Objectivesmentioning
confidence: 99%
“…Goal Models (GM) are used in Requirements Engineering to represent software requirements, objectives, and design qualities [77]. Constrained Goal Models (CGM) [59,60] are a novel, formal version of GM, representing AND/OR goal decomposition graphs which are enriched with constraints so that to handle preferences, numerical attributes and resources (e.g., scores, financial cost, workforce, etc. ).…”
Section: Constrained Goal Modelsmentioning
confidence: 99%
See 1 more Smart Citation