software requirements for oiml r91
Download
Skip this Video
Download Presentation
Software requirements for OIML R91

Loading in 2 Seconds...

play fullscreen
1 / 13

Software requirements for OIML R91 - PowerPoint PPT Presentation


  • 320 Views
  • Uploaded on

Software requirements for OIML R91. Roman Flegar Metrology Institute of the Republic of Slovenia. Agenda. Overview of development Basic rule for software requirements Goals Speed meter building blocks Software role Overview of requirements. Overview of development.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Software requirements for OIML R91' - radley


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
software requirements for oiml r91

Software requirements for OIML R91

Roman Flegar

Metrology Institute of the Republic of Slovenia

agenda
Agenda
  • Overview of development
  • Basic rule for software requirements
  • Goals
  • Speed meter building blocks
  • Software role
  • Overview of requirements
overview of development
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]
basic rule regarding software requirements
Basic rule regarding software requirements

Mechanics = Electronics = Software

  • Same functionality or requirement can be implemented or fulfilled on different technological bases.
goals
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
speed meter building blocks
km/h

foto

foto

Speed meter – building blocks

Remote access unit

Display

unit

Evidence

unit

Sensor unit

Decision unit

Storage unit

km/h

Offencerecord

foto

km/h

role of the software
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, ….
list of requirements
List of requirements
  • Five basic software requirements groups:
    • Software identification [OIML D 31: 5.1.1]
    • Correctness of algorithms and functions [OIML D 31: 5.1.2]
    • Software protection [OIML D 31: 5.1.3]
    • Support of hardware features [OIML D 31: 5.1.4]
    • Requirements specific for configuration [OIML D 31: 5.2]
more details
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]
more details1
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]
even more details
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]
ad