Models in Conflict – Towards a Semantically Enhanced Version Control System for Models

Altmanninger, Kerstin

doi:10.1007/978-3-540-69073-3_31

Cited by 23 publications

(23 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Initially, the model-oriented solutions appeared in the studies, where only one of the main configuration management tasks was solved, for example, configuration item identification [10], [2], [13], [6].…”

Section: Related Researchmentioning

confidence: 99%

“…While researching version of controlled solutions, one may encounter model creation [2], [5]. Study [2] describes an algorithm, which consists of meta-model controlled items.…”

Section: Related Researchmentioning

confidence: 99%

“…Study [2] describes an algorithm, which consists of meta-model controlled items. The meta-model describes the syntax of the model, which could be exposed to version control.…”

Section: Related Researchmentioning

confidence: 99%

See 2 more Smart Citations

Towards the Model-driven Software Configuration Management Process/ Modeļu vadāmais programmatūras konfigurācijas pārvaldības process/ Процесс управления конфигурациями программного обеспечения, основанный на моделях

Bartusevičs

Novickis

2014

Information Technology and Management Science

View full text Add to dashboard Cite

-Software configuration management is one of the most important disciplines within the software development project, which helps control the software evolution process and allows including into the end product only tested and validated changes. To achieve this, software management completes certain tasks. Concrete tools are used for technical implementation of tasks, such as version control systems, servers of continuous integration, compilers, etc. There are situations when some tools or scripts are implemented to support small particular parts of complex software configuration management process without a general picture of total process. Maintenance of such solutions is complex and more expensive than it could be. The study describes a model-driven configuration management approach, which foresees the development of an abstract environment model for the configuration management process that later is transformed to lower abstraction level models and tools are indicated to support the technical process. This approach allows implementing all tools and solutions according to the planned configuration management process and developing reusable solutions.

show abstract

Section: Related Researchmentioning

confidence: 99%

“…While researching version of controlled solutions, one may encounter model creation [2], [5]. Study [2] describes an algorithm, which consists of meta-model controlled items.…”

Section: Related Researchmentioning

confidence: 99%

See 1 more Smart Citation

Towards the Model-driven Software Configuration Management Process/ Modeļu vadāmais programmatūras konfigurācijas pārvaldības process/ Процесс управления конфигурациями программного обеспечения, основанный на моделях

Bartusevičs

Novickis

2014

Information Technology and Management Science

View full text Add to dashboard Cite

show abstract

“…Conflicts may also occur due to same intentions of users who edited a copy of the same artifact (Altmanninger, 2007). For example, a conflict resulting from contradicting intentions is raised if both users rename the same method of a class in a UML class diagram with different intentions.…”

Section: Introductionmentioning

confidence: 97%

A categorization for conflicts in model versioning

Altmanninger¹,

Pierantonio

2011

Elektrotech. Inftech.

View full text Add to dashboard Cite

To coordinate different versions of a software model, edited by modelers in parallel, various model versions need to be merged to one consolidated version. Therefore, adequate tool support in terms of version control systems (VCSs) is considered essential. Diverse approaches evolved for merging model versions including different conflict detection methods. Indeed, only a limited consensus about possible categories for conflicts exists. A common terminology and a categorization of possible types of conflict are missing.In this article we propose a categorization for conflicts in model versioning along with an assessment of levels of severity: a base for future discussions and comparison of approaches to conflict detection on models.Eine Kategorisierung von Konflikten in der Modellversionierung.Zur Koordination der verteilten Bearbeitung von Software-Modellen mü ssen die entstandenen Modellversionen wieder zusammengefü hrt werden. Daher wird eine zufriedenstellende Toolunterstü tzung in Form von Versionierungssystemen (VCSs) als wesentlich erachtet. Es haben sich unterschiedliche Ansä tze fü r das Zusammenfü hren von Modellen einschließlich Konflikterkennungsmethoden entwickelt. Dabei herrscht nur eine eingeschrä nkte Einigkeit ü ber eine mö gliche Kategorisierung von Konflikten. Eine gemeinsame Terminologie und Kategorisierung fehlen.In diesem Artikel wird eine Kategorisierung von Konflikten in der Modellversionierung zusammen mit einer Bewertung der Niveaus der Schwere von Konflikten vorgeschlagen: eine Basis fü r zukü nftige Diskussionen und fü r den Vergleich von Konflikterkennungsansä tzen fü r Modelle.Schlü sselwö rter: Versionierungssystem; Konflikterkennung; Model-Management; modellgetriebene Softwareentwicklung

show abstract

“…A more extensive review on refactoring UML models can be found in [22]. An approach of detecting semantically equivalent modeling concepts for structurally different models is described in [23].…”

Section: Related Workmentioning

confidence: 99%

Removal of Redundant Elements within UML Activity Diagrams

Beckmann

Michalke

Schlutter

et al. 2017

2017 ACM/IEEE 20th International Conference on Model Driven Engineering Languages and Systems (MODELS)

View full text Add to dashboard Cite

Abstract-As the complexity of systems continues to rise, the use of model-driven development approaches becomes more widely applied. Still, many created models are mainly used for documentation. As such, they are not designed to be used in following stages of development, but merely as a means of improved overview and communication. In an effort to use existing UML2 activity diagrams of an industry partner (Daimler AG) as a source for automatic generation of software artifacts, we discovered, that the diagrams often contain multiple instances of the same element. These redundant instances might improve the readability of a diagram. However, they complicate further approaches such as automated model analysis or traceability to other artifacts because mostly redundant instances must be handled as one distinctive element. In this paper, we present an approach to automatically remove redundant ExecutableNodes within activity diagrams as they are used by our industry partner. The removal is implemented by merging the redundant instances to a single element and adding additional elements to maintain the original behavior of the activity. We use reachability graphs to argue that our approach preserves the behavior of the activity. Additionally, we applied the approach to a real system described by 36 activity diagrams. As a result 25 redundant instances were removed from 15 affected diagrams.

show abstract

Models in Conflict – Towards a Semantically Enhanced Version Control System for Models

Cited by 23 publications

References 12 publications

Towards the Model-driven Software Configuration Management Process/ Modeļu vadāmais programmatūras konfigurācijas pārvaldības process/ Процесс управления конфигурациями программного обеспечения, основанный на моделях

Towards the Model-driven Software Configuration Management Process/ Modeļu vadāmais programmatūras konfigurācijas pārvaldības process/ Процесс управления конфигурациями программного обеспечения, основанный на моделях

A categorization for conflicts in model versioning

Removal of Redundant Elements within UML Activity Diagrams

Contact Info

Product

Resources

About