Formalizing standards and regulations variability in longlife projects.

1. Formalizing standards and regulations variability in longlife projects. A challenge for Model-Driven Engineering Nicolas Sannier* **, Benoît Baudry** and Thuy Nguyen* * EDF R&D STEP P1A – 6 Quai Watier BP49 78401 Chatou Cedex France ** Inria Rennes Bretagne Atlantique – Campus de Beaulieu 35042 Rennes Cedex France

2. Standards in recent EDF projects • Software in systems important to safety Sannier, Baudry & Nguyen – Formalizing standards and regulations variability

3. Lessons to learn • This recent history shows the need: • To follow standards and regulations evolutions • To take into account the different possible interpretations of the same document • To Know the gap between different practices • Many actors over decades • From different backgrounds and with different concerns • Textual documents as the most common communication vector • That share only partial expertise on the project Sannier, Baudry & Nguyen – Formalizing standards and regulations variability

4. Two illustrating examplesIEC 60880-2001 standard • 6.2 Self-supervision 6.2.AThe software of the computer-based system shall supervise the hardware during operation within specified time intervalsand the software behaviour(A.2.2). This is considered to be a primary factor in achieving high overall system reliability. 6.2.BThose parts of the memory that contain code or invariable data shall be monitored to detect unintended changes. 6.2.CThe self-supervision should be able to detect to the extent practicable: - Random failure of hardware components; - Erroneous behavior of software (e.g. deviations from specified software processing and operating conditions or data corruption); - Erroneous data transmission between different processing units. 6.2.DIf a failure is detected by the software during plant operation, the software shall take appropriate and timely response. Those shall be implemented according to the system reactions required by the specification and to IEC61513 system design rules. This may require giving due consideration to avoiding spurious actuation. 6.2.ESelf‑supervisionshallnotadversely affect the intended system functions. 6.2.FIt should be possible to automatically collect all useful diagnostic information arising from software self-supervision. • About Partitioning,definition, reference, information, scope, composition, characterization. Sannier, Baudry & Nguyen – Formalizing standards and regulations variability

5. Two illustrating examplesEDF CSCT document • Standards and regulations used/applied in: • As references in multiple documents • Scope: All relevant components in all applicable contexts • Determined using human expertise • With a high level of interpretation Sannier, Baudry & Nguyen – Formalizing standards and regulations variability

6. Challenges • A change of perspective for both industry and research • A jump from document-centric to MBSE and further more MDE • Knowledge-driven instead of development-driven • Future works: • Propose a DSML to handle standards variability and knowledge management around practice • Build this EDF’s knowledge model w.r.t this DSML • Two working tracks: • Modeling practices variability • Enhance standards interpretation traceability questions Sannier, Baudry & Nguyen – Formalizing standards and regulations variability

7. Where to go Sannier, Baudry & Nguyen – Formalizing standards and regulations variability

8. Requirements variability and traceability • Elements of variability • At the documentation level and at the practice level • Bridging practices: Traceability to capitalize on choices and interpretations (and their consequences) • Formalizing practices dependencies • Refinements (composition, characterization, specialization …) • Interactions (reference, conflict, requires, equivalence, coverage …) • To make one project comply with several practices • Comparing practices at different levels • Know the available documentation in one context • Know the commonalities and the gaps between related documents Sannier, Baudry & Nguyen – Formalizing standards and regulations variability

9. Conclusion • A move from document-centric approaches to models • From textual artifacts to model elements • From implicit and partial knowledge to explicit referencing • From approximate links between documents to explicit relations • Being knowledge-driven instead of development-driven • Applying MDE to: • Formalize and capitalize human partial expertise • Manage, analyze and raise information on these formalized elements Sannier, Baudry & Nguyen – Formalizing standards and regulations variability

10. Thank you for your attention Questions? Discussions? Ideas? {nicolas.sannier, benoit.baudry}@inria.fr {nicolas.sannier, n.thuy}@edf.fr