1. Republic of Slovenia Ministry for economic relations and development Metrology Institute of the Republic of Slovenia Laboratory for Information Technology in Metrology Software requirements for OIML R91 Roman Flegar Metrology Institute of the Republic of Slovenia

2. Agenda Overview of development Basic rule for software requirements Goals Speed meter building blocks Software role Overview of requirements

3. Overview of development 2013 Novembar - Kickstart document 2014 January- Rewritten requirements 2014 April- Document completed Members: -Roman Flegar [roman.flegar@gov.si] -Ambler Thompson [ambler.thompson@nist.gov] -Ben van de Pavert [b.vandepavert@gatso.com] -Yin Bai [baiyin@nim.ac.cn]

4. Basic rule regarding software requirements Same functionality or requirement can be implemented or fulfilled on different technological bases.

5. Goals Simple and understandable requirements Requirements as guide for both sides: manufacturer and regulator Support future development of technology “Black box testing”: functional testing and documentation overview

6. Speed meter – building blocks Sensor unit Evidence unit Display unit Decision unit Remote access unit Storage unit foto km/h Offence record Offence record km/h foto

7. Role of the software General roles: – operating the sensor, where value of measurement is acquired, – calculating the final measurement result, based on the acquired values from sensors – displaying the result, – documenting the result with evidences, – storing of results, – transmitting of results and – securing the results against unintentional or intentional changes, ….

8. INTRODUCTION TO REQUIREMENTS

9. List of requirements Five basic software requirements groups: 1.Software identification [OIML D 31: 5.1.1] 2.Correctness of algorithms and functions [OIML D 31: 5.1.2] 3.Software protection [OIML D 31: 5.1.3] 4.Support of hardware features [OIML D 31: 5.1.4] 5.Requirements specific for configuration [OIML D 31: 5.2]

10. More details … 3. Software protection [OIML D 31: 5.1.3] – Prevention of misuse [OIML D 31: 5.1.3.1] – Fraud protection [OIML D 31: 5.1.3.2] 4.Support of hardware features [OIML D 31: 5.1.4] – Support of fault detection [OIML D 31: 5.1.4.1] – Support of durability protection [OIML D 31: 5.1.4.1]

11. More details … 4.Support of hardware features [OIML D 31: 5.1.4] – Support of fault detection [OIML D 31: 5.1.4.1] – Support of durability protection [OIML D 31: 5.1.4.1]

12. Even more details … 5. Requirements specific for configuration [OIML D 31: 5.2] – Specifying and separating relevant parts specifying interface of parts [OIML D 31: 5.2.1] – Shared indications [OIML D 31: 5.2.2] – Storage of data, transmission via communication systems [OIML D 31: 5.2.3] – Compatibility of operating system and hardware, portability [OIML D 31: 5.2.5] – Conformity of manufactured devices to the approved type [OIML D 31: 5.2.5] – Maintenance and re-configuration [OIML D 31: 5.2.6]

13. LETS GO THROUGH REQUIREMENTS…