DOPROPC: a domain property pattern system helping to specify control system requirements Fan WuHehua ZhangMing Gu School of Software, Tsinghua University.

Slides:



Advertisements
Similar presentations
1 Verification by Model Checking. 2 Part 1 : Motivation.
Advertisements

Copyright 2000 Cadence Design Systems. Permission is granted to reproduce without modification. Introduction An overview of formal methods for hardware.
Critical Reading Strategies: Overview of Research Process
Auto-Generation of Test Cases for Infinite States Reactive Systems Based on Symbolic Execution and Formula Rewriting Donghuo Chen School of Computer Science.
The Conference Presentation Lynda Gagne University of Victoria October 2004.
LASER From Natural Language Requirements to Rigorous Property Specifications Lori A. Clarke Work done in collaboration with Rachel L. Smith, George S.
1 Mechanical Verification of Timed Automata Myla Archer and Constance Heitmeyer Presented by Rasa Bonyadlou 24 October 2002.
Formal verification of safety communication protocol for ETCS Chen Lijie  Introduction  Safety communication protocol in ETCS  CPN model.
Rafael Duque Medina Position in CHICO: Investigator Position in UCLM: Investigator Maximum Degree: Engineer in Computer Science Research Lines:  CSCW/CSCL.
Algorithms and Problem Solving-1 Algorithms and Problem Solving.
Algorithms and Problem Solving. Learn about problem solving skills Explore the algorithmic approach for problem solving Learn about algorithm development.
Four Dark Corners of Requirements Engineering
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
Writing Good Software Engineering Research Papers A Paper by Mary Shaw In Proceedings of the 25th International Conference on Software Engineering (ICSE),
Final Year Dissertation Advice Daniel Bryant Software Systems Group Dept. of Computing.
School of Computer ScienceG53FSP Formal Specification1 Dr. Rong Qu Introduction to Formal Specification
1 Formal Engineering of Reliable Software LASER 2004 school Tutorial, Lecture1 Natasha Sharygina Carnegie Mellon University.
Ontologies for Cadastral Processes Gerhard Navratil COST G9-Meeting Aalborg,
Department of Computer Science & Engineering College of Engineering Dr. Betty H.C. Cheng, Laura A. Campbell, Sascha Konrad The demand for distributed real-time.
Formal verification Marco A. Peña Universitat Politècnica de Catalunya.
Reduction and Slicing of Hierarchical State Machines Mats Heimdahl et al. University of Minnesota Presented by Tom McMullen For CISC836 1.
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
«Tag-based Social Interest Discovery» Proceedings of the 17th International World Wide Web Conference (WWW2008) Xin Li, Lei Guo, Yihong Zhao Yahoo! Inc.,
Bridging the chasm between MDE and the world of compilation Nondini Das 1.
Writing Scientific Articles – General Structures Agus Suryanto Department of Mathematics FMIPA – Brawijaya University.
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
Architecture-Based Runtime Software Evolution Peyman Oreizy, Nenad Medvidovic & Richard N. Taylor.
SOUPA: Standard Ontology for Ubiquitous and Pervasive Applications Harry Chen, Filip Perich, Tim Finin, Anupam Joshi Department of Computer Science & Electrical.
Agent-Oriented Software Engineering CSC532 Xiaomei Huang.
Verification and Validation Overview References: Shach, Object Oriented and Classical Software Engineering Pressman, Software Engineering: a Practitioner’s.
OHTO -99 SOFTWARE ENGINEERING LECTURE 5 Today: - An overview to OO Analysis and OO Design - Introduction of Assignment 2.
Dart: A Meta-Level Object-Oriented Framework for Task-Specific Behavior Modeling by Domain Experts R. Razavi et al..OOPSLA Workshop DSML‘ Dart:
Standards for Mathematical Practice #1 Make sense of problems and persevere in solving them. I can: explain the meaning of a problem. choose the right.
Author: Graham Hughes, Tevfik Bultan Computer Science Department, University of California, Santa Barbara, CA 93106, USA Source: International Journal.
UML Profile to Support Requirements Engineering with KAOS Presented by Chin-Yi Tsai.
B. Fernández, D. Darvas, E. Blanco Formal methods appliedto PLC code verification Automation seminar CERN – IFAC (CEA) 02/06/2014.
Dimitrios Skoutas Alkis Simitsis
A Collaborative and Semantic Data Management Framework for Ubiquitous Computing Environment International Conference of Embedded and Ubiquitous Computing.
1 Context-dependent Product Line Practice for Constructing Reliable Embedded Systems Naoyasu UbayashiKyushu University, Japan Shin NakajimaNational Institute.
Overview Of Expert System Tools Expert System Tools : are all designed to support prototyping. Prototype : is a working model that is functionally equivalent.
K. Ingram (with thanks to A. Seddon) Staffordshire UNIVERSITY School of Computing Introduction to Software System Design.
Architectural Point Mapping for Design Traceability Naoyasu Ubayashi and Yasutaka Kamei Kyushu University, Japan March 26, 2012 FOAL 2012 (AOSD Workshop)
Outline Introduction – Frequent patterns and the Rare Item Problem – Multiple Minimum Support Framework – Issues with Multiple Minimum Support Framework.
Deriving Operational Software Specification from System Goals Xin Bai EEL 5881 Course Fall, 2003.
Basic Concepts of Component- Based Software Development (CBSD) Model-Based Programming and Verification.
MODES-650 Advanced System Simulation Presented by Olgun Karademirci VERIFICATION AND VALIDATION OF SIMULATION MODELS.
Bandera: Extracting Finite-state Models from Java Source Code. Paper By: James C. Corbett, Mathew Dwyer, John Hatcliff, Shawn Laubach, Corina Pasareanu,
Ensure that the right functions are performed Ensure that the these functions are performed right and are reliable.
1 Levent Yilmaz COMP7730: Formal Methods in Software Engineering.
Some Thoughts to Consider 8 How difficult is it to get a group of people, or a group of companies, or a group of nations to agree on a particular ontology?
Properties as Processes : FORTE slide Properties as Processes: their Specification and Verification Joel Kelso and George Milne School of Computer.
Model validity, testing and analysis. Conceptual and Philosophical Foundations Model Validity and Types of Models –Statistical Forecasting models (black.
Formal Methods in Software Engineering1 Today’s Agenda  Mailing list  Syllabus  Introduction.
Requirements Engineering Methods for Requirements Engineering Lecture-31.
Automated Formal Verification of PLC (Programmable Logic Controller) Programs
Research Methodology II Term review. Theoretical framework  What is meant by a theory? It is a set of interrelated constructs, definitions and propositions.
“The Role of Experience in Software Testing Practice” A Review of the Article by Armin Beer and Rudolf Ramler By Jason Gero COMP 587 Prof. Lingard Spring.
Algorithms and Problem Solving. Learn about problem solving skills Explore the algorithmic approach for problem solving Learn about algorithm development.
Cs498dm Software Testing Darko Marinov January 24, 2012.
A Simple Fuzzy Excitation Control System for Synchronous Generator International conference on emerging trends in electrical and computer technology, p.p.
Luca Pazzi, Marco Pradelli University of Modena and Reggio Emilia
Chapter3:Software Processes
Algorithms and Problem Solving
Timed Safety Property Runtime Enforcement Wanjiang Qian 03/22/2016.
A. P. Shah Institute of Technology
Is “Higher Level” Better?
Introduction to Pattern Oriented Analysis and Design (POAD)
Algorithms and Problem Solving
Towards a Unified Theory of Operational and Axiomatic Semantics
Dept. of Computation, UMIST
Presentation transcript:

DOPROPC: a domain property pattern system helping to specify control system requirements Fan WuHehua ZhangMing Gu School of Software, Tsinghua University Beijing, China

Outline Introduction Overview of DOPROPC property patterns Main conclusions of this paper Future work

Introduction Model checking provides means to validate the correctness of systems. It is often desired by safety critical control systems. However, it hasn’t been widely used in industry. A primary cause is that industry experts are not familiar with formal logics.

Introduction To overcome this difficulty, Dwyer et al.[1] firstly developed a pattern system for property specification. The property patterns are high-level abstractions of frequently used temporal logic formulae.

Introduction Although property patterns have already been in the abstract level, we found there is still a long distance from requirements to them. Using Property pattern is usually difficult to industrial engineers, since it also needs knowledge about formal semantics.

Introduction we come up with an idea: using what industrial engineers are most familiar with -domain knowledge- to do the work. That is to say adding domain knowledge to property patterns which can be a bridge between domain knowledge and formal semantics.

DOPROPC property patterns We developed DOPROPC as a two layer property pattern system.

DOPROPC—Bottom layer The bottom layer depends on qualitative property patterns [1], real-time property patterns [2, 3] and probabilistic property patterns [4]. We merge these three patterns together to gain an overall view.

DOPROPC—Bottom layer TABLE I. Basic property patterns 2 Categories, 15 property patterns

DOPROPC—Bottom layer TABLE II. Absence Pattern Each pattern includes four parts elements, Table II shows Absence pattern as an example.

DOPROPC—Top layer We concluded 39 domain property patterns of control systems, which are classified into 12 categories. The patterns are generalized from 104 properties of several real control systems.

DOPROPC—Top layer Analog quantityTime horizonMutual exclusionState reachability State holdStart upStopManual control Command control Fault handlingMotion controlAlarm 12 domain property categories:

DOPROPC—Top layer Each pattern includes five parts elements, Table III shows an example. TABLE III. ANALOG QUANTITY 2 Domain Property Pattern

Conclusions Our work has three contributions: – merging existent property patterns [1-5] as a full-scale basic property pattern system; – presenting a domain based property patterns of control; – developed a specification editor to help users to use DOPROPC easily, but for the space limitation, we haven’t introduced the editor in this paper.

Future work Optimize domain property patterns of control systems. Try to conclude a methodology from summarizing different domain property patterns as a general method to help different domain experts to develop their own domain property patterns.

References [1] M. B. Dwyer, G. S. Avrunin, and J. C. Corbett. Patterns in property specifications for finite- state verification. In Proceedings of the 1999 International Conference on Software Engineering (ICSE’99), 1999:411–421. [2] V. Gruhn and R. Laue. Patterns for timed property specifications. Electr. Not. Theor. Comp. Sci, 2006, 153(2):117–133. [3] S. Konrad and B. H. C. Cheng. Real-time specification patterns. In G.-C. Roman, W. G. Griswold, and B. Nuseibeh, editors, 27th Int. Conf. on Software Engineering, ICSE 05, 2005:372– 381. [4] L. Grunske. Specification patterns for probabilistic quality properties. In Robby, editor, 30th International Conference on Software Engineering (ICSE 2008), 2008:31–40. [5] Gruhn V. Laue R. Specification Patterns for Time-Related Properties. In 12th International Symposium on Temporal Representation and Reasoning (2005) , Burlington, Vermont, USA.

Q&A Any questions, please contact Thank you!