New Kind of Logic The first step to approch this questions consists of a new definition of logic operators able to explain the richness of the events happened.

Slides:



Advertisements
Similar presentations
Chapter 7 System Models.
Advertisements

Configuration management
Modern information retrieval Modelling. Introduction IR systems usually adopt index terms to process queries IR systems usually adopt index terms to process.
Introducing Formal Methods, Module 1, Version 1.1, Oct., Formal Specification and Analytical Verification L 5.
Copyright Irwin/McGraw-Hill Data Modeling Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley.
Formal Methods in Software Engineering Credit Hours: 3+0 By: Qaisar Javaid Assistant Professor Formal Methods in Software Engineering1.
Software Requirements
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Formal Methods. Importance of high quality software ● Software has increasingly significant in our everyday activities - manages our bank accounts - pays.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
© Copyright 2011 John Wiley & Sons, Inc.
Using Use Case Scenarios and Operational Variables for Generating Test Objectives Javier J. Gutiérrez María José Escalona Manuel Mejías Arturo H. Torres.
Sharif University of Technology Session # 7.  Contents  Systems Analysis and Design  Planning the approach  Asking questions and collecting data 
The Fundamentals: Algorithms, the Integers & Matrices.
BIS310: Week 7 BIS310: Structured Analysis and Design Data Modeling and Database Design.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Software Engineering 8. System Models.
Teaching Teaching Discrete Mathematics and Algorithms & Data Structures Online G.MirkowskaPJIIT.
©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.
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Engineering Law-Governed Approaches How to reuse, extend and compose interaction specifications Gustavo Carvalho, Carlos Lucena
Configuration Management (CM)
CMPT 275 Software Engineering
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Author: Graham Hughes, Tevfik Bultan Computer Science Department, University of California, Santa Barbara, CA 93106, USA Source: International Journal.
Chapter 7 System models.
Slide 1 System models. Slide 2 Objectives l To explain why the context of a system should be modelled as part of the RE process l To describe behavioural.
System models l Abstract descriptions of systems whose requirements are being analysed.
Pertemuan 19 PEMODELAN SISTEM Matakuliah: D0174/ Pemodelan Sistem dan Simulasi Tahun: Tahun 2009.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 On Interactions in the RM-ODP Guy Genilloud, Gonzalo Génova WODPEC’2005 Workshop on ODP for Enterprise Computing * Information Engineering Group Departamento.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Formal Specification of Intrusion Signatures and Detection Rules By Jean-Philippe Pouzol and Mireille Ducassé 15 th IEEE Computer Security Foundations.
Copyright © 2010, 2007, 2004 Pearson Education, Inc. All Rights Reserved. Section 7-1 Review and Preview.
Programming Languages and Design Lecture 3 Semantic Specifications of Programming Languages Instructor: Li Ma Department of Computer Science Texas Southern.
8-1 Compilers Compiler A program that translates a high-level language program into machine code High-level languages provide a richer set of instructions.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Software Requirements Specification (SRS)
Software Requirements Specification Document (SRS)
Properties as Processes : FORTE slide Properties as Processes: their Specification and Verification Joel Kelso and George Milne School of Computer.
Chapter 1: Getting Started Section 1: Essential question: What is statistics?
1 Specification A broad term that means definition Used at different stages of software development for different purposes Generally, a statement of agreement.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
Presented by Kyumars Sheykh Esmaili Description Logics for Data Bases (DLHB,Chapter 16) Semantic Web Seminar.
DataTAG is a project funded by the European Union International School on Grid Computing, 23 Jul 2003 – n o 1 GridICE The eyes of the grid PART I. Introduction.
Introduction: Databases and Database Systems Lecture # 1 June 19,2012 National University of Computer and Emerging Sciences.
Chapter 27 Network Management Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Model Checking Early Requirements Specifications in Tropos Presented by Chin-Yi Tsai.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
5 Chapter 5: Modeling Systems Requirements: Events and Things Systems Analysis and Design in a Changing World.
Requirements Specification
Knowledge Representation Techniques
GridICE monitoring for the EGEE infrastructure
Web Ontology Language for Service (OWL-S)
Abstract descriptions of systems whose requirements are being analysed
a VO-oriented perspective
Data Model.
Copyright © Cengage Learning. All rights reserved.
Chapter 15 Functional Programming 6/1/2019.
SECTION 4: OO METHODOLOGIES
Sets and Probabilistic Models
Presentation transcript:

