Preserving Architectural Choices throughout the Component-based Software Development Process

Tibermacine, Chouki; Fleurquin, Régis; Sadou, Salah

doi:10.1109/wicsa.2005.52

Cited by 13 publications

(18 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The lack of one of these two aspects could lead to undetected StAD violations. In the literature, the existing work about ADLs [1,13] or architectural constraints [37,38] focus solely on the structural consistency aspect. The validity of StADs is maintained as long as concerned elements structurally conform to their playing roles in the architecture.…”

Section: Illustration and Problemmentioning

confidence: 99%

See 1 more Smart Citation

Preserving architectural decisions through architectural patterns

et al. 2014

View full text Add to dashboard Cite

Architectural decisions have emerged as a means to maintain the quality of the architecture during its evolution. One of the most important decisions made by architects are those about the design approach such as the use of patterns or styles in the architecture. The structural nature of this type of decisions give them the potential to be controlled systematically. In the literature, there are some works on the automation of architectural decision violation checking. In this paper we show that these works do not allow to detect all possible architectural decision violations. To solve this problem we propose an approach which: i) describes architectural patterns that hold the architectural decision definition, ii) integrates architectural decisions into an architectural model and, iii) automates the architectural decision conformance checking. The approach is implemented using Eclipse Modeling Framework and its accompanying technologies. Starting from well-known architectural patterns, we show that we can formalize all those related to the structural aspect. Through two evaluations, we show that our approach can be adapted to different architecture paradigms and allows to detect more violations comparing to the existing approaches.

show abstract

Section: Illustration and Problemmentioning

confidence: 99%

“…Being one of the first work dealing with StAD conformance checking, Tibermacine et al [37,38] propose a family of architectural constraint languages to describe the structural part of StAD. Architectural constraints are used as a means to formalize StADs.…”

Section: Ad Conformance Checkingmentioning

confidence: 99%

Preserving architectural decisions through architectural patterns

et al. 2014

View full text Add to dashboard Cite

show abstract

“…It consists in making explicit and formal the reasons behind architectural decisions. The choice of a formal language to specify this documentation guarantees not only the unambiguity of descriptions but also allows the automation of some operations, like the preservation of architectural choices throughout the development process of a component-based software [23].…”

Section: Principles Of the Approachmentioning

confidence: 99%

“…We describe this ADs using the standard profile of ACL, which is composed of CCL and of a generic architecture metamodel called ArchMM [23]. This metamodel is used as an intermediate representation when transforming ACL constraints from one profile to another.…”

Section: Ad Definition Languagementioning

confidence: 99%

On-Demand Quality-Oriented Assistance in Component-Based Software Evolution

Tibermacine

Fleurquin

Sadou

2006

Component-Based Software Engineering

View full text Add to dashboard Cite

Abstract. During an architectural evolution of a component-based software, certain quality attributes may be weakened. This is due to the lack of an explicit definition of the links between these non-functional characteristics and the architectural decisions implementing them. In this paper, we present a solution that aims at assisting the software maintainer during an evolution activity on his demand. It requires the definition of a documentation during development, organized in the form of bindings between formal descriptions of architectural decisions and their targeted quality attributes. Through an assistance algorithm, the approach uses this documentation in order to notify the maintainer of the possible effects of architectural changes on quality requirements. We also present a prototype tool which automates our proposals. This tool and the overall approach has been experienced on a real-world software in order to validate them.

show abstract

“…In order to make explicit architectural decisions, we proposed ACL, an Architecture Constraint Language [11]. Architectural decisions are thus formalised as architecture predicates which have as a context an architectural element (component, connector, etc.)…”

Section: Formalization Of Architectural Decisions With Aclmentioning

confidence: 99%

Component Deployment Evolution Driven by Architecture Patterns and Resource Requirements

Hoareau

Tibermacine

2006

Software Architecture

View full text Add to dashboard Cite

Abstract. Software architectures are often designed with respect to some architecture patterns, like the pipeline and peer-to-peer. These patterns are the guarantee of some quality attributes, like maintainability or performance. These patterns should be dynamically enforced in the running system to benefit from their associated quality characteristics at runtime. In dynamic hosting platforms where machines can enter the network, offering new resources, or fail, making the components they host unavailable, these patterns can be affected. In addition, in this kind of infrastructures, some resource requirements can also be altered. In this paper we present an approach which aims at dynamically assist deployment process with information about architectural patterns and resource constraints. This ensures that, faced with disconnections or machine failures, the runtime system complies permanently with the original architectural pattern and the initial resource requirements.

show abstract

Preserving Architectural Choices throughout the Component-based Software Development Process

Cited by 13 publications

References 10 publications

Preserving architectural decisions through architectural patterns

Preserving architectural decisions through architectural patterns

On-Demand Quality-Oriented Assistance in Component-Based Software Evolution

Component Deployment Evolution Driven by Architecture Patterns and Resource Requirements

Contact Info

Product

Resources

About