Defining and retrieving themes in nuclear regulations

Safety systems in nuclear industry must conform to an increasing set of regulatory requirements. These requirements are scattered throughout multiple documents expressing different levels of requirements or different kinds of requirements. Consequently, when licensees want to extract the set of regulations related to a specific concern, they lack explicit traces between all regulation documents and mostly get lost while attempting to compare two different regulatory corpora. This paper presents the regulatory landscape in the context of digital Instrumentation and Command systems in nuclear power plants. To cope with this complexity, we define and discuss challenges toward an approach based on information retrieval techniques to first narrow the regulatory research space into themes and then assist the recovery of these traceability links.

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

[2]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

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

[4]  Jane Cleland-Huang,et al.  Clustering support for automated tracing , 2007, ASE '07.

[5]  Travis D. Breaux,et al.  Comparing requirements from multiple jurisdictions , 2011, 2011 Fourth International Workshop on Requirements Engineering and Law.

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

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

[8]  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.

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

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

[11]  A. Antón,et al.  A Systematic Method for Acquiring Regulatory Requirements : A Frame-Based Approach , 2007 .

[12]  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.

[13]  Gerard Salton,et al.  Automatic Text Processing: The Transformation, Analysis, and Retrieval of Information by Computer , 1989 .

[14]  Annie I. Antón,et al.  Towards Regulatory Compliance: Extracting Rights and Obligations to Align Requirements with Regulations , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

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

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

[17]  Siobhán Clarke,et al.  Theme: an approach for aspect-oriented analysis and design , 2004, Proceedings. 26th International Conference on Software Engineering.

[18]  Jane Cleland-Huang,et al.  Towards mining replacement queries for hard-to-retrieve traces , 2010, ASE.

[19]  Jane Huffman Hayes,et al.  Advancing candidate link generation for requirements tracing: the study of methods , 2006, IEEE Transactions on Software Engineering.

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

[21]  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.

[22]  Benoit Baudry,et al.  Formalizing standards and regulations variability in longlife projects. A challenge for Model-driven engineering , 2011, 2011 Model-Driven Requirements Engineering Workshop.

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

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