ACM Home Page
Please provide us with feedback. Feedback
Targeting safety-related errors during software requirements analysis
Full text PdfPdf (731 KB)
Source Foundations of Software Engineering archive
Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering table of contents
Los Angeles, California, United States
Pages: 99 - 106  
Year of Publication: 1993
ISBN:0-89791-625-5
Also published in ...
Author
Sponsor
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 61,   Citation Count: 11
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

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

ABSTRACT

This paper provides a Safety Checklist for use during the analysis of software requirements for spacecraft and others safety-critical, embedded systems. The checklist specifically targets the two most common causes of safety-related software errors: (1) inadequate interface requirements and (2) discrepancies between the documented requirements and the requirements actually needed for correct functioning of the system. The analysis criteria represented in the checklist are evaluated by application to two spacecraft projects. Use of the checklist to enhance the software-requirements analysis is shown to reduce the number of safety-related software errors.


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
ANSI/IEEE Standard Glossary of Software Engineering Terminology. New York: IEEE, 1983.
 
2
Proceedings of the Berkeley Workshop on Temporal and Real-Ttme Specijcatton. Eds. P. B. Ladkin and F. H. Vogt. Berkeley, CA: International Computer Science Institute, 1990, TR-90- 060.
 
3
J. Cullyer, "Safety-critical Control Systems ," Computing and Control Engineering Journal, Vol. 2, No. 5, Sept 1991, pp. 202-210.
 
4
 
5
 
6
S/W Development Formai Inspections Course. Version H, Sept, 1992, D-8925, Software Product Assurance, Sect. 522, Jet Propulsion Laboratory.
 
7
M. K. Franklin and A. Gabrelian, "A Transformational Method for Verifying Safety Properties in Real-Time Systems," in Proceedings of the ReaLTime Systems Symposium, 1989, pp. 112 -123.
 
8
 
9
E. M. Gray and R. H. Thayer, "Requirements," in Aerospace Software Engineering, A Collection of Concepts, Ed. C. Anderson and M. Dorfman. Washington: AIAA, 1991, pp. 89-121.
10
 
11
 
12
 
13
14
 
15
R. Lutz, "Analyzing Software Requirements Errors in Safety-Critical, Embedded Systems," Proceedings of the IEEE International Symposium on Requirements Engineering, Jan 1993, pp. 126-133.
 
16
 
17
N. Lynch and H. Attiya, "Using Mappings to Prove Timing Properties," MIT/L CS/TM- ll?. b, Dec 1989.
 
18
P. G. Neumann, "The Computer-Related Risk of the Year: Weak Links and Correlated Events," in Proceedings of the Sixth Annual Conference on Computer Assurance. NIST/IEEE, 1991, pp. 5-8.
19
20
 
21

CITED BY  11