2009 ICSE Workshop on Modeling in Software Engineering 2009
DOI: 10.1109/mise.2009.5069890
|View full text |Cite
|
Sign up to set email alerts
|

Relationship-based change propagation: A case study

Abstract: Software development is an evolutionary process. Re

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
11
0

Year Published

2009
2009
2017
2017

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 18 publications
(12 citation statements)
references
References 10 publications
1
11
0
Order By: Relevance
“…We made this decision with the hope of achieving higher levels of automation. This rationale is consistent with the findings of Chechik et al [26], who reason that propagating changes between models at different levels of abstraction is impossible.…”
Section: Related Worksupporting
confidence: 91%
See 1 more Smart Citation
“…We made this decision with the hope of achieving higher levels of automation. This rationale is consistent with the findings of Chechik et al [26], who reason that propagating changes between models at different levels of abstraction is impossible.…”
Section: Related Worksupporting
confidence: 91%
“…Chechik et al [26] have taken a model-based approach and provided an algorithm for propagating changes between requirements and design models. Their approach propagates changes between requirements-level activity diagrams, and design-level sequence diagrams.…”
Section: Related Workmentioning
confidence: 99%
“…Controlled Update Approaches with support for multiple models may only allow the user to update the state in a controlled manner, typically only allowing updates over a single model [7,27,33] so that the propagation to the others is more easily managed. These is common in bidirectional transformation techniques, where the update is propagated from one of the models to the other: allowing concurrent updates could lead to conflicts that could not be resolved.…”
Section: Multi-modelmentioning
confidence: 99%
“…In particular, we would like to investigate how one can combine a collection of models that are interconnected via not just one but multiple relationship types, i.e., the situation where some models are overlapping, some models are interacting, and some models are cross-cutting others. Further, we plan to extend our conceptual framework to encompass other model management operations such as consistency checking and change propagation [3,4].…”
Section: Discussionmentioning
confidence: 99%