Contextual Metadata - the FRIS modelling context - euroCRIS seminar 2013.

Slides:



Advertisements
Similar presentations
SDMX in the Vietnam Ministry of Planning and Investment - A Data Model to Manage Metadata and Data ETV2 Component 5 – Facilitating better decision-making.
Advertisements

ARCHITECTURE FRAMEWORKS IN COMPLEX ENVIRONMENTS SIMPLIFYING THE MYSTERY OF I.T. SYSTEMS IN SMALL AND LARGE ENTERPRISES JOHN HODGSON, I.T. ARCHITECT.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Software Engineering September 12, 2001 Capturing.
e-Framework Components and Responsibilities.
Overview of OASIS SOA Reference Architecture Foundation (SOA-RAF)
Basic guidelines for the creation of a DW Create corporate sponsors and plan thoroughly Determine a scalable architectural framework for the DW Identify.
OASIS Reference Model for Service Oriented Architecture 1.0
Reference Models مدل های مرجع معماری.
Requirements Specification
Software Requirements
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Architectural Design Principles. Outline  Architectural level of design The design of the system in terms of components and connectors and their arrangements.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
Systems Engineering Foundations of Software Systems Integration Peter Denno, Allison Barnard Feeney Manufacturing Engineering Laboratory National Institute.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
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.
LEVERAGING THE ENTERPRISE INFORMATION ENVIRONMENT Louise Edmonds Senior Manager Information Management ACT Health.
Enterprise Architecture
10 December, 2013 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: DPM Meta model CWA1Page 1.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
Developing Enterprise Architecture
GSIM Stakeholder Interview Feedback HLG-BAS Secretariat January 2012.
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
WP.5 - DDI-SDMX Integration E.S.S. cross-cutting project on Information Models and Standards Marco Pellegrino, Denis Grofils Eurostat METIS Work Session6-8.
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
ArchiMate Authors : eSchoolink Group - ITNLU. Contents 1. What’s ArchiMate ? 2. Why ArchiMate ? 3. Main Benefits of ArchiMate 4. Layers of ArchiMate 5.
Architecture Ecosystem Foundation (AEF) RFP aesig/ Draft RFP Presentation June 2010.
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
Introduction to MDA (Model Driven Architecture) CYT.
Integrating aspects of interoperability, policy and governance FRIS: a research information infrastructure in Flanders euroCRIS Strategic Members meeting.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
SDMX Standards Relationships to ISO/IEC 11179/CMR Arofan Gregory Chris Nelson Joint UNECE/Eurostat/OECD workshop on statistical metadata (METIS): Geneva.
Interfacing Registry Systems December 2000.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
95-843: Service Oriented Architecture 1 Master of Information System Management Service Oriented Architecture Lecture 3: SOA Reference Model OASIS 2006.
1 Introduction to Software Engineering Lecture 1.
Illustrations and Answers for TDT4252 exam, June
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
1 Everyday Requirements for an Open Ontology Repository Denise Bedford Ontolog Community Panel Presentation April 3, 2008.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Week III  Recap from Last Week Review Classes Review Domain Model for EU-Bid & EU-Lease Aggregation Example (Reservation) Attribute Properties.
Object-Oriented Modeling: Static Models. Object-Oriented Modeling Model the system as interacting objects Model the system as interacting objects Match.
Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Requirement Engineering Virtusa Training Group 2004 Trainer: Ojitha Kumanayaka Duration : 1 hour.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
2.An overview of SDMX (What is SDMX? Part I) 1 Edward Cook Eurostat Unit B5: “Central data and metadata services” SDMX Basics course, October 2015.
A Mediated Approach towards Web Service Choreography Michael Stollberg, Dumitru Roman, Juan Miguel Gomez DERI – Digital Enterprise Research Institute
Achieving Semantic Interoperability at the World Bank Designing the Information Architecture and Programmatically Processing Information Denise Bedford.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Basic Concepts and Definitions
1 Chapter 2 Database Environment Pearson Education © 2009.
Software Engineering Lecture 10: System Engineering.
1 SOA Seminar Seminar on Service Oriented Architecture SOA Reference Model OASIS 2006.
Slide 1 Chapter 8 Architectural Design. Slide 2 Topics covered l System structuring l Control models l Modular decomposition l Domain-specific architectures.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures. Core Concepts Key Learning Points: This chapter will help you to answer the following questions: What are the ADM phase names.
Models of the OASIS SOA Reference Architecture Foundation Ken Laskey Chair, SOA Reference Model Technical Committee 20 March 2013.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Informatics for Scientific Data Bio-informatics and Medical Informatics Week 9 Lecture notes INF 380E: Perspectives on Information.
Data and classification governance, key to semantic interoperability of CRIS systems in inter-organizational contexts Sadia Vancauwenbergh
Requirements Analysis Requirements Engineering (CI 2323) Daniel Siahaan.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
eHealth Standards and Profiles in Action for Europe and Beyond
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Software Architecture
2. An overview of SDMX (What is SDMX? Part I)
2. An overview of SDMX (What is SDMX? Part I)
Presentation transcript:

Contextual Metadata - the FRIS modelling context - euroCRIS seminar 2013

Flemish government | Department of Economy, Science and Innovation Information Modeling in the FRIS context The project team Leen Van Campe Geert Van Grootel Kris Maison Pieter De Leenheer Research Director & Co-Founder Patrick Derde Enterprise Architect 2

Flemish government | Department of Economy, Science and Innovation Framework Impuls Financing Program for the universities Concept note on research output monitoring Goals Implementation of a management environment for integrated research information within the institutions Connectivity with the FRIS gateway infrastructure Reporting obligations Content providing FRIS Research Portal FRIS linked open data store Integration with FRIS master data service Organization, Person, Journal, Project,… 3

Flemish government | Department of Economy, Science and Innovation The ecosystem concerned Realizing integrated research information start from very different environments ranging from: Large ERP systems with integration path tot output Large ERP systems without integration path to output Individual applications for the different lines of business integrating with CRIS system Home brewed application stack flanked by output management environment Almost all output management environments are based on or implementations of repository software 4

Flemish government | Department of Economy, Science and Innovation Challenges Achieve alignment of business concept, their meaning an representation within an Institution Does the Business Concept “Person”, represent by the Business Term ”Person” have the same meaning as the Business Term “Human Being” Achieve the same alignment across institutes Have formal modeled relations between the Business Concepts, Meanings and Representation. Define the Business Concepts of concern for the FRIS ecosystem Formally model the relations between the Business Concepts and their representation at the level of the data.  connect the database schemes formally with the conceptual layer Manages all required Classifications and Code Sets Do all the above in a collaborative way Make sure the models at every level are machine readable 5

Flemish government | Department of Economy, Science and Innovation Impuls Financing Project 6 New Methodology

Flemish government | Department of Economy, Science and Innovation Principles Answering these challenges requires a modelling stack that implements the following principles Model Driven Meta Data Management Pattern Driven Meta Models Organization Specific Information Delivery 7

Flemish government | Department of Economy, Science and Innovation Model Driven Meta Data Management Statement:  Consistent management of meta data for the Flanders Research Information Space is supported by conceptual models. Rationale  Meta data is data about the data and is expressed in description elements which are visualized as labels. These labels have a meaning. In order to be consistent in the definition of the meaning of describing attributes the use of models is a powerful instrument to avoid ambiguity and redundancy. Implications  All meta data should be able to be defined by means of the model elements and the relationships between each other. 8

Flemish government | Department of Economy, Science and Innovation Pattern Driven Meta Models Statement  Models developed to define meta data will be a variation of more generic models. We call these models Patterns. Rationale  Patterns enable consistency in the development of the specific models used to manage the meta data definitions. These models are abstract, but very useful for the team that has to manage and govern the meta data the Flanders Research Information Space within a international context. Implications  A set of Patterns must be developed and governed by some key stakeholders that have extended modeling skills. These patterns are not used for communication with the different information providers.  Patterns will be modeled in ArchiMate 2.0 9

