Towards Drafting a Risk Ontology based on the IRIS Risk Glossary SUMMER ACADEMY Sep 1 st – Sep 4 th 2009 Nick Bassiliades, Dimitris Vrakas Logic Programming.

Slides:



Advertisements
Similar presentations
Language standards as a cornerstone for business strategies Implications for the design of academic curricula Kara Warburton, City University of Hong Kong.
Advertisements

Formal Modelling of Reactive Agents as an aggregation of Simple Behaviours P.Kefalas Dept. of Computer Science 13 Tsimiski Str Thessaloniki Greece.
Database Systems: Design, Implementation, and Management Tenth Edition
Programming Languages Marjan Sirjani 2 2. Language Design Issues Design to Run efficiently : early languages Easy to write correctly : new languages.
So What Does it All Mean? Geospatial Semantics and Ontologies Dr Kristin Stock.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.
LEAD BENEFICIARY: ARISTOTLE UNIVERSITY OF THESSALONIKI – AUTh (Professor Demos Angelides) IRIS SUMMER ACADEMY 2011 hosted by VCE 03 – 07 September 2011,
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Chapter Chapter 1: Introduction to Decision Support Systems Decision Support.
Chapter 2: Impact of Machine Architectures What is the Relationship Between Programs, Programming Languages, and Computers.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Software Process and Product Metrics
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
Module 8: Risk Management, Monitoring and Project Control We would like to acknowledge the support of the Project Management Institute and the International.
The Edit Anders Norberg, Statistics Sweden (SCB) Work Session on Statistical Data Editing Ljubljana, Slovenia, 9-11 May 2011.
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
HW/SW/FW Allocation – Page 1 of 14CSCI 4717 – Computer Architecture CSCI 4717/5717 Computer Architecture Allocation of Hardware, Software, and Firmware.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
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.
Database Architecture Introduction to Databases. The Nature of Data Un-structured Semi-structured Structured.
TOWARDS INTEROPERABILITY IN TRACKING SYSTEMS: AN ONTOLOGY-BASED APPROACH Juan Gómez Romero Miguel A. Patricio Jesús García José M. Molina Applied A.I.
Representing variables according to the ISO/IEC standard.
CHAPTER ONE Problem Solving and the Object- Oriented Paradigm.
Spoken dialog for e-learning supported by domain ontologies Dario Bianchi, Monica Mordonini and Agostino Poggi Dipartimento di Ingegneria dell’Informazione.
Computer Science 101 Database Concepts. Database Collection of related data Models real world “universe” Reflects changes Specific purposes and audience.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Which of the following items must you consider when planning instruction in your class? Place a dot next to each item. UbD IFL/POL IEP/504/UDL ESL/SIOP.
Eurostat Expression language (EL) in Eurostat SDMX - TWG Luxembourg, 5 Jun 2013 Adam Wroński.
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Gerrit Schutte OHIM 9th of December, 2011 Trademark terminology control.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Telerik Software Academy Software Quality Assurance.
Elizabeth Furtado, Vasco Furtado, Kênia Sousa, Jean Vanderdonckt, Quentin Limbourg KnowiXML: A Knowledge-Based System Generating Multiple Abstract User.
Database Systems DBMS Environment Data Abstraction.
©Ferenc Vajda 1 Semantic Grid Ferenc Vajda Computer and Automation Research Institute Hungarian Academy of Sciences.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Project Overview Vangelis Karkaletsis NCSR “Demokritos” Frascati, July 17, 2002 (IST )
ISO-PWI Lexical ontology some loose remarks Thierry Declerck, DFKI GmbH.
Week III  Recap from Last Week Review Classes Review Domain Model for EU-Bid & EU-Lease Aggregation Example (Reservation) Attribute Properties.
Christoph F. Eick University of Houston Organization 1. What are Ontologies? 2. What are they good for? 3. Ontologies and.
SPE-RFI-R : FEB.1999 : NUL-ITD-Iwata 2-01 Needs for Software Development Model Hiromichi Iwata Information Technologies.
Developing a Software Package for Conceptualizing Molecular Findings Xinghua Lu, Harry Hocheiser & Vicky Chen Dept Biomedical Informatics.
Application Ontology Manager for Hydra IST Ján Hreňo Martin Sarnovský Peter Kostelník TU Košice.
RLV Reliability Analysis Guidelines Terry Hardy AST-300/Systems Engineering and Training Division October 26, 2004.
Formal Specification: a Roadmap Axel van Lamsweerde published on ICSE (International Conference on Software Engineering) Jing Ai 10/28/2003.
Ontology domain & modeling extensions. Modeling enhancements: overview Enhancements: – Increased expressivity in ontology – Increased expressivity in.
Using an Integrated Ontology and Information Model for Querying and Reasoning about Phenotypes The Case of Autism Samson W. Tu, MS, Lakshika Tennakoon,
Chapter 19: Building Systems with Assurance Dr. Wayne Summers Department of Computer Science Columbus State University
McGraw-Hill/Irwin © The McGraw-Hill Companies, All Rights Reserved CHAPTER 9 Enabling the Organization—Decision Making.
CIMA and Semantic Interoperability for Networked Instruments and Sensors Donald F. (Rick) McMullen Pervasive Technology Labs at Indiana University
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
Stoimen Stoimenov QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
C. Mugnier, D. Lafarge, C. Perolini, R. Pilon, J. Ruiz-Cabezas
UNIFIED MEDICAL LANGUAGE SYSTEMS (UMLS)
Knowledge Representation Techniques
Business process management (BPM)
Towards a framework for architectural design decision support
DOMAIN ONTOLOGY DESIGN
Security SIG in MTS 05th November 2013 DEG/MTS RISK-BASED SECURITY TESTING Fraunhofer FOKUS.
Business process management (BPM)
Complexity Time: 2 Hours.
Abstract descriptions of systems whose requirements are being analysed
Ontology.
Chapter 19: Building Systems with Assurance
مدل زنجیره ای در برنامه های سلامت
SCOTT NO meeting Measurement
Presentation transcript:

