Lutz, R. Software Engineering for Safety: A Roadmap, Proceedings of the 22nd International Conference on Software Engineering (ICSE 2000), Limerick, Ireland, June 4--11, 2000, ACM. Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Testing: A Roadmap - Harrold (2000) (14 citations) (Correct)
....subjects can be used for experimentation. If these subjects cannot be made available publicly, we may be able to create sanitized information that would reveal no proprietary information but would still be useful for experimentation. 3 TESTING RESOURCES Other reports in this volume (e.g. [12, 17, 25, 30, 31]) provide additional information about verification. Several recent workshops, including the Workshop on Strategic Directions in Software Quality (1996) spon sored by Association of Computing Machinery, National Science Foundation, and Computing Research Association, International Workshop on the ....
R. Lutz. Software engineering for safety: A roadmap. In A. Finkelstein, editor, The Future of Software Engineering. ACM Press, New York, 2000.
Software Engineering for Real-Time: A Roadmap - Kopetz (2000) (3 citations) (Correct)
....be decided whether a given system is safe to deploy in the intended application domain. If this application domain is safety critical, i.e. a failure of the computer system can result in high financial loss or even a catastrophe where human lives are endangered then this decision is difficult [13]. Many safety critical applications demand a level of dependability that cannot be established by state of the art testing technology [12] In this section we discuss some trends in the field of validation of high dependability real time systems. 6.1 Process versus Product Since it is beyond the ....
Lutz, R.L. (2000). Software Engineering for Safety: A Roadmap. In this volume
Testing: A Roadmap - Harrold (2000) (14 citations) (Correct)
....subjects can be used for experimentation. If these subjects cannot be made available publicly, we may be able to create sanitized information that would reveal no proprietary information but would still be useful for experimentation. 3 TESTING RESOURCES Other reports in this volume (e.g. [12, 17, 25, 30, 31]) provide additional information about verification. Several recent workshops, including the Workshop on Strategic Directions in Software Quality (1996) sponsored by Association of Computing Machinery, National Science Foundation, and Computing Research Association, International Workshop on the ....
R. Lutz. Software engineering for safety: A roadmap. In A. Finkelstein, editor, The Future of Software Engineering. ACM Press, New York, 2000.
Development of a Normative Package for Safety-Critical.. - Vilkomir, Ghose (Correct)
No context found.
Lutz, R. Software Engineering for Safety: A Roadmap, Proceedings of the 22nd International Conference on Software Engineering (ICSE 2000), Limerick, Ireland, June 4--11, 2000, ACM.
Trust-By-Contract: Modelling, Analysing And Predicting.. - Schmidt, Poernomo.. (2001) (Correct)
No context found.
: The Future of Software Engineering, 22nd Intl. Conf. Software Engineering, IEEE, 2000
Templates for Misuse Case Description - Guttorm Sindre Andreas (2001) (2 citations) (Correct)
No context found.
R. R. Lutz, "Software Engineering for Safety: A Roadmap", in A. Finkelstein (ed.): The Future of Software Engineering, ACM Press, 2000.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC