Traceability of Software Safety Requirements in Legacy Safety Critical SystemsHow can traceability of software safety requirements be created for legacy safety critical systems? Requirements in safety standards are imposed most times during contract negotiations. On the other hand, there are instances where safety standards are levied on legacy safety critical systems, some of which may be considered for reuse for new applications. Safety standards often specify that software development documentation include process-oriented and technical safety requirements, and also require that system and software safety analyses are performed supporting technical safety requirements implementation. So what can be done if the requisite documents for establishing and maintaining safety requirements traceability are not available?
Document ID
20130011642
Acquisition Source
Kennedy Space Center
Document Type
Conference Paper
Authors
Hill, Janice L. (Florida Univ. Gainesville, FL, United States)
Date Acquired
August 27, 2013
Publication Date
March 22, 2007
Subject Category
Computer Programming And Software
Report/Patent Number
KSC-2007-052
Meeting Information
Meeting: Traceability of Software Safety Requirements in Legacy Safety Critical Systems (TEFSE/GCT''07