Human-centered specification exemplars for critical infrastructure environments.

Specification models of critical infrastructure focus on parts of a larger environment. However, to consider the security of critical infrastructure systems, we need approaches for modelling the sum of these parts; these include people and activities, as well as technology. This paper presents human-centered specification exemplars that capture the nuances associated with interactions between people, technology, and critical infrastructure environments. We describe requirements each exemplar needs to satisfy, and present preliminary results in developing and evaluating them

A Goal Modeling Framework for Self-contextualizable Software

Abstract. Self-contextualizability refers to the system ability to autonomously adapt its behaviour to context in order to maintain its objectives satisfied. In this paper, we propose a modeling framework to deal with self-contextualizability at the requirements level. We use Tropos goal models to express requirements; we provide constructs to analyse and represent context at each variation point of the goal model; and we exploit the goal and context analysis to define how the system satisfies its requirements in different contexts. Tropos goal analysis provides constructs to hierarchically analyse goals and discover alternative sets of tasks the system can execute to satisfy goals; our framework extends Tropos goal model by considering context at its variation points, and provides constructs to hierarchically analyse context and discover alternative sets of facts the system has to monitor to verify a context. A self-contextualizable promotion information system scenario is used to illustrate our approach. Key words: GORE, Context Analysis, Self-Contextualization

Requirements Engineering

Requirements Engineering (RE) aims to ensure that systems meet the needs of their stakeholders including users, sponsors, and customers. Often consid- ered as one of the earliest activities in software engineering, it has developed into a set of activities that touch almost every step of the software development process. In this chapter, we reflect on how the need for RE was first recognised and how its foundational concepts were developed. We present the seminal papers on four main activities of the RE process, namely (i) elicitation, (ii) modelling & analysis, (iii) as- surance, and (iv) management & evolution. We also discuss some current research challenges in the area, including security requirements engineering as well as RE for mobile and ubiquitous computing. Finally, we identify some open challenges and research gaps that require further exploration

Automatic Monitoring of Software Requirements

Automatic run-time monitoring of software systems' design- / purchase- / installation- time requirements and assumptions is a key step towards making those systems more robust, maintainable, and self-evolving. A concise language has been designed to permit the convenient expression of a wide range of requirements and assumptions. A compiler automatically converts these expressions into run-time monitors to watch for, and report, all requirement and assumption violations. The mechanism is applicable to systems which have not necessarily been designed with monitoring in mind, permits addition of further requirements and assumption monitoring on-the-fly, and emphasizes usability by a wide range of end-users. Keywords Monitoring, requirements, assumptions, expectations, maintenance, robustness, software evolution. INTRODUCTION It is common for the environment within which a software system resides to evolve. Assumptions of both the requirements that the system must fulfill, and the o..