Towards Drafting a Risk Ontology based on the IRIS Risk Glossary SUMMER ACADEMY Sep 1 st – Sep 4 th 2009 Nick Bassiliades, Dimitris Vrakas Logic Programming & Intelligent Systems group Dept. of Informatics Aristotle University of Thessaloniki

RAT Risk Factors Risk Risk Assessment Tool Risk Identification Methodology Risk Management Standard Risk Components Risk Attributes

RAT Risk Factor 1 Risk Risk Assessment Tool Risk Identification Methodology Risk Management Standard CBR MBR Risk Factor 2 Risk Factor 3 Risk Factor n …

Why do we need Ontologies? All the variables associated with the Risk Assessment Process must be defined in the Risk Ontology(ies) – Inputs to RAT – Outputs of RAT – Past cases or Models – Others Why? – To facilitate integration of risk assessment practices from different domains – To eliminate misunderstandings concerning the use of terms – To allow the use of various ways to describe the same term (synonyms, translations, e.t.c) – To enable the software to reason in a higher level of abstraction (general rules that apply to a group of specific cases)

The Ontology Server IRIS Risk Glossary

Definition of Risk Risk is a function of probability, exposure and vulnerability. – Often, exposure is incorporated in the assessment of consequences Risk can be considered as having two components – the probability that an event will occur and – the impact (or consequence) associated with that event

Class Hierarchy

Object Properties Relating Risk to Other Concepts

Risk Class Properties

Event Properties

Probability Properties

Consequence Properties

Risk Specializations (1/3)

Risk Specializations (2/3) There are special cases of risks requiring additional properties – E.g. acceptable risk has an acceptance level property

Risk Specializations (3/3) There are special cases of risks imposing restrictions on properties of general concepts – E.g. individual risk has a consequences for a single human

Consequence Specializations

Human Consequences

Individual Human Consequences

Multilingual Capabilities (1/2) Concepts in ontology are expressed in English Use of annotation properties (rdfs:label) in classes for expressing the concept in multiple languages

Multilingual Capabilities (2/2) More than one synonym terms can be expressed using multiple rdfs:label entries

Thank you! Ontology can be found at: