Why is My Component and Connector Views Specification Unsatisfiable?

Maoz, Shahar; Pomerantz, Nitzan; Ringert, Jan Oliver; Shalom, Rafi

doi:10.1109/models.2017.26

Cited by 3 publications

(2 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Since these checks are completely automatic, they can be integrated in a commit-based or nightly continuous integration process. These algorithms are described by Maoz and Ringert [15].…”

Section: Improving the Development Process At Daimler Agmentioning

confidence: 99%

Improving the Model-Based Systems Engineering Process

Wenckstern

2022

Ernst Denert Award for Software Engineering 2020

View full text Add to dashboard Cite

Modern embedded software systems are becoming more and more complex. Engineering embedded systems raise specific challenges that are rarely present in other software engineering disciplines due to the systems’ steady interactions with their environment. Research and industry often describe embedded systems as component and connector models (C&C). C&C models describe the logical architecture by focusing on software features and their logical communications. In C&C models, hierarchical decomposed components encapsulate features, and connectors model the data flow between components via typed ports. As extra-functional properties, for example, safety and security, are also key features of embedded systems, C&C models are mostly enriched with them. However, the process to develop, understand, validate, and maintain large C&C models for complex embedded software is onerous, time consuming, and cost intensive. Hence, the aim of this chapter is to support the automotive software engineer with: (i) automatic consistency checks of large C&C models, (ii) automatic verification of C&C models against design decisions, (iii) tracing and navigating between design and implementation models, (iv) finding structural inconsistencies during model evolution, (v) presenting a flexible approach to define different extra-functional properties for C&C models, and (vi) providing a framework to formalize constraints on C&C models for extra-functional properties for automatic consistency checks.

show abstract

“…Since these checks are completely automatic, they can be integrated in a commit-based or nightly continuous integration process. These algorithms are described by Maoz and Ringert [15].…”

Section: Improving the Development Process At Daimler Agmentioning

confidence: 99%

Improving the Model-Based Systems Engineering Process

Wenckstern

2022

Ernst Denert Award for Software Engineering 2020

View full text Add to dashboard Cite

show abstract

“…T ime is a set of point structure of time, modeled by a global clock. Moreover, (In ∩ Out ∩ Spec) = ∅, and the set of data and control values is disjoint.Now, borrowing from the syntax and semantics of components and connectors views[16,18], we formalize the structure of the timed-event component and connector model (TeC&C) model by not focusing on the interfaces defined for the ports, but rather on the relation between the different pieces of the TeC&C model.Definition 5.2. A timed-event component and connector TeC&C model is a sextuple structure CC = (C, C, P, S, δ p , δ t ) where (i) C = {C 1 , C 2 , .…”

mentioning

confidence: 99%

On Architectural Decay Prediction and Detection in Real-Time Software Systems

Fellah¹,

Bandi

EPiC Series in Computing

View full text Add to dashboard Cite

As the number of software applications including the widespread of real-time and em- bedded systems are constantly increasing and tend to grow in complexity, the architecture tends to decay over the years, leading to the occurrence of a spectrum of defects and bad smells (i.e., instances of architectural decay) that are manifested and sustained over time in a software system’s life cycle. Thus, the implemented system is not compliant to the specified architecture and such architectural decay becomes an increasing challenge for the developers. We propose a set of constructive architecture views at different levels of granularity, which monitor and ensure that the modifications made by developers at the implementation level are in compliance with those of the different architectural timed-event elements of real-time systems. Thus, we investigated a set of orthogonal architectural de- cay paradigms timed-event component decay, timed-event interface decay, timed-event connector decay and timed-event port decay. All of this has led to predicting, forecasting, and detecting architectural decay with a greater degree of structure, abstraction techniques, architecture reconstruction; and hence offered a series of potential effectiveness and enhancement in gaining a deeper understanding of implementation-level bad smells in real-time systems. Furthermore, to support this research towards an effective architectural decay prediction and detection geared towards real-time and embedded systems, we investigated and evaluated the effect of our approach through a real-time Internet of Things (IoT) case study.

show abstract

Semantic comparisons of Alloy models

Ringert

Wali

2020

Proceedings of the 23rd ACM/IEEE International Conference on Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

Why is My Component and Connector Views Specification Unsatisfiable?

Cited by 3 publications

References 13 publications

Improving the Model-Based Systems Engineering Process

Improving the Model-Based Systems Engineering Process

On Architectural Decay Prediction and Detection in Real-Time Software Systems

Semantic comparisons of Alloy models

Contact Info

Product

Resources

About