INCREMENT: A Mixed MDE-IR Approach for Regulatory Requirements Modeling and Analysis

[Context and motivation] Regulatory requirements for Nuclear instrumentation and control I&C systems are first class requirements. They are written by national safety entities and are completed through a large documentation set of national recommendation guides and national/international standards. [Question/Problem] I&C systems important to safety must comply to all of these requirements. The global knowledge of this domain is scattered through these different documents and not formalized. Its organization and traceability relationships within this domain is mainly implicit. As a consequence, such long lasting nuclear I&C projects set important challenges in terms of tacit expertise capitalization and domain analysis. [Principal ideas/results] To tackle this domain formalization issue, we propose a dual Model-driven Engineering MDE and Information Retrieval IR approach to address the nuclear regulatory requirements domain definition, and assisted traceability based on the acquired requirements model. [Contributions] In this paper, we present the Connexion metamodel that provides a canvas for the definition and capitalization of the nuclear regulatory requirements domain. We also present an hybrid MDE/IR-based approach, named INCREMENT, for acquiring, modeling and analyzing these regulatory requirements. This approach is supported by a tool that is developed in the context of the CONNEXION project, which gathers French major nuclear I&C industrial actors.

[1]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[2]  Björn Regnell,et al.  An industrial survey of requirements interdependencies in software product release planning , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[3]  G. Johnson Comparison of IEC and IEEE standards for computer-based control systems important to safety , 2001 .

[4]  Peter Sawyer,et al.  REVERE: Support for Requirements Synthesis from Documents , 2002, Inf. Syst. Frontiers.

[5]  Haiyan Zhao,et al.  A feature-oriented approach to modeling requirements dependencies , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[6]  Erik Kamsties,et al.  Understanding Ambiguity in Requirements Engineering , 2005 .

[7]  Daniel Amyot,et al.  Towards a Framework for Tracking Legal Compliance in Healthcare , 2007, CAiSE.

[8]  Annie I. Antón,et al.  The ChoicePoint Dilemma: How Data Brokers Should Handle the Privacy of Personal Information , 2007, IEEE Security & Privacy.

[9]  Christian S. Jensen,et al.  Capturing Temporal Constraints in Temporal ER Models , 2008, ER.

[10]  Jon Doyle,et al.  Semantic parameterization: A process for modeling domain descriptions , 2008, TSEM.

[11]  Annie I. Antón,et al.  Analyzing Regulatory Rules for Privacy and Security Requirements , 2008, IEEE Transactions on Software Engineering.

[12]  John Mylopoulos,et al.  Automating the Extraction of Rights and Obligations for Regulatory Compliance , 2008, ER.

[13]  Axel van Lamsweerde,et al.  Requirements Engineering: From System Goals to UML Models to Software Specifications , 2009 .

[14]  Annie I. Antón,et al.  Developing Production Rule Models to Aid in Acquiring Requirements from Legal Texts , 2009, 2009 17th IEEE International Requirements Engineering Conference.

[15]  Jonas Helming,et al.  Managing iterations with UNICASE , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[16]  Kevin Lano,et al.  Slicing of UML models using model transformations , 2010, MODELS'10.

[17]  Jörg Leuser,et al.  Tackling Semi-automatic Trace Recovery for Large Specifications , 2010, REFSQ.

[18]  Jane Cleland-Huang,et al.  A machine learning approach for tracing regulatory codes to product specific requirements , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[19]  Gregory Zoughbi,et al.  Modeling safety and airworthiness (RTCA DO-178B) information: conceptual model and UML profile , 2011, Software & Systems Modeling.

[20]  Olly Gotel,et al.  Out of the labyrinth: Leveraging other disciplines for requirements traceability , 2011, 2011 IEEE 19th International Requirements Engineering Conference.

[21]  Annie I. Antón,et al.  A legal cross-references taxonomy for identifying conflicting software requirements , 2011, 2011 IEEE 19th International Requirements Engineering Conference.

[22]  Jane Cleland-Huang,et al.  On-demand feature recommendations derived from mining public product descriptions , 2011, 2011 33rd International Conference on Software Engineering (ICSE).

[23]  Yang Li,et al.  A domain specific requirements model for scientific computing: NIER track , 2011, 2011 33rd International Conference on Software Engineering (ICSE).

[24]  Bashar Nuseibeh,et al.  Unknown knowns: Tacit knowledge in requirements engineering , 2011, RE.

[25]  Mehrdad Sabetzadeh,et al.  A Model-Driven Engineering Approach to Support the Verification of Compliance to Safety Standards , 2011, 2011 IEEE 22nd International Symposium on Software Reliability Engineering.

[26]  Mark Rouncefield,et al.  Model-driven engineering practices in industry , 2011, 2011 33rd International Conference on Software Engineering (ICSE).

[27]  John C. Grundy,et al.  Improving automated documentation to code traceability by combining retrieval techniques , 2011, 2011 26th IEEE/ACM International Conference on Automated Software Engineering (ASE 2011).

[28]  Daniel Amyot,et al.  User Requirements Notation: The First Ten Years, The Next Ten Years (Invited Paper) , 2011, J. Softw..

[29]  Patrick Mäder,et al.  Trace Queries for Safety Requirements in High Assurance Systems , 2012, REFSQ.

[30]  Nan Niu,et al.  Enhancing candidate link generation for requirements tracing: The cluster hypothesis revisited , 2012, 2012 20th IEEE International Requirements Engineering Conference (RE).

[31]  Benoit Baudry,et al.  Toward multilevel textual requirements traceability using model-driven engineering and information retrieval , 2012, 2012 Second IEEE International Workshop on Model-Driven Requirements Engineering (MoDRE).

[32]  Travis D. Breaux,et al.  Reconciling multi-jurisdictional legal requirements: A case study in requirements water marking , 2012, 2012 20th IEEE International Requirements Engineering Conference (RE).

[33]  Jane Cleland-Huang,et al.  A tactic-centric approach for automating traceability of quality concerns , 2012, 2012 34th International Conference on Software Engineering (ICSE).

[34]  Annie I. Antón,et al.  Managing changing compliance requirements by predicting regulatory evolution , 2012, 2012 20th IEEE International Requirements Engineering Conference (RE).

[35]  Benoit Baudry,et al.  Defining and retrieving themes in nuclear regulations , 2012, 2012 Fifth IEEE International Workshop on Requirements Engineering and Law (RELAW).

[36]  Jose Luis de la Vara,et al.  SafetyMet: A Metamodel for Safety Standards , 2013, MoDELS.

[37]  David Lo,et al.  Automatic recommendation of API methods from feature requests , 2013, 2013 28th IEEE/ACM International Conference on Automated Software Engineering (ASE).