bCMS requirements modelling using SysML/KAOS (Initial requirements model submission) Christophe Gnaho, Régine Laleau, Farida Semmak LACL/U. Paris-Est Créteil Créteil, France Christophe.gnaho@free.fr , {semmak, laleau}@u-pec. fr Jean-Michel Bruel IRIT/U. of Toulouse Toulouse, France bruel@irit.fr Abstract—In this paper we have modelled an illustrative subset of the requirements of the bCMS case study using a combined approach called SysML/KAOS˙. This submission is part of a broader effort that aims at the comparison of those three specific requirements modelling techniques (see [1], [2], [3], [4]). Keywords—goal-oriented requirements; SysML; functional requirement; non-functional requirements I. INTRODUCTION The OMG has recently proposed SysML [5], an UML extension for complex systems. This language has some interesting advantages. It provides concepts for linking requirements to the design and the implementation elements, thus ensuring continuity from requirements analysis to implementation. Since it is a UML profile, it offers other benefits like the ability to quickly and easily develop open source tools to support creation of models. However, the SysML concepts for requirements specification are not as rich as those proposed in goal-oriented approaches. We think that it would be interesting to take advantage of the contribution of SysML while providing a clear definition of requirements and relationships between them. The SysML/KAOS [6], [7], [8] language tries to provide an answer to this issue. The SysML/KAOS language is an extension of the SysML requirements language [5] with the most relevant concepts of KAOS and NFR Framework, two approaches largely recognized and used in requirements engineering over the past decade. The main idea is to combine the concepts of KAOS [10] that are better suited to represent functional requirements with concepts of the NFR model [9] which are most relevant to specify non-functional requirements. This allows the integration of non-functional requirements much earlier at the same level of abstraction than functional requirements. There are a number of advantages to use Goal Oriented Requirements Engineering (GORE) approaches. They allow detection and resolution of conflicts among requirements and they help reasoning about alternative configurations. In addition to the above advantages, our approach specifically allows the detection and analysis of impact of non-functional requirements on functional requirements. The paper is organized as follows. In the following subsections, we present the bCMS case study as well as the minimum of background needed to understand the models. Section II describes the approach and Section III the bCMS requirements model obtained with the SysML/KAOS approach. After the conclusion, the detailed requirements are provided in Section V. Finally we provide the required statements about the approach in Section VI. A. The bCMS Case Study In this paper we use the SysML/KAOS language to model the bCMS case study 1 . Here is an excerpt of the case study. The bCMS is a distributed crash management system that is responsible for coordinating the communication between a FireStation Coordinator (FSC) and a Police Station Coordinator (PSC) to handle a crisis in a timely manner. Information regarding the crisis as it pertains to the tasks of the coordinators is updated and maintained during and after the crisis. There are two collaborative sub-systems. Thus, the global coordination is the result of the parallel composition of the (software) coordination processes controlled by the two (human) distributed coordinators. There is no central database; fire and police stations maintain separate databases and may only access information from the other database through the bCMS system. Each coordination process is hence in charge of adding and updating information in its respective database. Figure. 1 shows the overall view of the bCMS case study. Fig. 1. bCMS Case Study Overall View 1 Available at http://cserg0.site.uottawa.ca/cma2013re/CaseStudy.pdf