Publikationsdatum:
2019-07-13
Beschreibung:
Safety standards contain technical and process-oriented safely requirements. The best time to include these requirements is early in the development lifecycle of the system. When software safety requirements are levied on a legacy system after the fact, a retrospective safety case will need to be constructed for the software in the system. This can be a difficult task because there may be few to no art facts available to show compliance to the software safely requirements. The risks associated with not meeting safely requirements in a legacy safely-critical computer system must be addressed to give confidence for reuse. This paper introduces a proposal for a software safely risk taxonomy for legacy safely-critical computer systems, by specializing the Software Engineering Institute's 'Software Development Risk Taxonomy' with safely elements and attributes.
Schlagwort(e):
Computer Programming and Software
Materialart:
KSC-2007-111
,
3rd IEEE Systems and Software Week SAS/W 2007; Mar 06, 2007 - Mar 08, 2007; Baltimore, MD; United States|31st Annual Software Engineering Workshop; Mar 06, 2007 - Mar 08, 2007; Baltimore, MD; United States
Format:
application/pdf
