2001
DOI: 10.1007/3-540-45254-0_10
|View full text |Cite
|
Sign up to set email alerts
|

Architectural Reflection Realising Software Architectures via Reflective Activities

Abstract: Abstract. Architectural reflection is the computation performed by a software system about its own software architecture. Building on previous research and on practical experience in industrial projects, in this paper we expand the approach and show a practical (albeit very simple) example of application of architectural reflection. The example shows how one can express, thanks to reflection, both functional and non-functional requirements in terms of object-oriented concepts, and how a clean separation of con… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
15
0
1

Year Published

2005
2005
2016
2016

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 20 publications
(16 citation statements)
references
References 18 publications
0
15
0
1
Order By: Relevance
“…However, the principles of computational reflection are also applicable to programming-in-the-large, which represents the complex self-adaptive software systems we are interested in our research [Andersson et al 2009b]. In fact, numerous previously developed self-adaptation approaches (e.g., [Cazzola et al 1999;Tisato et al 2001;Blair et al 2004]) are based on the principles of reflection. Figure 1 provides an overview of the FORMS's primitives and their relationships to the reflection perspective.…”
Section: Reflection Perspectivementioning
confidence: 99%
“…However, the principles of computational reflection are also applicable to programming-in-the-large, which represents the complex self-adaptive software systems we are interested in our research [Andersson et al 2009b]. In fact, numerous previously developed self-adaptation approaches (e.g., [Cazzola et al 1999;Tisato et al 2001;Blair et al 2004]) are based on the principles of reflection. Figure 1 provides an overview of the FORMS's primitives and their relationships to the reflection perspective.…”
Section: Reflection Perspectivementioning
confidence: 99%
“…Introspection is the observation of an application's own behavior, while intercession is the reaction on introspection's results, which can be structural, parameter or context adaptation [67]. Reflection techniques have been investigated with self-adaptive systems as an underlying principle for self-awareness on different levels of software, e.g., architectural reflection [68], behavioral reflection. However, these methods apply reflection on the software itself, while we consider reflexive behavior with respect to unanticipated changes at the larger ecosystem level to support evolution of the ecosystem, and not at the system level.…”
Section: Reflexivitymentioning
confidence: 99%
“…Few ADLs support dynamic architecture representation: Darwin (Magee et al, 1995), Dynamic Wright (Allen et al, 1998), -Space (Chaudet & Oquendo, 2000), C2SADEL (Medvidovic et al, 1999;, Piccola (Nierstrasz & Achermann, 2000), Pilar (Cuesta et al, 2005), ArchWare -ADL Oquendo 2004), ArchWare C&C-ADL . Most of them are not suitable to support unplanned dynamic architecture evolution as they consider different representations for the concrete and abstract levels, and use reflection mechanisms to switch among these representations: a dynamic architecture is first defined at abstract level and is then reflected (1) into a dynamic evolvable concrete software-intensive system (Cazzola et al, 1999;Tisato et al, 2000) or (2) into another, evolved abstract representation (Cuesta et al, 2001;Cuesta et al, 2005). The link between the abstract level and the concrete one is not maintained, leading to a situation in which only anticipated modifications can be supported dynamically.…”
Section: Related Workmentioning
confidence: 99%