Maurice Glandrup

  • Citations Per Year
Learn More
This document describes the results of the two-day workshop on Advanced Separation of Concerns at ECOOP 2001. The workshop combined presentations with tigthly focused work in small groups on these predefined topics: requirements and challenges for ASoC technologies, conventional solutions for ASoC problems, feature interaction, design support forASoC and(More)
It is generally acknowledged that separation of concerns is a key requirement for effective software engineering: it helps in managing the complexity of software and supports the maintainability of a software system. Separation of concerns makes only sense if the realizations in software of these concerns can be composed together effectively into a working(More)
It is generally acknowledged that separation of concerns is a key requirement for effective software engineering: it helps in managing the complexity of software and supports the maintainability of a software system. Separation of concerns makes only sense if the realizations in software of these concerns can be composed together effectively into a working(More)
Mission-critical, distributed systems are often designed as a set of distributed, components that interact using publish/subscribe middleware. Currently, in these systems, software components are usually statically allocated to the nodes to fulfil predictability, reliability requirements. However, a static allocation of components has major drawbacks, e.g.(More)
Anticipating future software requirements might support the evolution of software systems and as such reduce the cost of development and maintenance in due time. Unfortunately identifying the right set of evolution scenarios is difficult due to the uncertainty of occurrence of future requirements. In this paper we propose the Software Evolution Analysis(More)
  • 1