dopropc: a domain property pattern system helping to specify control system requirements fan wuhehua...
TRANSCRIPT
DOPROPC: a domain property pattern system helping to specify
control system requirements
Fan Wu Hehua Zhang Ming GuSchool 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—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 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
• 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) 189 - 191, Burlington, Vermont, USA.