Model-Centric, Context-Aware Software Adaptation

Software must be constantly adapted to changing requirements. The time scale, abstraction level and granularity of adaptations may vary from short-term, fine-grained adaptation to long-term, coarse-grained evolution. Fine-grained, dynamic and context-dependent adaptations can be particularly difficult to realize in long-lived, large-scale software systems. We argue that, in order to effectively and efficiently deploy such changes, adaptive applications must be built on an infrastructure that is not just model-driven, but is both model-centric and context-aware. Specifically, this means that high-level, causally-connected models of the application and the software infrastructure itself should be available at run-time, and that changes may need to be scoped to the run-time execution context. We first review the dimensions of software adaptation and evolution, and then we show how model-centric design can address the adaptation needs of a variety of applications that span these dimensions. We demonstrate through concrete examples how model-centric and context-aware designs work at the level of application interface, programming language and runtime. We then propose a research agenda for a model-centric development environment that supports dynamic software adaptation and evolution.

Vitreoretinal Interface Changes in Geographic Atrophy.

PURPOSE Geographic atrophy (GA) is the end-stage manifestation of atrophic age-related macular degeneration (AMD). The disease progresses slowly over time, eventually causing loss of central vision. Its cause and pathomechanism are not fully known. Previous studies have suggested that vitreoretinal traction (VRT) may contribute to the progression of neovascular AMD. The aim of this study was to examine whether an association between changes at the vitreoretinal interface (VRI), in particular traction (VRT), and the characteristics and progression of GA in eyes with dry AMD can be established. DESIGN Clinic-based prospective cohort study. PARTICIPANTS A total of 97 patients (age range, 61-90 years; mean, 78.4 years) with GA secondary to dry AMD were enrolled. Patients exhibiting neovascular signs on fluorescein angiography in either eye were excluded. METHODS The VRI changes were examined using spectral-domain optical coherence tomography (SD-OCT). Characteristics of GA were examined using fundus autofluorescence (FAF) imaging. All imaging was performed using a Spectralis SLO+OCT device (Heidelberg Engineering, Heidelberg, Germany); GA area was measured using the Region Finder (Heidelberg Engineering) software native to the Spectralis platform. MAIN OUTCOME MEASURES Area and increase in area of GA. RESULTS A total of 97 eyes were examined. Vitreoretinal traction was found in 39 eyes (40%). The GA area at baseline was 6.65±5.64 mm(2) in eyes with VRT and 5.73±4.72 mm(2) in eyes with no VRT. The annual rate of progression of GA area progression was 2.99±0.66 mm(2) in eyes with VRT and 1.45±0.67mm(2) in eyes without VRT. Differences between groups in both parameters were statistically significant (n = 97 total number of eyes; P<0.001). Multiple regression analysis confirmed this finding (B = 0.714, P<0.001; F3,93 = 72.542, P<0.001; adjusted R(2) = 0.691) CONCLUSIONS: Our results indicate an association between VRT and an increased rate of progression of GA area in dry AMD. Monitoring VRT may contribute to an improved estimate of the prospective time of visual loss and to a better timing of emerging therapies in dry AMD.

Spotter: towards a unified search interface in IDEs

Program comprehension requires developers to reason about many kinds of highly interconnected software entities. Dealing with this reality prompts developers to continuously intertwine searching and navigation. Nevertheless, most integrated development environments (IDEs) address searching by means of many disconnected search tools, making it difficult for developers to reuse search results produced by one search tool as input for another search tool. This forces developers to spend considerable time manually linking disconnected search results. To address this issue we propose Spotter, a model for expressing and combining search tools in a unified way. The current implementation shows that Spotter can unify a wide range of search tools. More information about Spotter can be found at scg.unibe.ch/research/moldablespotter