Transcript Functional specification: the data exchange standards Andrew

Functional specification:
data exchange standards
Andrew Howard
UNFCCC secretariat
Pre-sessional consultations on registries
www.unfccc.int
[email protected]
2 June 2003
Bonn, Germany
1
Scope
• Development stages
• Introduce the functional specification
• Map the specification against COP decisions
• Implications for registry developers
• Indicate necessary refinements in the specification
2
Registry systems and data exchange
National
registry
CDM
registry
(of an Annex I Party)
(for Non-Annex I Parties)
Sender/receiver
Communication via the
data exchange standards
Sender/receiver
Sender/receiver
Communications hub
Autochecks
Transaction log
3
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
4
Data exchange standards development stages
COP 7
COP 8
Current
Dec 2003
Development mandated in
decision 19.CP.7
Data exchange standard
in decision 24/CP.8
Functional specifications
Technical specifications
General design
requirements
Requirements on what the
standards are to mandate
Detail on how they are
to be implemented
5
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!
6
Structure of the document
Introduction
Outline of the purpose, scope and derivation documents
Functional specification
Assumptions
What is to hold true for the functional specification to be valid
Data transfer format
Functional and non-functional requirements
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
7
Registries
(functional requirements)
COP decision
Requirement
Reference
Unique numbers
Serial number elements
Transaction number elements
Account number elements
Message identification
4.1.1
4.1.2
4.1.3
4.1.8
Full audit trail
Logging transactions
Logging messages and notifications
Record retention
4.1.4
4.1.5
4.1.6
Compatible messages Conform to transaction log sequences
4.1.9
Communication hub
All communication through the hub
4.1.11
Central authentication Authentication info from transaction log 4.1.12
Stop discrepancies
If discrepancy, terminate transaction
Provide reference data to the log
4.1.10
4.1.7
Reconciliation
Provide holdings and entity data to log
Resolve through manual adjustments
4.1.13
4.1.14
8
Registries
(non-functional requirements)
Topic
Requirement
Reference
Data
Accuracy of data
4.2.1
Integrity of data
4.2.2
Discrepancy prevention
4.2.9
Efficient processing of data
4.2.3
System testing
4.2.4
“Minimum” downtime
4.2.5
Protect against unauthorized access
4.2.6
Protect from attack
4.1.7
Safeguards, recovery of data/service
4.1.8
Performance
Safety
9
Transaction log
(functional requirements)
COP decision
Requirement
Reference
Full audit trail
Logging transactions
5.1.2
Logging messages and notifications
5.1.3
Logging users of the transaction log
5.1.4
Record retention
5.1.7
Provide communications hub
5.1.8
Communication hub
Central authentication Provide authentication information
5.1.1
Transaction finality
Points in sequences to be agreed
5.1.9
Reconciliation
Check holdings and entity data
5.1.10
Resolve through manual adjustments
5.1.11
10
Transaction log
(non-functional requirements)
Topic
Requirement
Reference
Data
Accuracy of data
5.2.1
Integrity of data
5.2.2
Efficient processing of data
5.2.3
System testing
5.2.4
“Minimum” downtime
5.2.5
Protect against unauthorized access
5.2.6
Protect from attack
5.1.7
Safeguards, recovery of data/service
5.1.8
Performance
Safety
11
Data transfer format
(functional requirements)
COP decision
Requirement
Reference
Transaction info
Number
Transaction type
Transaction record
Stage information
Status information
Time of creation
Destination registry
Information on authorized entities
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.8
3.1.11
3.1.12
Indicate discrepancy
Discrepancy information
3.1.6
Message and notification information
Authentication information
3.1.7
3.1.9
Free-text content
3.1.10
12
Data transfer format
(non-functional requirements)
Topic
Requirement
Flexibility
Data format additions
Languages
Support non-Roman characters on any
operating system
Reference
13
General constraints
COP decision
Independence
General constraint
Reference
Reliable data stream
6.1
Industry standards preferred
6.2
Product and vendor independence
6.3
14
Interfaces
Connections
Content
Transfer
Requirement
Reference
Awareness of client connection state
7.1.7
Auto-logout timer
7.1.8
Send data/messages
7.1.5
Receive data/messages
7.1.6
Accuracy
7.1.2
Confidentiality
7.1.3
Security
7.1.4
15