BS EN ISO 16410-1:2017

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviated terms
5 Test suite structure
Annex A (normative) - Test purposes (TP) for Front End
Annex B (normative) - Test purposes (TP) for Back End
Annex C (normative) - Data structures
Annex D (normative) - PCTR for Front End
Annex E (normative) - PCTR for Back End
Bibliography

Gives a suite of tests in order to assess compliance of the Front End and Back End behaviours in relation to the requirements in ISO 17575-3.

The ISO16410series provides a suite of tests in order to assess compliance of the Front End and Back End behaviours in relation to the requirements in ISO17575‑3 . This document contains the definition of such tests in the form of test purposes, listing the required initial conditions, references and individual steps in a structured textual manner. ISO16410‑2 contains the identical tests written in testing and test control notation version 3 (TTCN v3).

The test purposes defined in this document reflect the structural and semantic requirements stated in ISO17575‑3 .

• Presence/absence of particular data elements (see ISO17575‑3:2016, 8.5.5);

• Semantics related to various data elements, e.g.:

  • Activation of context data and handling multiple contexts (see ISO17575‑3:2016, 8.3);

  • Handling the precedence and priority levels (see ISO17575‑3:2016, 8.5.2 to 8.5.4);

  • Uniqueness of relevant data elements (see ISO17575‑3:2016, 8.5.2 to 8.5.4);

  • Correct definition of the charge objects (see ISO17575‑3:2016, 8.5.4);

• Fee calculation algorithm (see ISO17575‑3:2016, 8.5.3.7);

• Security (see ISO17575‑3:2016, 7.2).

With regard to the individual data sets and EFC attributes defined in ISO17575‑3 , the test purposes have been organized into the test suite groups, designated for the Front End and Back End respectively.

In addition to the test purposes, this document also provides proforma conformance test report templates for both the Front End and Back End test purposes and an informative statement on the usage of this document for the European electronic toll service (EETS).

For more information regarding the requirements against which the conformance is evaluated in this document, refer to ISO17575‑3 .

Testing of the following behaviours and functionalities is outside the scope of this document:

• dynamic behaviour, i.e. sequence of messages and triggering events that must be exchanged/happen to fulfil certain charging scenarios;

• profiles and business logic built on top of particular pricing schemas;

• behaviour invalid of Front End and Back End, BI test purposes are not applicable for any test purpose group (as ISO17575‑3 does not specify behaviour invalid).