
Requirements consist of (a) domain assumptions, (b) hard goals, (c) quality constraints, (d) possibly prioritized preferences. The very core of Requirements Engineering consists of the following problem: given a set of (a)-(d), generate specifications that fulfill hard goals and quality constraints, assuming that domain assumptions hold, and satisfy maximal sets of preferences. We are working towards tools that solve this problem for expressive modeling languages in terms of which one can represent domain assumptions, goals, etc. Such tools can be used as basis for exploring requirements by varying preferences and priorities, or weakening/strengthening goals.
prioritiyed preferences, Domain assumptions, qualitz constraints, hard goals, 004
prioritiyed preferences, Domain assumptions, qualitz constraints, hard goals, 004
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
