Modelling the Asynchronous Dynamic Evolution of Architectural Types

Costa-Soria, Cristóbal; Heckel, Reiko

doi:10.1007/978-3-642-14412-7_10

Cited by 2 publications

(2 citation statements)

References 32 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A software component is an architectural entity that (1) encapsulates a subset of the system's functionality and/or data, (2) restricts access to that subset via an explicitly defined interface, and (3) has explicitly defined dependencies on its required execution context. (Taylor et al, 2009) A component is a computational element that permits users to structure the functionality of software systems.…”

Section: Componentmentioning

confidence: 99%

See 1 more Smart Citation

Dynamic Evolution and Reconfiguration of Software Architectures Through Aspects

Cubel

Benedí

Costa-Soria

View full text Add to dashboard Cite

Change is an intrinsic property of software. A software system, during its lifetime, may require several updates, improvements, or new features. If these change requirements are not addressed, the risk of becoming a useless system increases. In fact, this is a challenging issue of safety-and mission-critical software systems, which cannot be stopped to perform maintenance or evolution operations due to their continuous operation. To reduce the aging of these critical systems, they must be provided with mechanisms enabling their dynamic evolution, i.e. the support of changes on their structure and behaviour while they remain in operation.This thesis is concerned with the design of a framework to build architecturebased, dynamically evolvable, software systems. The fact that this framework is a software architecture based approach provides the following advantages: (i) it offers a high-level of abstraction for describing dynamic changes; (ii) it allows varying the level of system description; and (iii) it advantages from the existing support for system modelling, code-generation, and formal analysis provided by architecture description languages.The framework presented in this thesis, called Dynamic PRISMA, is characterized by the combination of two levels of dynamism: Dynamic Reconfiguration, which addresses changes at the configuration level (i.e. the architectural configuration), and Dynamic Type Evolution, which addresses changes at the type-level (i.e. the specification of architectural types and instances). This combination is one of the major contributions of this thesis: thus a system is not only able to reconfigure at runtime the building blocks it is composed of (i.e. architectural types), but also to redefine these building blocks (or introduce new ones) at runtime.Another contribution of the thesis is the identification of the concerns related to dynamic evolution and their integration in the framework through aspects. This improves the separation of concerns and allows us to change reconfiguration specifications, evolution mechanisms, or the business logic independently of each other.A third contribution of this thesis is how this dynamism is supported: reconfiguration through autonomic capabilities, which provides proactivity according to either internal or external stimuli; and type evolution through asynchronous reflection, which enables the modification of a type specification and the transformation of their instances at different rates (i.e. when they are ready for evolution). Specifically, the asynchronous evolution vi semantics is precisely described by means of graph transformations. This formalism has been chosen because it naturally models both the system architecture and its asynchronous evolution.The work presented in this thesis is illustrated through a case study from the robotics domain; an area which could potentially benefit from the results of this thesis. KEYWORDSsoftware architectures, dynamic evolution, dynamic reconfiguration, dynamic type evolution, dynamic instance evol...

show abstract

Section: Componentmentioning

confidence: 99%

“…6 The most extended definition of passive status is restricted to only independent transactions (i.e. which cannot be nested).…”

Section: Quiescencementioning

confidence: 99%

Dynamic Evolution and Reconfiguration of Software Architectures Through Aspects

Cubel

Benedí

Costa-Soria

View full text Add to dashboard Cite

show abstract

Business process and software architecture model co-evolution patterns

Jamshidi¹,

Pahl²

2012

2012 4th International Workshop on Modeling in Software Engineering (MISE)

View full text Add to dashboard Cite

Abstract-Software systems are subject to change. To embrace change, the systems should be equipped with automated mechanisms. Business process and software architecture models are two artifacts that are subject to change in an interrelated manner that requires them co-evolve. As opposed to the traditional batch-based model transformation, we propose a comprehensive set of structural and behavioral evolution patterns that enable to incrementally reflect the impact of change of business processes to their associated architecture models by applying reusable patterns. A basis for automation is provided through a graph-based formalism.

show abstract

Modelling the Asynchronous Dynamic Evolution of Architectural Types

Cited by 2 publications

References 32 publications

Dynamic Evolution and Reconfiguration of Software Architectures Through Aspects

Dynamic Evolution and Reconfiguration of Software Architectures Through Aspects

Business process and software architecture model co-evolution patterns

Contact Info

Product

Resources

About