150 likes | 256 Vues
This document outlines the functional specifications for data exchange standards related to registry systems, guiding their development based on COP decisions. It addresses crucial aspects like data formats, transaction logs, and the communication structure between sender and receiver systems. The specification aims to ensure accuracy, harmonization, and auditability, serving as a bridge between COP mandates and technical requirements. Key elements discussed include general design requirements, functional and non-functional requirements, and the implications for registry developers.
E N D
Functional specification:data exchange standards Pre-sessional consultations on registries 2 June 2003 Bonn, Germany Andrew Howard UNFCCC secretariat www.unfccc.int ahoward@unfccc.int
Scope • Development stages • Introduce the functional specification • Map the specification against COP decisions • Implications for registry developers • Indicate necessary refinements in the specification
Registry systems and data exchange National registry (of an Annex I Party) CDM registry (for Non-Annex I Parties) Sender/receiver Sender/receiver Communication via the data exchange standards Sender/receiver Communications hub Autochecks Transaction log
The data exchange standards Transactions are enacted through data exchange Standards ensure sufficient harmonization • Data formats for data exchange • Sender/receiver units of registries and the transaction log • Behind-the-scenes to ensure accuracy and auditability
Development mandated in decision 19.CP.7 Data exchange standardin decision 24/CP.8 COP 7 Functional specifications General design requirements COP 8 Technical specifications Requirements on what the standards are to mandate Current Detail on how they are to be implemented Dec 2003 Data exchange standards development stages
Purpose of the functional specification To translate COP decisions into technical terms To guide the later technical specification of the standards This is done through identifying Key requirements that the standards are to mandate Mandatory constraints on how the requirements are fulfilled Acceptance criteria for non-mandatory aspects Written in technical terms for a technical audience Read in conjunction with the glossary!
Structure of the document Introduction Outline of the purpose, scope and derivation documents Assumptions What is to hold true for the functional specification to be valid Data transfer format Functional and non-functional requirements Functional specification Registries Functional and non-functional requirements Transaction log Functional and non-functional requirements General constraints General boundaries that the standards must stay within Interfaces Defines the interfaces that must be supported by the standards