10 December, 2013 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: DPM Meta model CWA1Page 1.

Slides:



Advertisements
Similar presentations
XBRL Versioning Committee of European Banking Supervisors XBRL Network Vice-Chair VWG Katrin Schmehl Amsterdam, th European Banking Supervisors.
Advertisements

Issues of concern at COREP ON 15. September 2004 The common framework should: be flexible enough so that countries are able to choose the level of details.
26 September 2012 Katrin Heinze CEN/WS XBRL Kick-off meeting CWA1 deliverables 1CWA1.
Profiles Construction Eclipse ECESIS Project Construction of Complex UML Profiles UPM ETSI Telecomunicación Ciudad Universitaria s/n Madrid 28040,
SDMX in the Vietnam Ministry of Planning and Investment - A Data Model to Manage Metadata and Data ETV2 Component 5 – Facilitating better decision-making.
DPM ARCHITECT FOR XBRL XBRL taxonomy editor aimed at BUSINESS USERS Based on the DPM approach and DPM XBRL Architecture Currently on its last stage of.
Filing rules and extensions of EBA/EIOPA taxonomies
Peter Neudorfer Managing the quality of the ECB’s enhanced ‘Register of Institutions and Affiliates Database‘ (RIAD) Meeting of the Group of Experts on.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.
Reducing the burden of building taxonomies
Formal Techniques in Software Engineering Universiteit AntwerpenIntroduction 1.1 Formal Techniques in Software Engineering 3de BAC Informatica Chapter.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Detail Design Extending UML and Object Design. Object Design.
Introduction to UML Visual modeling Models and its importance
Requirements Analysis Concepts & Principles
Data Management: Documentation & Metadata Types of Documentation.
Foundations This chapter lays down the fundamental ideas and choices on which our approach is based. First, it identifies the needs of architects in the.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
18 June, 2013 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: European Filing Rules Data Point Meta Model Data Point Methodology Guidance European Taxonomy.
Background Data validation, a critical issue for the E.S.S.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
12 December, 2012 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: European Filing Rules CWA1Page 1.
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
1 CIM User Group Conference Call december 8th 2005 Using UN/CEFACT Core Component methodology for EIC/TC 57 works and CIM Jean-Luc SANSON Electrical Network.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Ontology Development Kenneth Baclawski Northeastern University Harvard Medical School.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
4 April 2007METIS Work Session1 Metadata Standards and Their Support of Data Management Needs Daniel W. Gillman Bureau of Labor Statistics Paul Johanis.
Introduction to MDA (Model Driven Architecture) CYT.
1 Sujan Kukreja, B 10-7 German Banking Supervisory IT Systems Overview, Architecture, Challenges Katrin Heinze.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Definition of a taxonomy “System for naming and organizing things into groups that share similar characteristics” Taxonomy Architectures Applications.
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
12 December, 2012 Aitor Azcoaga, EIOIPA CEN/WS XBRL CWA3: Standardized roll-out package CWA3Page 1.
Modeling Issues for Data Warehouses CMPT 455/826 - Week 7, Day 1 (based on Trujollo) Sept-Dec 2009 – w7d11.
20 February, 2012 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: European Filing Rules CWA1: Data Point Meta Model CWA1Page 1.
Metadata Common Vocabulary a journey from a glossary to an ontology of statistical metadata, and back Sérgio Bacelar
TMF - Terminological Markup Framework Laurent Romary Laboratoire LORIA (CNRS, INRIA, Universités de Nancy) ISO meeting London, 14 August 2000.
Of 33 lecture 1: introduction. of 33 the semantic web vision today’s web (1) web content – for human consumption (no structural information) people search.
Eurostat SDMX and Global Standardisation Marco Pellegrino Eurostat, Statistical Office of the European Union Bangkok,
Eurostat 4. SDMX: Main objects for data exchange 1 Raynald Palmieri Eurostat Unit B5: “Central data and metadata services” SDMX Basics course, October.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Winter 2007SEG2101 Chapter 31 Chapter 3 Requirements Specifications.
UML Profile BY RAEF MOUSHEIMISH. Background Model is a description of system or part of a system using well- defined language. Model is a description.
Statistical Data and Metadata Exchange SDMX Metadata Common Vocabulary Status of project and issues ( ) Marco Pellegrino Eurostat
Chapter 9 Architectural Design. Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a software.
Defects of UML Yang Yichuan. For the Presentation Something you know Instead of lots of new stuff. Cases Instead of Concepts. Methodology instead of the.
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
SysML v2 Formalism: Requirements & Benefits
CWA3 Standardized roll-out package Part 2: XBRL Handbook for Declarers
Business Process Measures
Abstract descriptions of systems whose requirements are being analysed
SDMX Information Model
Software Measurement Process ISO/IEC
System models October 5, 2005.
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
The implementation of a more efficient way of collecting data
2. An overview of SDMX (What is SDMX? Part I)
2. An overview of SDMX (What is SDMX? Part I)
NewCronos what policy and architecture contents consultation evolution
Metadata Framework as the basis for Metadata-driven Architecture
Chapter 9 Architectural Design.
CEN/WS XBRL Kick-off meeting
Objective of this presentation
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Software Architecture & Design
Presentation transcript:

