1 / 14

Functional specification: the transaction log Pre-sessional consultations on registries

Functional specification: the transaction log Pre-sessional consultations on registries 2 June 2003 Bonn, Germany. Andrew Howard UNFCCC secretariat www.unfccc.int ahoward@unfccc.int. Scope. Development stages Interaction processes for registries and the transaction log

sanura
Download Presentation

Functional specification: the transaction log Pre-sessional consultations on registries

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Functional specification:the transaction log Pre-sessional consultations on registries 2 June 2003 Bonn, Germany Andrew Howard UNFCCC secretariat www.unfccc.int ahoward@unfccc.int

  2. Scope • Development stages • Interaction processes for registries and the transaction log • Introduce the functional specification • Map the specification against COP decisions • Indicate necessary refinements in the specification

  3. The transaction log Verifies the validity of transactions • Issuance of units • Transfer and acquisition of units between registries • Cancellation of units (not used for compliance) • Retirement of units (used for compliance) • Carry-over of ERUs, CERs and AAUs • Independent checks of proposed transactions • Integrated in electronic communications between registries • Ensures the integrity of transactions before completion

  4. Requirements contained in decision 19.CP.7 Data exchange standardin decision 24/CP.8 The role ofthe transaction log COP 7 Functional specifications How the transaction log is to exchange data COP 8 Technical specifications Detailed requirements the system is to fulfill Current Detail on how the systemis to work technically Construct, test, roll-out, operate, maintain Dec 2003 Construct the full transaction log to meet requirements By Dec 2004 Transaction log development stages

  5. Interaction processesRegistries and the transaction log Transaction log checks against • Reference data • Data format • Holdings data • Validity rules Issuance of AAUs, RMUs, CERs • Results • Issued units • Units removedfrom accounts • Units addedto accounts • Unitscarried-over • Logged data • Inconsistenciesdiscovered Conversion (ERU issuance) External transfers Internal transfers (cancellation) Internal transfers (retirement) Carry-over Reconciliation of data • Registry inputs • Transactions • Base data • Unit choice • Account choice • Reconciliation • Holdings data • Entity data

  6. Purpose of the functional specification To translate COP decisions into technical terms To guide the later technical specification and construction This is done through identifying Key requirements that the transaction log is to fulfil Mandatory constraints on how the requirements are fulfilled Acceptance criteria for non-mandatory aspects Written in technical terms for a technical audience More requirements under the data exchange standards Read in conjunction with the glossary!

  7. 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 Functional requirements Requirements that are directly related to the log’s functionality Functional specification Non-functional requirements Requirements that are not directly related to functionality General constraints General boundaries that the log must stay within Documentation requirements Documents to support users and the operator Interfaces Defines the interfaces that must be supported by the log

  8. Automated checks(functional requirements)

  9. Transaction log actions(functional requirements)

  10. Logging data for audit trails(functional requirements)

  11. Non-functional requirements

  12. General constraints

  13. Interfaces

  14. Further refinements • Improve contextual information • Improve overview of validity rules • Separate format rules from transaction validity • Clarify relation to data exchange standards

More Related