Safety Critical Software: Status Report

소개글

Safety-Critical Software: Status Report - Patrick R. H. Place and Kyo C. Kang
논문 요약 후 발표자료 입니다.
파워포인트 디자인 요소만을 사용하셔도 좋습니다.

목차

1. Introduction
1.1 Purpose of this report
1.2 Requirements Engineering and Safety
1.3 Background
2. Comments on software safety
2.1 Safety is a System Issue
2.2 Safety is Measured as Risk
2.3 Reliability is not Safety
2.4 Software need not be Perfect
2.5 Safety Software is Secure and Reliable
2.6 Software should not replace Hardware
2.7 Development Software is also Safety-Critical
3. hazard analysis techniques
3.1 Hazard Identification
3.2 Hazard Analysis
4. Summary

본문내용

+ To bring together concepts necessary for the development of software
in safety-critical systems.

+ To know the role of safety-critical software in requirements engineering.

+ To deal of recent activity in the application of formal methods to safety-
critical software development.

+ To introduce the classes of formal methods and how they may be used.

1.2 Requirements Engineering and Safety

+ The expensive required development techniques
+ A limited number of the staff

+ Minimize the proportion of the developed system according
to safety standard

+ The Requirements engineer has to manipulate the requirements
to minimize the safety-critical subsystems while maintaining
an overall required level of safety for the entire system

참고 자료

Software Engineering, The Development Process (Practitioners)
by Richard H. Thayer, Mark J. Christensen
Publisher: Wiley-IEEE Computer Society Pr; 3 edition (November 11, 2005)