10 December, 2013 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: DPM Meta model CWA1Page 1

DPM representation Definition of a Data Point Model  DPM is a dictionary of business concepts and their properties  used in tables (explicitly indicated in annotation)  identifying the content of every data point and  its relation to other data points. Data Point Model represented in Developed by: EIOPA EBA

Identified obstacles with DPMs Background for the development  ambiguity in the understanding of the concept of a Data Point Model  missing rule set to be followed in the process of Data Point modelling  different constraints depending on the field of application  missing abstraction layer to ease the understanding for IT experts  missing description of the relations between the different components of a Data Point Model

Objectives: DPM Meta model Objectives  represent the requirements of European reporting frameworks in a data model  link the business requirements with the technical transfer format  describes the rules to be recognised in the process of modelling The Data Point Meta Model should provide  (1) the model components for the creation of a formal model on sets of data points for European supervisory reporting frameworks,  (2) rules on how to combine these components and  (3) the meaning (semantic) of the components and their relations.  Similar to a model construction kit for toys it provides the modelling principles with all characteristics available for use by the modeller.

Multidimensional terminology 5 List of Countries France Spain Austria Belgium Germany Italy Dimension Total European countries Other than European countries Japan USA Hierarchy Domain

Multidimensional terminology - samples Domain A Domain is a classification system to categorize items that share a common semantic identity. A Domain provides therefore an unambiguous collection of items in a value range. The items of a Domain can have a definite, and therefore countable, number of items, or an infinite number of elements that follow a specific (syntax) pattern. Dimension A Dimension is a data set to one characteristic area which is composed of individual and non-overlapping data elements. In the context of a data point model Dimensions are used to group information in a meaningful way. Dimensions are used to define "by" conditions and provide structured information to describe a data point in detail. 6

Concept of modelling 7 Objekt system Reality Model system model representation Modeller M etaphor construction interpretation modelling objectives Meta model modelling approach

Process of DPM modelling

Levels of meta modelling 9 Meta model Meta meta model Modelling language Meta modelling language conforms to represented by described by conforms to defines notation Data Point Model

UML Meta model for DPM Decisions taken on the modelling approach for the DPM Meta model Data Point Meta model UML Model UML + OCL UML conforms to represented by described by conforms to defines notation Data Point Model OCL (Object Constraint Language) is a formal language for specifications. It refers to an UML model to describe constraints about the objects in the model.

Perspectives of a meta model Different perspectives on the meta model  Perspectives reduce the complexity and provide views on different aspects of the object system  Perspectives needed to be consistent and complete as a whole Inconsistency Front view Side view Top view Model system Object system modelling

DPM model perspectives Perspectives on the DPM Meta Model  Structural  Versioning  Dimension Validation  Hierarchical  Presentation

Constraints on the DPM modelling Definition of constraints  General constraints on DPMs  Data warehouse specific constraints  European XBRL Taxonomy specific constraints

UML Meta model for DPM The DPM Meta Model  eases the understanding of DPMs for IT experts by using the standard modelling language UML,  reduces the complexity of DPMs by showing only the relevant aspects,  provides syntax and semantics to ease the automation of IT tasks  like generating data formats for the reporting process or  validation checks on basis of the constraints defined,  enables the derivation of a database design (relational as well as multidimensional).

Model-2-Model transformation 15 Explanation of the correspondence of model graphs via graph transformation by using the Triple Graph Grammar  Here: mapping between DPM and XBRL Domain graph (DPM) Domain graph XBRL correspondence graph

Model-2-Model transformation 16 Domain graph (DPM) correspondence graphs Domain graph (SDMX) Future fields of application  Here: mapping between DPM and SDMX

Further CWA1 deliverables 17 represented by Data Point Model XBRL taxonomy transformed by European reporting frameworks XBRL instances conforms to European XBRL Taxonomy Architecture Guidelines for data point modelling European data point methodology European Filing Rules

Thanks for your attention Page 18 Comments or questions? CWA1