Software Architecture Evolution

Barais, Olivier; Meur, Anne-Françoise Le; Duchien, Laurence; Lawall, Julia

doi:10.1007/978-3-540-76440-3_10

Cited by 28 publications

(20 citation statements)

References 36 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Tamzalit and Mens [5] used graph transformations to express architectural evolution patterns to introduce architectural styles as well as to verify whether a given architectural evolution preserves the constraints imposed by an architectural style. Another approach to transformation-based architectural evolution, though not directly relying on graph transformation, is work by Barais [6]. These contributions focus on structural aspects of architecture descriptions without taking the behavior into account.…”

Section: Applicability Of the Evolution Patternsmentioning

confidence: 99%

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

Section: Applicability Of the Evolution Patternsmentioning

confidence: 99%

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

show abstract

“…Requirements evolve [11] due to changes in the stakeholders needs, in organizational policies, in norms and laws in the deployment environment, and as a result of feedback about system operation. Architectural evolution [1] can be either internal-the architecture topology changes-or external-the specification of components and interactions is altered.…”

Section: Introductionmentioning

confidence: 99%

Aligning Service-Oriented Architectures with Security Requirements

Salnitri

Dalpiaz

Giorgini

2012

On the Move to Meaningful Internet Systems: OTM 2012

View full text Add to dashboard Cite

Abstract. Aligning requirements and architectures is a long-standing concern in software engineering. Alignment is crucial in the area of systems evolution, wherein requirements and system architectures keep changing after system deployment. We address a specific alignment problem, i.e., checking the compliance of a service-oriented architecturerepresenting a composite service-with security requirements. Serviceoriented architectures are dynamic (services can be replaced on-the-fly), and assessing compliance with security requirements is key, since noncompliance may lead to sanctions as well as privacy violation. After motivating and describing the problem, we propose algorithms to check two specific security requirements: non-disclosure and non-repudiation. We illustrate the approach using a scenario about e-government.

show abstract

“…By providing formal syntax and semantics, ADLs facilitate analysis, which provide input for engineered evolution. However, existing ADLs do not provide any techniques to specify architectural change in the context of evolution [6].…”

Section: Related Workmentioning

confidence: 99%