a way for applicable formal specification of safety requirements by ...

More documents

Recommendations

Info

With the tool SAPIS the safety pattern concept moves from theory into practice. A web application is available (see Bitsch & Lovasi, 2002) for identification of the appropriate safety patterns for the safety requirements to be specified. We are still collecting more practical experience for the safety pattern concept with the help of case studies, especially by developing system models related to the railway control area. It is planed to extend the tool SAPIS by support functions for the application of the selected safety patterns for safety requirements specification. The safety pattern norm language is still under development. The reference of the terms of the norm language is to be supported by hyperlink technology. Also a graphical notation in speciality for safety pattern specification is currently being developed. So far graphical representations are only used for explanations of examples, which fulfil the requirement of the respective safety pattern. conventional safety requirment specification safety pattern dialogue system safety pattern identification catalogue of the suitable safety pattern specification of safety requirement • in formal language • in norm language • formal language • norm language • graphical explanations • explanation in natural language • example of use Fig. 3. Principle of the safety pattern approach. Furthermore an XML-based language is under development. Such an XML-based language will be the basis to generate the specification of the safety patterns in different formal languages. In such a way it is not necessary to specify manually every safety pattern in several formal specification languages. Besides, an XML-based safety pattern language is also a suitable software technology basis to explain the safety patterns by graphical illustrations or by simulations. A further benefit is that using XML a specification language could be developed, which is easily useable and interpretable and which is oriented according to the safety pattern classification. Such a language would not be as universal as temporal logic languages but fit the characteristics of safety pattern properties. ACKNOWLEDGEMENT This work was sponsored by the German Research Council (DFG) within the scope of the focus area program (1064) on the “Integration of Specification Techniques with Applications in Engineering” which is gratefully acknowledged. REFERENCES Arabestani, S. and J.-T. Gayen (2000). Objektorientierte Analyse zur Modellierung im Eisenbahnwesen. Signal & Draht 92(2000)1+2, S. 20-27. Bitsch, F., E. Canver and A. Moik (2000). Strukturierte Erstellung von Sicherheitsspezifikationen in UML mit Hilfe der FMEA- Methode. In: FORMS '99 - Formale Techniken für die Eisenbahnsicherung (E. Schnieder, Ed.), Fortschritt-Berichte VDI, Reihe 12, Nr.436, VDI Verlag GmbH, Düsseldorf, S. 225-245. Bitsch, F. and C. Lovasi (2002). Safety Pattern Instantiation System - SAPIS. http:// www.ias.uni-stuttgart.de/safety_patterns/. Bitsch, F. (2002). Process Model for the Development of System Requirements Specifications for Railway Systems. In: Workshop on Software specification of safety relevant transportation control tasks (E. Schnieder, Ed.), Fortschritt-Berichte VDI, VDI Verlag GmbH, Düsseldorf. Bitsch, F. (2001). Safety Patterns - The Key to Formal Specification of Safety Requirements. In: Proceedings of 20th International Conference SAFECOMP 2001 - Computer
Safety Reliability and Security (U. Voges, Ed.), Berlin, Heidelberg: Springer-Verlag, LNCS 2187, S. 176-189. Bitsch, F. and P. Göhner (2002). Spezifikation von Sicherheitsanforderungen mit Safety- Patterns. Software Engineering in der industriellen Praxis, VDI-Bericht-Nr. 1666, Düsseldorf, S. 29-40. Heitmeyer, C. and J. Kirby, Jr., B. Labaw, M. Archer and R. Bharadwaj (1998). Using Abstraction and Model Checking to Detect Safety Violations in Requirements Specifications. IEEE Transactions on software engineering, vol. 24, no. 11, pp. 927-948, November 1998. Dill, D.L. and A.J. Drexler, A.J. Hu, and C.H. Yang (1992). Protocol Verification as a Hardware Design Aid. Proc. IEEE Int’l Conf. Computer Design: VLSI in Computers and Processors, pp. 522–525. Dwyer, M.B. et al. (1999). Patterns in Property Specification for Finite-state Verification. In Proceedings of the 21st International Conference on Software Engineering. Flake, S. and W. Mueller (2001). An OCL Extension for Real-Time Constraints. In: Advances in Object Modelling with the OCL (T. Clark and J. Warmer, Eds.). Heidelberg: Springer-Verlag. Gorski, J. (1986): Design for Safety Using Temporal Logic. In: Proceedings of Safecomp ’86 (W.J. Quirk, Ed.), pergamon press, Oxford. Huth, M. and M. Ryan (2000). Logic in Computer Science – Modelling and reasoning about systems. Cambridge: Cambridge University press. Kammel, K., K. Lennartz and K.-H. Suwe (2000). Die Anwendung von formalen Techniken aus Sicht des Eisenbahn- Bundesamtes. In: FORMS '99 - Formale Techniken für die Eisenbahnsicherung (E. Schnieder, Ed.), Fortschritt-Berichte VDI, Reihe 12, Nr.436, VDI Verlag GmbH, Düsseldorf, S. 55-69. CENELEC EN 50128 (2001). Railway Applications - Communications, signaling and processing systems - Software for railway control and protection systems. CENELEC prEN 50129 (2000). Railway Applications - Safety related electronic systems for signaling. Heiner, M., Th. Mertke and P. Deussen (2001). A Safety-oriented Technical Language for the Requirement Specification in Control Engineering. Computer Science Reports 09/01, Brandenburg University of Technology at Cottbus, May 2001. International Standard IEC 61508 (2000). Functional Safety of Electrical/Electronic/ Programmable Electronic Safety Related Systems. International Electrotechnical Commission, Geneva, Switzerland. Mertke, Th., P. Deussen and M. Heiner (2001): Eine anwenderorientierte Sicherheitsfachsprache zur Verifikation von Steuerungsprogrammen. In: Engineering komplexer Automatisierungssysteme (EKA) (E. Schnieder, Ed.), S. 297-309. Moik, A. (2002). Ingenieurgerechte formale Methoden für die Entwicklung von sicheren Automatisierungssystemen. Dissertation, IAS, Universität Stuttgart. navicon GmbH (2002). Produktbroschüre “Navican Decision Suite”. Frankfurt. Ortner, E. (1997). Methodenneutraler Fachentwurf - Zu den Grundlagen einer anwendungsorientierten Informatik. Stuttgart, Leipzig: B. G. Teubner Verlagsgesellschaft, 1997. I-Logix Inc. and OFFIS Systems and Consulting GmbH (2002). Statemate Magnum – Certifier – Pattern Library – User Guide. Andover. Schienmann, E. (1997). Objektorientierter Fachentwurf. Stuttgart, Leipzig: B. G. Teubner Verlagsgesellschaft. Villa, T., G. Swamy and T. Shiple. VIS User’s Manual. The VIS Group, University of California, Berkeley. Wille, R. (2000). Begriffliche Wissensverarbeitung: Theorie und Praxis. Informatik Spektrum, Organ der GI, Band 23, Heft 6, S. 357-369, Dezember 2000.
Page 1 and 2: A WAY FOR APPLICABLE FORMAL SPECIFI
Page 3 and 4: (Globally)”, “Until” and “W
Page 5 and 6: Safety Pattern ds-wet-27 dynamic sa
Page 7 and 8: mode “strong guided dialog“ so
Page 9: is, the more it is difficult to con

a way for applicable formal specification of safety requirements by ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?