2013
DOI: 10.1007/978-3-642-36249-1_1
|View full text |Cite
|
Sign up to set email alerts
|

Model Checking Adaptive Software with Featured Transition Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
34
0

Year Published

2013
2013
2017
2017

Publication Types

Select...
5
1

Relationship

1
5

Authors

Journals

citations
Cited by 26 publications
(34 citation statements)
references
References 42 publications
0
34
0
Order By: Relevance
“…(ii) It allows us to relate approaches presented independently and in different areas but sharing, essentially, the same category of control data. This is, e.g., the case of the approaches based on modes of operation proposed by the Software Engineering [11] adaptation coordination strategies adaptation strategy 4.1 [48] adaptation rules adaptation strategy 5.3 [15] architecture architecture 3.1 [46] architecture architecture 3.2 [60] architecture architecture 3.2 [66] module stack architecture 3.2 [22] current workflow architecture 3.2 [7] connectors architecture 3.2 [11] architecture architecture 4.1 [76] effector channel architecture 4.3 [48] set of activities architecture 5.3 [61] entire programs entire program 4.1 [55] rewrite rules entire program 4.2 [35] processes entire program 4.3 [30] processes entire program 4.3 [28] features operation mode 4.1 [53] regions operation mode 4.1 [83] operation mode operation mode 4.1 [1] active configuration operation mode 4.1 [72] active configuration operation mode 4.1 [19] control proposition operation mode 4.1 [82] steady state programs operation mode 4.1 [42] state space zones operation mode 4.1 [33] graph rewrite rules operation mode 4.2 [80] base level Petri net operation mode 4.3 [51] adaptor processes operation mode 4.3 [16] adaptable (local) processes operation mode 4.3 [69] context stack operation mode 5.1 [36] advices operation mode 5.2 [44] policies operation mode 5.3 community with paradigm-oriented approaches and by the Theoretical Computer Science community with automata and process-algebraic approaches. (iii) It allows us to compare approaches apparently similar (and falling in the same section) but based on different categories of control data.…”
Section: When Is a Software Component Adaptive?mentioning
confidence: 99%
See 1 more Smart Citation
“…(ii) It allows us to relate approaches presented independently and in different areas but sharing, essentially, the same category of control data. This is, e.g., the case of the approaches based on modes of operation proposed by the Software Engineering [11] adaptation coordination strategies adaptation strategy 4.1 [48] adaptation rules adaptation strategy 5.3 [15] architecture architecture 3.1 [46] architecture architecture 3.2 [60] architecture architecture 3.2 [66] module stack architecture 3.2 [22] current workflow architecture 3.2 [7] connectors architecture 3.2 [11] architecture architecture 4.1 [76] effector channel architecture 4.3 [48] set of activities architecture 5.3 [61] entire programs entire program 4.1 [55] rewrite rules entire program 4.2 [35] processes entire program 4.3 [30] processes entire program 4.3 [28] features operation mode 4.1 [53] regions operation mode 4.1 [83] operation mode operation mode 4.1 [1] active configuration operation mode 4.1 [72] active configuration operation mode 4.1 [19] control proposition operation mode 4.1 [82] steady state programs operation mode 4.1 [42] state space zones operation mode 4.1 [33] graph rewrite rules operation mode 4.2 [80] base level Petri net operation mode 4.3 [51] adaptor processes operation mode 4.3 [16] adaptable (local) processes operation mode 4.3 [69] context stack operation mode 5.1 [36] advices operation mode 5.2 [44] policies operation mode 5.3 community with paradigm-oriented approaches and by the Theoretical Computer Science community with automata and process-algebraic approaches. (iii) It allows us to compare approaches apparently similar (and falling in the same section) but based on different categories of control data.…”
Section: When Is a Software Component Adaptive?mentioning
confidence: 99%
“…A first example of this tradition are the Adaptive Featured Transition Systems (A-FTS) of [28], which were introduced for the purpose of model checking adaptive software (with a focus on software product lines). A-FTSs are a sort of transition systems where states are composed by the local state of the system, its configuration (set of active features) and the configuration of the environment.…”
Section: Automata-based Approaches To Adaptationmentioning
confidence: 99%
“…Adaptive Featured Transition Systems (A-FTS) have been introduced in [6] for the purpose of model checking adaptive software (with a focus on software product lines). A-FTS are a sort of transition systems where states are composed by the local state of the system, its configuration (set of active features) and the configuration of the environment.…”
Section: Related Workmentioning
confidence: 99%
“…Properties are expressed in AdaCTL, a variant of the computation-tree temporal logic CTL. Contrary to aias which are equipped with suitable composition operations, A-FTS are seen in [6] as monolithic systems.…”
Section: Related Workmentioning
confidence: 99%
“…An alternative is to organize the variability between these programs into features, a concept borrowed from software product line engineering (SPLE) [4]. In the latter discipline, a feature is an added functionality that meet a requirement of customers.…”
Section: Introductionmentioning
confidence: 99%