Citation Context

...ifferent models. This is a common technique in software maintenance and product line engineering [8]. A different approach to dealing with variabilities is to originally treat them as inconsistencies =-=[7, 31, 27]-=-. This is more suitable for early stages of development where variabilities may be due to conceptual disagreements between stakeholders. 8 Conclusions and Future Work We presented an approach to match...

Citation Context

...Checklists [154] Consistency checking [55, 70, 107] Interaction analysis [23, 67, 125] Obstacle analysis [96, 152] Causal order analysis [11] Simulation [142] Invariant generation [79] Model checking =-=[25, 52, 137]-=- Model satisfiability [76] Prioritization [105] Variability Analysis [63, 93] Requirements selection [122, 139] Aligning Req. with COTS [91, 126] Effort estimation [33] Impact analysis [88] Traceabili...

Citation Context

...ly on merging models that describe the observable behaviour of a system. On the other hand, merging operational specifications in which system states are explicitly described is frequently done (e.g. =-=[24, 19, 7, 10]-=-). In [24], states are modelled as valuations of state propositions, and states with compatible valuations can be merged. In [7], states can be merged only if they have the same label. [19] proposes a...

Citation Context

... provide a conceptual framework to discuss viewpoints with regard to requirements coverage [8]. Proposed frameworks facilitate elicitation [27], integrate viewpoints [23] and identify inconsistencies =-=[10]-=-. Herein, different stakeholders viewpoints are embedded in rights and obligations that can be balanced to expose implied rights and obligations for other stakeholders (see Section 4.5). Giorgini et a...

Citation Context

...independently developed databases [2, 18, 11], static and dynamic UML models [26, 4], web services [10], program variants [7, 16], requirements models [21, 22], and many varieties of reactive systems =-=[9, 25, 3, 6]-=-. The modeling formalisms and the underlying assumptions in these approaches differ significantly. For example, most of these approaches require that only consistent models be merged, implying that in...

Citation Context

...eparate problem, because of the desire to maintain views as loosely-coupled distributed objects [2]. The use of multi-valued logics for merging incomplete and inconsistent views was first proposed in =-=[38]-=- and was later generalized in [17]. The latter work, which serves as a precursor to this paper, suggested category theory as a unified means for formalizing incompleteness and inconsistency and charac...

Citation Context

...k, which is consistency checking of arbitrary and unknown configurations of models and mappings. The idea of consistency checking via merge was first explored in prior work by Easterbrook and Chechik =-=[6]-=-. The work uses temporal logic model checking to reason about behavioural properties of state machine models when they are merged. This earlier work is not applicable to structural models, because tem...

Citation Context

...ther relevant work. A very significant problem is reasoning about inconsistencies that are the result of conflicts among multiple stakeholders – often referred to as viewpoints. For example, [11] and =-=[12]-=- define techniques for reasoning formally over multiple models despite the presence of logical inconsistencies. [13] defines a technique for merging conceptual models and detecting inconsistencies ove...