Modeling Architectural Patterns’ Behavior Using Architectural Primitives

Kamal, Ahmad; Avgeriou, Paris

doi:10.1007/978-3-540-88030-1_13

Cited by 9 publications

(9 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [19,34], the authors propose to use a number of "architectural primitives" to model architectural patterns. Through the stereotype extension mechanism of UML, one can define architectural primitives to design a specific structure [19] or behavior [34] of a pattern. Each primitive is a tangible modeling element with its own semantic that can be composed to form a pattern.…”

Section: Architecture Constraint Reuse At Design Stage In Adlsmentioning

confidence: 99%

Software architecture constraint reuse-by-composition

Tibermacine

Sadou

That

et al. 2016

Future Generation Computer Systems

View full text Add to dashboard Cite

Architecture constraints are specifications which enable developers to formalize design rules that architectures should respect, like the topological conditions of a given architecture pattern or style. These constraints can serve as a documentation to better understand an existing architecture description, or can serve as invariants that can be checked after the application of an architecture change to see whether design rules still hold. Like any specifications, architecture constraints are frequently subject to reuse. Besides, these constraints are specified and checked during architecture design time, when component descriptions are specified (or selected from repositories), then instantiated and connected together to define architecture descriptions. These two facts (being subject to reuse and instantiation/connection) make architecture constraints good candidates for component-based design within a unified environment. In this paper, we propose a component model for specifying architecture constraints. This model has been implemented as an extension to an ADL that we have developed, which is called CLACS. The obtained process advocates the idea of specifying architecture constraints using the same paradigm (of component-based development) as for architecture description. To evaluate the component model, we conducted an experiment with a catalog of constraints formalizing the topological conditions of architecture patterns. The results of this experiment showed that constraint specification is improved by this reuse-by-composition model.

show abstract

Section: Architecture Constraint Reuse At Design Stage In Adlsmentioning

confidence: 99%

Software architecture constraint reuse-by-composition

Tibermacine

Sadou

That

et al. 2016

Future Generation Computer Systems

View full text Add to dashboard Cite

show abstract

“…Unfortunately, it only provides limited support for modelling behavioural patterns like synchronous and asynchronous communication, push and pull. A recent modelling paper [14] proposes to use stereotypes to express these architectural primitives, an idea that we adopt in our framework.…”

Section: Related Workmentioning

confidence: 99%

“…Synchronous messages are mostly used to pull information and can contain information in the request message. The "push" stereotype [14] can be used to explicitly specify information push.…”

Section: Conceptual Frameworkmentioning

confidence: 99%

“…These systems present different properties and attributes, which make them suitable for specific application areas or contexts. Based on our own experience and literature study (e.g., [14,[16][17][18]), we identify the following groups of properties (scalability, efficiency, pervasiveness, and maintainability) that characterize pervasive systems:…”

Section: Properties Of Pervasive Systemsmentioning

confidence: 99%

See 1 more Smart Citation

Reuse of pervasive system architectures

Bijwaard¹,

Zwaag²,

Meratnia³

et al. 2014

ICST Transactions on Ubiquitous Environments

View full text Add to dashboard Cite

Developers are often confronted with incompatible systems and lack a proper system abstraction that allows easy integration of various hardware and software components. To try solve these shortcomings, building blocks are identified at different levels of detail in today's pervasive/communication systems and used in a conceptual reasoning framework allowing easy comparison and combination. The generality of the conceptual framework is validated by decomposing a selection of pervasive systems into models of these building blocks and integrating these models to create improved ones. Additionally, the required properties of pervasive systems on scalability, efficiency, degree of pervasiveness, and maintainability are analysed for a number of application areas. The pervasive systems are compared on these properties. Observations are made, and weak points in the analysed pervasive systems are identified. Furthermore, we provide a set of recommendations as a guideline towards flexible architectures that make pervasive systems usable in a variety of applications.

show abstract

“…The challenges described above are already a focus of ongoing work in the field of software design to effectively model patterns within a system design [8] [9]. In this paper, we address these problems with a specific focus on tackling the issue of modeling pattern variability.…”

Section: Introductionmentioning

confidence: 99%

Modeling the variability of architectural patterns

Kamal

Avgeriou

2010

Proceedings of the 2010 ACM Symposium on Applied Computing

Self Cite

View full text Add to dashboard Cite

Architectural patterns provide proven solutions to recurring design problems that arise in a system context. A major challenge for modeling patterns in a system design is effectively expressing pattern variability. However, modeling pattern variability in a system design remains a challenging task mainly because of the infinite pattern variants addressed by each architectural pattern. This paper is an attempt to solve this problem by categorizing the solution participants of patterns. More precisely, we identify variable participants that lead to specializations within individual pattern variants and participants that appear over and over again in the solution specified by several patterns. With examples and a case study, we demonstrate the successful applicability of this approach for designing systems. Using the UML extension mechanism, we offer extensible architectural modeling constructs that can be used for modeling several pattern variants.

show abstract

Modeling Architectural Patterns’ Behavior Using Architectural Primitives

Cited by 9 publications

References 9 publications

Software architecture constraint reuse-by-composition

Software architecture constraint reuse-by-composition

Reuse of pervasive system architectures

Modeling the variability of architectural patterns

Contact Info

Product

Resources

About