Conformance assessment

Last updated:  JUNE 14th, 2019

Assessing conformance to the specification.


Status: Draft resulting from 2019-05-23 SSCONE F2F

Good to know

Conformance to the EUROCONTROL Specification for SWIM Service Description is through self-assessment.

Conformance to the specification

The specification contains a conformity checklist. It sets out whether conformance with the requirement is "mandatory", "recommended" or "mandatory when the conditions apply".

The organisation or person responsible for the service description is expected to

  • assess whether all requirements are fulfilled 
  • capture the result in a conformance matrix
  • express the overall conformance to the specification

It is then possible to attach the results of this conformance assessment to the service description as evidence of conformance.

Conformance to a requirement

To conform with a requirement, the entire requirement has to be satisfied. This includes the need to perform verification. Each requirement contains a verification statement on the quality characteristics to be assessed when inspecting a service description with regards to the requirement. Each requirement indicates the verification method to cover the following characteristics:  completenessconsistency and correctness.

Support

Resource - Conformance assessment report

The Conformance assessment report is a resource supporting conformance assessment.

Example of use: Conformance assessment - Donlon example

Terminology - Conformance vs. Compliance

Conformance is the voluntary adherence to a standard, rule, specification, requirement, design, process or practice.

It should not be confused with compliance which is the forced adherence to a law, regulation, rule, process or practice.

Justification for the confusion - If someone mandates you meet the requirements of a standard or test method then conformance becomes compliance (i.e. your conformity is required in order for you to comply).

Excerpts from the specification

1.5 Conventions [+]

1.5 Conventions

The following conventions are used in this EUROCONTROL specification:

  • shall’-  indicates a requirement that must be implemented to provide conformity with this specification;
  • should’ -  indicates a requirement that is recommended to achieve the best possible implementation of this specification; and
  • may’ -  indicates an option.

Annex B to this specification provides the conformity checklist indicating, per requirement, the level
of implementation to be achieved – see tables 4 and 5.

2. Conformance [+]

2. Conformance
The conformity checklist table is available in Annex B. It is provided in support of assessing conformance with this specification.

ANNEX B – Conformity Checklist [+]

ANNEX B – Conformity Checklist
This annex summarises the requirements to be met when assessing conformity to this specification.

Table 5 lists each requirement in the specification using its identifier and title. It then states the level of implementation to be achieved (see Table 4). In some cases, the implementation is conditional which means that the requirement is to be implemented when the condition applies.

Table 4 – Level of implementation [+]

Level of Implementation

Operative verb used in the requirement

M = Mandatory

shall

R = Recommended

should

O = Optional

may

Table 5 – Conformity checklist [+]

Identifier

Title

Level of Implementation

 

General Requirements

 

SWIM-SERV-001

Service description coverage

M

SWIM-SERV-002

Service description language

M

SWIM-SERV-003

Define abbreviations and acronyms

M

SWIM-SERV-004

Use standard abbreviations and acronyms

R

SWIM-SERV-005

Service description identification

M

SWIM-SERV-006

Service identification

M

SWIM-SERV-007

Service abstract

M

SWIM-SERV-008

Service provider

M

SWIM-SERV-009

Service categories

M

SWIM-SERV-010

Service standard reference

M

SWIM-SERV-011

Operational needs

M

SWIM-SERV-012

Service functionality

M

SWIM-SERV-013

Service access and use conditions

M

SWIM-SERV-014

Quality of service

M

SWIM-SERV-015

Technical constraint

M Conditional

 

Service Interface Requirements

 

SWIM-SERV-016

Service interfaces

M

SWIM-SERV-017

Message exchange pattern

M

SWIM-SERV-018

SWIM TI Profile and interface bindings

M

SWIM-SERV-019

Service interface protocols and data format

M

SWIM-SERV-020

Machine-readable service interface definition

M Conditional

SWIM-SERV-021

Service operations

M

SWIM-SERV-022

Information definition

M

SWIM-SERV-023

AIRM conformance

M

SWIM-SERV-024

Filter capabilities

M

SWIM-SERV-025

Service behaviour

M

SWIM-SERV-026

Model view

R

 

Other Requirements

 

SWIM-SERV-027

Service validation

M

SWIM-SERV-028

Service monitoring

M Conditional

SWIM-SERV-029

Examples of code

R

Content