New Kind of Logic The first step to approch this questions consists of a new definition of logic operators able to explain the richness of the events happened in the system. Let’s introduce the following table: Occurs when both e1 and e2 occur irrespective of their order 1)Occurs when e1 or e2 occur (logic or) 2)Occurs when e1 timestamp is less then e2 3)Occurs T-time later after occurrence of e 4)Occurs when e1 followed by e2 occur with no interleaving of e3 It appears necessary to give an answer to the subsequent questions: how does the system remember the happened events? how long does the system have to remember that e1 event has happened and wait for event e2? A Monitoring Subscription Language in the Framework of Distributed System De Bortoli N., Palmiero R., Tortone G., Department of Physic, Department of Mathematics University of Naples and INFN section of Naples Abstract The Grid technology is attracting much interest, involving hundreds of researchers and software engineers around the world. The characteristics of Grid demand the developing of a suitable monitoring system, able to obtain the significant information in order to make management decision and control system behaviour. In this paper we are going to analyze a formal declarative interpreted language for the description of monitoring events. A user expresses his interest in verifying certain events, for example he/she is interested in the occurring of subsequent composite events: e1:= 'workload for ten minutes >K', after e2:='number of active machine <y', so he/she subscribes the event e:= e1 after e2. This language, inspired to Generalized Event Monitoring Language (GEM)[1], allows high level subscriptions to be specified as composition of atomic subscriptions and integrates the concept of real time. The language allows to express many temporal constraints, which would have been very difficult to specify in distributed systems. The goal of our research project consists of three steps: 1) the description of subscriptions through the use of a formal language; 2) the translating of the problem in a XML frame, using XML metalanguage tools; 3) the integration of this new language, made 'ad-hoc', in monitoring services. Introduction The monitoring is the activity of collecting, presenting and measuring significant information asked from human observer or automatic system. In the same way Grid monitoring consists of measuring the resource-related parameters in order to analyze usage, to detect and to notify fault situations and user-defined events with the aim of building a behaviour model of a Grid system. The present research work is involved in the context of Grid Ice but it is independent from it. In details it regards notification service and the area of XML document filtering. Temporal costraints are fundamental in many activities concerning distributed systems. Another important question is the changing of monitoring requirements without stopping the system. In this paper we are going to model a new declarative interpreted language to explain monitoring events, available to generic user, without knowing XML subscription language. We are interested in expressing many temporal constraints, which would have been very difficult to specify in distributed systems. Events, subscriptions, notifications An event is an incident which happens during the life of a system. Primitive events regard the changing of only one characteristic of a monitored object, a composite event is a composition of the primitive ones. A generic event consists of a finite set of ordered n-ples (n=4) where each one is defined in the subsequent way: event:= {(name, type,value,tms),...,} Which means: type:= type chosen between predefined primitive types used in a programming language name:= name of the event value:= value, boolean or numerical tms:= time of events happening The given definition is the most frequently used in literature regarding events. An atomic event or a simple event is defined as a set containing only one element: (name, type, value, tms) Example: (integer, pressure, 2, 12:31), or equally: (integer, pressure=2, at 12:31) A subscription is defined as a finite set of n-ples and constraints on the values that these n-ple can assume. A subscription specifies the attributes and the binary operators on the assumed values: { (integer, pressure, x, *) | x >= 1.5 } In the previous case the user is interested in all events where name is pressure, type is integer with value greater than 1.5, published any time from emission of subscription. Observation: for many authors the definition of the event is equivalent to the definition of notification. In this work a notification is the information sent to one or more users to notify an event of his/her interest. The algebra The aim of this paragraph is to define the cover relation between set events and set subscriptions. Let’s define set E that contains all events produced by the system. Let’s define set S that contains all subscription subscribed by users. The subset of all events that satisfy the given subscription is contained in E. Let’s call it: E_{s}. An event covers a subscription when it satisfies the given subscription. The cover relation, defined on the set subscriptions, is a partial ordered relation. OperatorsEvent e1 &e2It happens if e1 and e2 occur e1|e2It happens if e1 or e2 occur e1; e2It happens if e1 occurs before e2 e + timeTIt happens a T-time after e has occurred {e1; e2} ! e3It happens if e1 occurs before e2 and e3 hasn’t happened Discovery ConsumersScheduler HTML XMLNotificationCharts Data aggregation and abstraction Persistent storage Conclusions During this year we are going to define the details (sintax, sintax categories, semantic...) of this new language. The notion of real­time has been integrated within the language, allowing the users to subscribe events depending on time points. We define the occurrence interval of a composite event as the period of time during which it is occurring. We think that the language has to be: declarative: it previews sequences like event-action interpreted: so as to be portable generalised: to explain all kind of events user frendly: it has to be simple to use Our interest is also oriented towards real time logic. At the end of the research work we will develop a first version of the interpreter.