TG MTS Introduction

From Wikicap - European Commission

Go up to the main TG MTS

Release notes - July 2019

There are no changes in the MTS methodology and workflow, but in the number of executive tests (to accomodate Art. 32(2)(b) of R1307/2013). All edits are highlighted in Maroon colour.

  • A set of executable test is introduced in Table 1 to test the model properties in relation to the eligible non-agricultural land cover (Art. 32(2)(b) of R1307/2013) The total number of executable test cases is changed to 47
  • The name of the abstract test “codeListEnumerationCompleteness” is changed to “extendedCodeList” for consistency with the XML schema of the MTS log.
  • Section 6.1: Footnote is added that INSPIRE metadata technical guidelines (INSPIRE Metadata Drafting Team 2013) was updated with the new version from 2017 (INSPIRE MIG subgroup for action MIWP-8 2017), but not yet implemented in the MTS.
  • Links to LPIS registry were updated
  • The alternative delivery of MTS-log as excel worksheet has been abolished. Section 8.3 deleted.


1.1 Background

This document presents the technical guidance on the Model Test Suite (MTS) for the Land Parcel Identification System.

This TG MTS is the successor of the 2010 ATS; the main differences with its predecessor are:

  • Implementation decisions and choices are targeted in an explicit and structured TG IXIT.
  • The LCM has been upgraded to incorporate the requirements of the 2013 CAP reform. This introduced a number conceptual elements (e.g. relating to EFA, differentiation of agriculture land), which, if not in scope of the annual data assessment, are ignored for this MTS.
  • With the introduction of structured upkeep reporting in ETS v6.0, feature metadata elements have been added
  • The testing environment has migrated from worksheet to a GI exchange environment. Despite the risk associated with redundancy, the worksheet is kept as an alternative.
  • Relevant system metadata has been introduced, referencing to selected elements of the INSPIRE implementing rules on metadata and orthoimagery.

1.2 Scope

The Model Test Suite serves to document every individual LPIS implementation so that it can correctly perform and report the data value testing procedures of the annual quality assessment. It is therefore an essential part of the LPIS QA framework.

The MTS, as a TG document, covers three distinct aspects of the LPIS implementation.

  • The choices made regarding source data, stakeholder role and other options implied by the CAP Regulations.
  • The data model elements that relate to relevant feature data and metadata values specified in the LCM.
  • The system metadata that relates to selected metadata of the INSPIRE implementing rule on metadata.

Under this scope, the document provides a comprehensive series of questions and/or tests, often based on conformity testing, to the answers necessary for a correct understanding of the various LPIS implementations, developed to address the common requirements in the CAP regulations and their supporting guidance documents.

For the data value aspects, this technical guidance sets up the abstract and executable test cases that identify all data elements necessary for the data quality assessment. It does so by describing the content and steps of the conformance testing process of the local LPIS implementation against the LCM.

The LPIS Core Model (LCM) has been designed considering the regulatory requirements, best practices and interoperability challenges in geographic information. The conformity testing verdict is not the objective of this TG MTS, the goal is to record a common and complete description, as required for the LPIS QA reporting and screening.

The modelling technique used by TG MTS is two tiered:

  • It defines a standardized Abstract Tests Suite (ATS) for testing an individual application schema against the LCM. Such conformance can be claimed for any LPIS implementation and data set.
  • It provides input guidelines for a series of executable test cases relevant for the LPIS QA reporting, which tests the data and concentrates on such data quality elements as completeness, thematic and temporal accuracy.

1.3 Terms and definitions

Term Definition (ISO/TC211 2000)
abstract test suite (ATS) Set of abstract test cases specifying all the requirements to be satisfied for conformance.
abstract test case Generalized test for a particular requirement. NOTE. An abstract test case is a formal basis for deriving executable test cases. One or more test purposes are encapsulated in the abstract test case. An abstract test case is independent of both the implementation and the values. It should be complete in the sense that it is sufficient to enable a test verdict to be assigned unambiguously to each potentially observable test outcome (i.e. sequence of test events) application schema conceptual schema for data required for one or more applications [ISO19101].
basic test Initial capability test intended to identify clear cases of non-conformance.
capability test Test designed to determine whether an Implementation Under Test (IUT) conforms to a particular characteristic of an International Standard as described in the test purpose.
conformance Fulfillment of specified requirements.
conformance testing Testing of a product to determine the extent to which the product is a conforming implementation.
conformance test report summary of the conformance to core elements as well as all the details of the testing that supports the given overall summary conforming.
implementation Implementation which satisfies the requirements.
executable test case specific test of an implementation to meet particular requirements. NOTE Instantiation of an abstract test case with values.
executable tests suite (ETS) Set of executable test cases.
feature Abstraction of real world phenomena [ISO 19101].

EXAMPLE. The phenomenon named ‘Eiffel Tower’ may be classified with other similar phenomena into a feature type ‘tower’.

feature association Relationship that links instances of one feature type with instances of the same or a different feature type.
feature attribute characteristic/properties of a feature
feature catalog Catalog containing definitions and descriptions of the feature types, feature attributes, and feature associations occurring in one or more sets of geographic data, together with any feature operations that may be applied.
non-conformance Failure to fulfill one or more specified requirements.

1.4 Abbreviations

Abbreviation Definition
MTS Model Test Suite
ATS Abstract Test Suite
ETS Executable Test Suite
IUT Implementation Under Test
IXIT Implementation eXtra Information for Testing
ICS Implementation Conformance Statement
SUT System Under Test
CAP Common Agricultural Policy
IACS Integrated Administration and Control System
MS Member State
LPIS Land Parcel Identification System
LCM LPIS Core Model
MBT Model Based Testing
UML Model
XML Unified Modelling Language
XSD Extensible Markup Language
GIS Geographic Information System
DB Data base
RDBMS Relational Database Management System
QAF Quality Assessment Framework
TG Technical Guidance
GDB Geographical Data Base
GUID Globally Unique IDentifier

1.5 Related documents


Go up to the main TG MTS page

Retrieved from "https://marswiki.jrc.ec.europa.eu/wikicap/index.php?title=TG_MTS_Introduction&oldid=1600"