ACM Home Page
Please provide us with feedback. Feedback
Software engineering for safety: a roadmap
Full text PdfPdf (1.21 MB)
Source International Conference on Software Engineering archive
Proceedings of the Conference on The Future of Software Engineering table of contents
Limerick, Ireland
Pages: 213 - 226  
Year of Publication: 2000
ISBN:1-58113-253-0
Author
Robyn R. Lutz  Jet Propulsion Laboratory, California Institute of Technology, 4800 Oak Grove Drive, M/S 125-233, Pasadena, CA
Sponsors
IEEE-CS : Computer Society
SIGSOFT: ACM Special Interest Group on Software Engineering
Irish Comp Soc : Irish Computer Society
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 24,   Downloads (12 Months): 176,   Citation Count: 7
Additional Information:

references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/336512.336556
What is a DOI?

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
J.-R. Abrial, E. Borger, and H. Langmaack. Formal Methods for Industrial Applications: Specifying and Programming the Steam Boiler Control, volume 1165 of LCNS. Springer-Verlag, 1996.
 
2
 
3
 
4
 
5
J. Bowen. Safety-critical systems, http://archive.comlab.ox, ac.uk/safety.html.
 
6
7
 
8
 
9
 
10
 
11
 
12
 
13
L. Dumas and A. Walton. Faster, better, cheaper: an institutional view. In Proc 50th Annual 1at Astronautical Congress, 1999.
 
14
 
15
 
16
 
17
 
18
 
19
A. Finkelstein. Requirements engineering: a review and research agenda. In Proc 1st Asian and Pacific Software Engineering Conference, pages 10-19, 1994.
 
20
G. C. Gannod and R. R. Lutz. An approach to architecturaJ analysis of product lines, submitted.
 
21
22
23
 
24
 
25
 
26
 
27
 
28
 
29
L. M. Ippolito and D. R. Wallace. A study on hazard anMysis in high integrity software standards and guidelines. Technical Report NISTR 5589, U.S. Department of Commerce, 1995.
 
30
 
31
S. J. Keene. Developing software for safety critical systems. IEEE, NTSC ISBN 0-7803-4573-8, 1998.
 
32
J. C. Knight and L. G. Nakano. Software test techniques for system fault-tree analysis. In Proc of 16th Int Conf on Computer Safety, Reliability, and Security, 1997.
33
34
 
35
N. Leveson. Safeware. Addison-Wesley, Reading, MA, 1995.
36
 
37
N. G. Leveson, L. D. Pinnel, S. D. Sandys, S. Koga, and J. D. Reese. Analyzing software specifications for mode confusion potential. In Proc Workshop on Human Error and System Development, pages 132-146, 1997.
 
38
 
39
 
40
 
41
R. R. Lutz and Y. Ampo. Experience report: Using formal methods for requirements analysis of critical spacecraft software. In Proc of 19th Annual Software Eng Workshop, pages 231-248, 1994.
 
42
 
43
 
44
T. Maier. FMEA and FTA to support safe design of embedded software in safety-critical systems. In Proc CSR 12th Annual Workshop on Safety and Reliability of Software Based Systems, 1995.
 
45
 
46
J. A. McDermid, M. Nicholson, D. J. Pumfrey, and P. Fenelon. Experience with the application of HAZOP to computer-based systems. In Proc 10th Annual Con} on Computer Assurance, pages 37-48, 1995.
 
47
48
 
49
NASA Mars Climate Orbiter Mishap Investigation Board. Phase I report, November 1999.
 
50
P. G. Neumann. The RISKS digest. http://www.csl.sri.com/-isko/risks.html; http://catless.ncl, ac.uk/Risks.
 
51
52
 
53
Northwestern University's Qualitative Reasoning Group. Welcome to the principles of operations, http://rax.arc.nasa.gov:80/activities/pofo/docs/index.htm.
 
54
55
56
 
57
 
58
H. Petrowski. To engineer is human. Vintage Books, New York, 1992.
 
59
 
60
President's Information Technology Advisory Committee. Information Technology Research: Investing in Our Future. February 1999.
 
61
 
62
D. Raheja. Assurance Technologies: principles and practices. McGraw-Hill, 1991.
 
63
 
64
J. Rushby. Critical system properties: Survey and taxonomy. Reliability Engineering and System Safety, 43(2):189-214, 1994.
 
65
J. Rushby. Formal methods and their role in the certification of critical systems. In R. Shaw, editor, Safety and Reliability of Software Based Systems, pages 1-42. Springer, 1995.
 
66
J. Rushby. Using model checking to help discover mode confusions and other automation surprises. In Proc 3rd Workshop on Human Error, Safety, and System Development, 1999.
 
67
J. M. Rushby. Partitioning in avionics architectures: Requirements, mechanisms, and assurance. Technical reoort. SRI. March 1999.
68
 
69
G. Slabodkin. Software glitches leave navy smart ship dead in the water, http://www.gcn.com/archives- /gcn/1998/July13/cov2.htm, July 13 1998.
 
70
 
71
V. Stavridou. Provably dependent software architectures for adaptable avionics. In Proc 18th Digital Avionics Systems Coal, 1999.
 
72
 
73
L. Strigini. Considerations on current research issues in software safety. Reliability Engineering and System Safety, 43:177-188, 1994.
 
74
75
 
76
 
77
 
78
79
 
80
Workshop on Research in Theoretical Computer Science. Challenges for theory of computing, 1999.
81