ALBERT

All Library Books, journals and Electronic Records Telegrafenberg

X
feed icon rss

Ihre E-Mail wurde erfolgreich gesendet. Bitte prüfen Sie Ihren Maileingang.

Leider ist ein Fehler beim E-Mail-Versand aufgetreten. Bitte versuchen Sie es erneut.

Vorgang fortführen?

Exportieren
Filter
Sammlung
Schlagwörter
Erscheinungszeitraum
  • 1
    facet.materialart.
    Unbekannt
    Product Engineering Class in the Software Safety Risk Taxonomy for Building Safety-Critical Systems (2008)
    In:  CASI
    Details
    Publikationsdatum: 2019-07-13
    Beschreibung: No abstract available
    Schlagwort(e): Computer Systems
    Materialart: KSC-2008-015 , KSC-2008-015R , 19th Australian Software Engineering Conference (ASWEC 2008); Mar 24, 2008 - Mar 28, 2008; Perth,; Australia
    Format: application/pdf
    Standort Signatur Erwartet Verfügbarkeit
    BibTip Andere fanden auch interessant ...
    NASA TECHNICAL REPORTS
  • 2
    facet.materialart.
    Unbekannt
    Traceability of Software Safety Requirements in Legacy Safety Critical Systems (2007)
    In:  Other Sources
    Details
    Publikationsdatum: 2019-07-13
    Beschreibung: How 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?
    Schlagwort(e): Computer Programming and Software
    Materialart: KSC-2007-052 , Traceability of Software Safety Requirements in Legacy Safety Critical Systems (TEFSE/GCT''07; Mar 22, 2007 - Mar 23, 2007; Lexington, KY; United States
    Format: text
    Standort Signatur Erwartet Verfügbarkeit
    BibTip Andere fanden auch interessant ...
    NASA TECHNICAL REPORTS
  • 3
    facet.materialart.
    Unbekannt
    Software Safety Risk in Legacy Safety-Critical Computer Systems (2007)
    In:  CASI
    Details
    Publikationsdatum: 2019-07-13
    Beschreibung: Safety Standards contain technical and process-oriented safety requirements. Technical requirements are those such as "must work" and "must not work" functions in the system. Process-Oriented requirements are software engineering and safety management process requirements. Address the system perspective and some cover just software in the system 〉 NASA-STD-8719.13B Software Safety Standard is the current standard of interest. NASA programs/projects will have their own set of safety requirements derived from the standard. Safety Cases: a) Documented demonstration that a system complies with the specified safety requirements. b) Evidence is gathered on the integrity of the system and put forward as an argued case. [Gardener (ed.)] c) Problems occur when trying to meet safety standards, and thus make retrospective safety cases, in legacy safety-critical computer systems.
    Schlagwort(e): Computer Programming and Software
    Materialart: KSC-2007-051 , IEEE Southeast Conference 2007, IEEE Region 3 Technical Professional and Student Conference; Mar 24, 2007 - Mar 25, 2007; Richmond, VA; United States
    Format: application/pdf
    Standort Signatur Erwartet Verfügbarkeit
    BibTip Andere fanden auch interessant ...
    NASA TECHNICAL REPORTS
  • 4
    facet.materialart.
    Unbekannt
    A Software Safety Risk Taxonomy for Use in Retrospective Safety Cases (2007)
    In:  CASI
    Details
    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
    Standort Signatur Erwartet Verfügbarkeit
    BibTip Andere fanden auch interessant ...
    NASA TECHNICAL REPORTS
Schließen ⊗
Diese Webseite nutzt Cookies und das Analyse-Tool Matomo. Weitere Informationen finden Sie hier...