Flemish government | Department of Economy, Science and Innovation Organisation Specific Information Delivery Statement  All institutions that deliver information to FRIS can do this in their own representation. Rationale  Research Institutions have their own information systems that are the source for information sharing. EWI wants to avoid that delivery organizations need to know the technical conceptual structure of a common canonical data and information model. Implications  Organization specific delivered data must be transformed to the canonical data and/or information model.  Transformation rules must be managed on top of the meta data management 10 Principles are guiding consistent decision making.

Flemish government | Department of Economy, Science and Innovation FRIS information requirements Achieving the goals of seamless information interchange and interoperability in the FRIS context reconciling the different views on the integrated research information requires a methodological approach. Obvious needs Standardization of the interchange format is unavoidable Standard of choice: CERIF Semantic agreement Agreement and management Meaning Representation The FRIS principles rephrased Syntactic and semantic alignment is realized at the systems interface. Institutions are responsible for their semantic management and the mapping to the agreed FRIS semantics. 11

Flemish government | Department of Economy, Science and Innovation FRIS responsibilities on semantic management Development and deployment of a suitable methodology for information modeling. Design high level conceptual models Evaluate existing object models against the FRIS conceptual model Organize the mapping between the institutional models on the FRIS standard exchange model Deployment of an suitable infrastructure Collaborative management of information models Collaborative management of classification schemes and code sets Machine readable classification schemes and codes sets Machine readable information models including business rules supporting automated validation of exchanged information. Organize the management of the information models, classifications, code sets by developing suitable governance models and their implementation via workflows 12

Flemish government | Department of Economy, Science and Innovation The FRIS modeling stack The FRIS modeling stack consist essentially of standards implemented in different products dividing the stack in two layers The meta mode layer Principles, Guidelines, Governance Structures High level conceptual models Governance models Standard language: Archimate 2.0 Product of choice : BizzDesign’s Architect The information modeling layer Information models Information templates Classification schemes Codes Sets Data base scheme Business rules Governance implementation via workflows Standard: SBVR Product of choice: Collibra’s Data Governance Center 13

Flemish government | Department of Economy, Science and Innovation Patterns for Data Management and Data Governance Business Term Model Pattern The pattern is derived from the SBVR. The ‘Business Term Model Pattern’ is a means to manage the distinction between a ‘Business Term’ and what is represented by the term. Business people are expressing themselves by means of business terms which have meaning in a certain context. A‘business term’ points to a ‘business concept’ Getting grip on the ‘Business Concepts’ is essential in order to be able to manage a glossary with Business Terms. Most organizations like to have 1 business term for 1 concept and the concept of ‘business term’ and the concept of ‘Business Concept’ are than seen as the same thing. From point of view of managing business semantics we must distinguish these two fundamental different concepts. 14

Flemish government | Department of Economy, Science and Innovation Model Pattern for a Business Term 15

Flemish government | Department of Economy, Science and Innovation Definitions  Business Term  A Business Term is the name of a Business Concept. It is the representation of a Business Concept by means of a word or ‘ordered set’ of words. A Business Term is used to refer to a Business Concept and its meaning 16

Flemish government | Department of Economy, Science and Innovation Definitions  Business Concept  A Business Concept is whatever can be thought of by the business. Normally each Business Concept has an unambiguous meaning expressed by an unambiguous definition.  A Business Concept can be taxonomically classified in various sub classifications e.g. Business Object, Classification, Business Rule, Code.  A Business Concept is represented by a Business Term 17

Flemish government | Department of Economy, Science and Innovation Definitions  Business Object  A Business Object is a Business Concept, concrete or abstract, that has the capability to influence behavior of a Business System. Typical examples are Person, Organization, Project, Location, Instruction, Account, etc.  A Business Object is represented by a Business Term 18

