Proceedings of the 18th International ACM SIGSOFT Symposium on Component-Based Software Engineering 2015
DOI: 10.1145/2737166.2737177
|View full text |Cite
|
Sign up to set email alerts
|

Change-Driven Consistency for Component Code, Architectural Models, and Contracts

Abstract: During the development of component-based software systems, it is often impractical or even impossible to include all development information into the source code. Instead, specialized languages are used to describe components and systems on different levels of abstraction or from different viewpoints: Component-based architecture models and contracts, for example, can be used to describe the system on a high level of abstraction, and to formally specify component constraints. Because models, contracts, and co… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
8
0

Year Published

2015
2015
2023
2023

Publication Types

Select...
4
2
1

Relationship

3
4

Authors

Journals

citations
Cited by 17 publications
(8 citation statements)
references
References 15 publications
0
8
0
Order By: Relevance
“…The models of both case studies were created independently, but as there are no predefined change sequences, we have to define them to evaluate the consistency preservation transformations. Similarly, we have to define the mappings, invariants, and responses, from which these transformations will be generated, based on existing, manually implemented transformations [15]. Using the first case study, we will show whether it is possible to keep component models and their implementation consistent using our approach.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…The models of both case studies were created independently, but as there are no predefined change sequences, we have to define them to evaluate the consistency preservation transformations. Similarly, we have to define the mappings, invariants, and responses, from which these transformations will be generated, based on existing, manually implemented transformations [15]. Using the first case study, we will show whether it is possible to keep component models and their implementation consistent using our approach.…”
Section: Discussionmentioning
confidence: 99%
“…From a specification, incremental consistency preservation transformations, which propagate incoming changes, are generated using an intermediate language for mapping expressions. Our approach is part of the Vitruvius framework for view-centric engineering [16,15], in which all model changes are recorded and in which custom views that integrate information from multiple metamodels can be defined. Altogether, we try to reduce the accidental complexity of keeping models consistent by generating change-driven transformations from consistency specifications that are defined in a language that we have created specifically for this purpose.…”
Section: Introductionmentioning
confidence: 99%
“…Vitruvius [9,71,72] presents a framework that supports flexible views [15] that may involve multiple models conforming to different metamodels. The approach is aligned with the Orthographic Software Modelling (OSM) approach by Atkinson et al [13].…”
Section: Vitruviusmentioning
confidence: 99%
“…Specific languages have been developed that support the definition of such delta-based consistency preservation in the VITRUVIUS approach [17]. Consistency preservation in VITRUVIUS was first investigated on a case study of component-based architectures, Java code and code contracts [19].…”
Section: Design Objectivesmentioning
confidence: 99%