53 Analyzing Interoperability in a Nonfunctional Requirements Ecosystem to Support Crisis Management Response

53.1. Introduction

The “ilities are desired properties of a system [...] that often manifest themselves after a system has been put into its initial use” [DEW 12]. In other words, “-ilities” are non-functional requirements to be reached and that provide a “special” capacity to a system to support the achievement of its mission. Numerous -ilities are identified in the literature, such as robustness, resilience, reliability and interoperability [ROS 12]. These non-functional requirements are clearly identified as requirements that have an impact on the functioning, the achievement of the mission and the performances of a system that must be mastered. This is typically the case of interoperability in a crisis context where it stands as a requirement that plays a major role between actors that develop plans, actions and processes to build an adapted crisis response. In this context and like any other requirement, interoperability is developed through technological (e.g. enterprise service bus), organizational (e.g. collaborative processes) or else conceptual (e.g. data management) aspects [ISO 09]. A part of these developments is related to the evaluation of interoperability in order to know its degree of satisfaction and further, if a given interoperability solution is fully adapted. Indeed, the evaluation of interoperability allows actors to either build a response before ...

Get Enterprise Interoperability: Smart Services and Business Impact of Enterprise Interoperability now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.