Flemish government | Department of Economy, Science and Innovation Definitions Classification  A Classification is a Business Concept that organizes and manages business information by defining (hierarchical) structures that provide classification categories that apply to one or more Business Concepts and groups of Business Concepts that apply to multiple Business Concepts  A Classification is represented by a Business Term 19

Flemish government | Department of Economy, Science and Innovation Definitions Code  A (technical) Business Concept that is an identifier of a Business Concept.  A Code is used to 'identify' or to 'refer to' a Business Concept.  A Code is represented by a Business Term  e.g. BE identifies the concept “Belgium” 20

Flemish government | Department of Economy, Science and Innovation Definitions Business Rule A formula that defines or constrains some aspect of business. Intended to assert business structure or to control or influence the behavior of the business. Describe the operations, definitions and constraints that apply to an organization. Can apply to people, processes, corporate behavior and computing systems in an organization, and are put in place to help the organization achieve its goals. May be informal or even unwritten, writing the rules down clearly and making sure that they don't conflict is a valuable activity. When carefully managed, rules can be used to help the organization to better achieve goals, remove obstacles to market growth, reduce costly mistakes, improve communication, comply with legal requirements, and increase customer loyalty. A Business Rule is represented by a Business Term 21

Flemish government | Department of Economy, Science and Innovation Information Model Pattern The Information Model Pattern defines the generic structure  Goal:  Helps to detect the type of metadata surrounding a Business Object  A business object is a concrete or abstract thing which exists in reality and is of importance for a defined business.  In this case the business is Flanders Research Information.  The business objects we can think of are ‘Person’, ‘Organization’, ‘Project’ and ‘Publication’.  When replacing the abstract term “Business Object” by the more concrete terms ‘Person’, ‘Organisation’, ‘Project’ and ‘Publication’ we have a template to define meta-data for the specific object to be described. 22

Flemish government | Department of Economy, Science and Innovation Meta Data Model Pattern 23 The meta data model pattern will be used to describe the conceptual FRIS Business Object Model. This is the high level conceptual data architecture which represents the fundamental business objects and the relations between each other and the environment and the principles guiding its design and evolution (TOGAF 9.1 ISO 42010, IEEE 1471).

Flemish government | Department of Economy, Science and Innovation Meta Model Pattern applied to the Business Concept Person 24

Flemish government | Department of Economy, Science and Innovation The use of the Information Model Pattern 25 cfOrgUnit cfPers-OrgUnit cfPers-Pers cfPers-Project cfPers cfResPubl cfProj cfPers.cfGender cfPers.cfBirthDate cfPers-ResPubl

Flemish government | Department of Economy, Science and Innovation Meta Model Pattern: an application Evaluation of a MODS based model: SSH-VABB 26

Flemish government | Department of Economy, Science and Innovation Information Model Pattern: an application The Mods model template shows the following Only two of the Business Concepts can be considered Business Objects ModsCollection ModsInstance All other Mods elements form a taxonomy of business concepts which are at the level of Business Object attributes The Mods Business Concept Identifier does not relate unambiguously to a ModsInstance In essence this translates to the fact that, in ER-modeling terms the Mods template recognizes only an entity equivalent to the Business Object “Publication” From the FRIS viewpoint, the mods template fails to register the Business Object: Person and Organization Potential Business Object –Business Object relation are not modeled as such since “RelatedItems” are Business Attributes. 27

Flemish government | Department of Economy, Science and Innovation Information Model Pattern: an application 28

Flemish government | Department of Economy, Science and Innovation Information Model Pattern: an application The results of the Information Model Pattern approach allows the FRIS information architects to evaluate the relevance and usability of models like Mods by: Clearly distinguish the Business Objects concerned in the model Evaluate the possible mapping scenario’s to the FRIS Business Object model Mapping of Mods Concepts to FRIS Business Object en Business Object attributes. Mapping to FRIS Classification Objects Mapping to FRIS Code Value sets Evaluate the mapping risks in term of ambiguity, redundancy, reciprocity 29

