12,000

We have over 12,000 students, from over 100 countries, within one of the safest campuses in the UK

93%

93% of Lancaster students go into work or further study within six months of graduating

Home > Research > Publications & Outputs > Requirements reflection: requirements as runtim...
View graph of relations

« Back

Requirements reflection: requirements as runtime entities

Research output: Contribution in Book/Report/ProceedingsPaper

Published

Publication date05/2010
Host publicationICSE '10 Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
Place of publicationNew York
PublisherACM
Pages199-202
Number of pages4
ISBN (Print)978-1-60558-719-6
Original languageEnglish

Conference

ConferenceInternational Conference on Software Engineering (ICSE 2010)
CityCapetown, South Africa
Period2/05/108/05/10

Conference

ConferenceInternational Conference on Software Engineering (ICSE 2010)
CityCapetown, South Africa
Period2/05/108/05/10

Abstract

Computational reflection is a well-established technique that gives a program the ability to dynamically observe and possibly modify its behavior. To date, however, reflection is mainly applied either to the software architecture or its implementation. We know of no approach that fully supports requirements reflection– that is, making requirements available as runtime objects. Although there is a body of literature on requirements monitoring, such work typically generates runtime artifacts from requirements and so the requirements themselves are not directly accessible at runtime. In this paper, we define the notion of requirements reflection and set out a research agenda. Requirements reflection is important because software systems of the future will be self-managing and will need to adapt continuously to changing environmental conditions. We argue that requirements reflection can support such self-adaptive systems by making requirements first-class runtime entities, thus endowing software systems with the ability to reason about, understand, explain and modify requirements at runtime.