Flemish government | Department of Economy, Science and Innovation Code Definition Pattern A Code pattern is a system of symbols (letters, numbers, shapes, sound, etc. ) used to represent assigned meanings of concepts. Just like a ‘Term’ is a word or set of words used to represent meanings of concepts. Codes often are used for easy communication, easy input in digitalized systems, information exchange between different systems, enabling semantic interoperability between systems, enabling integrated analysis between interoperating businesses, Etc. A Code is a systematic representation of the meaning of concepts. 30

Flemish government | Department of Economy, Science and Innovation Code Definition Pattern 31

Flemish government | Department of Economy, Science and Innovation Code Definition Pattern Definition “A Code is a (Technical) Business Concept that is an identifier of a Business Concept.” Eg. ‘Country Code’ is the Business Concept used to identify the Business Object ‘Country’. ‘Scientific Domain Code’ is the Business Concept used to identify a Classification Hierarchy of Scientific Domains 32

Flemish government | Department of Economy, Science and Innovation Code Definition Pattern Code Value  A Code Value is the representation of a Code.  A Code Value is a special type of Business Term  ‘Code Value’ is the name used to refer to a ‘Business Term’ in case the Business Concept that is represented is a ‘Code’ . From a modelling perspective a ‘Code Value’ is a specialisation of ‘Business Term’. Eg. ‘BE’ is a Code Value representing ‘Belgium’ according to Country Code ISO-3166 ISO-2 33

Flemish government | Department of Economy, Science and Innovation Code Definition Pattern  Code Set  A Code Set is a set of Code Values that are allowed values for concepts of a specific type, according to a specific management community.  A Code Value can be element in more than one Code Set.  The challenge is to manage which Code is exactly represented by the Code Value in the Code Set.  Difficulty in managing this aspect is often the cause of ambiguity in the definition and use of code values.  A Code Set is a special type of Business Glossary.  A Code Set can be the aggregation of multiple Code Value Sets. A typical example is ISO-3166 Country Code 34

Flemish government | Department of Economy, Science and Innovation Model Pattern overview The meta model consist of the following model patterns Business Term Model Pattern Information Model Pattern Codification Definition Pattern Object Classification Model Pattern These patterns sofar seem to suffice 35

Flemish government | Department of Economy, Science and Innovation The Patterns 36

Flemish government | Department of Economy, Science and Innovation The FRIS Model Type Stack 37 CERIF conceptual model

Flemish government | Department of Economy, Science and Innovation Template examples CASRAI profiles: Academic CV Meta model of Templates types Grouping Sub-Grouping Record Type Publication Templates OrgUnit Service Exchange Template PURE 38

Flemish government | Department of Economy, Science and Innovation 39

Flemish government | Department of Economy, Science and Innovation 40

Flemish government | Department of Economy, Science and Innovation Stack Part 2: How is it done in reality Stack Part 2: Modeling in the Data Goverance Center The Data Governance Center (DGC) Operation Model 41

Flemish government | Department of Economy, Science and Innovation 5 Modeling Concepts in DGC Operating Model

Flemish government | Department of Economy, Science and Innovation DGC Asset Types

Flemish government | Department of Economy, Science and Innovation 44

Flemish government | Department of Economy, Science and Innovation 45

Flemish government | Department of Economy, Science and Innovation 46

Flemish government | Department of Economy, Science and Innovation FRIS Communities 47

Flemish government | Department of Economy, Science and Innovation An example: Person 48

Flemish government | Department of Economy, Science and Innovation 49

Flemish government | Department of Economy, Science and Innovation cfPers 50

Flemish government | Department of Economy, Science and Innovation Mapping example: CASRAI: Family Name  CERIF: cfFamilyNames CASRAI: First Name  CERIF: cfFirstName 51

Flemish government | Department of Economy, Science and Innovation To create architecture is to put in order. Put what in order? Function and objects. Le Corbusier Architecture begins where engineering ends. Walter Gropius 52

Flemish government | Department of Economy, Science and Innovation 53