• Journal of Multimedia Information System
• /
• 제2권2호
• /
• pp.241-248
• /
• 2015

The safety-critical software in healthcare systems needs more and more perceptive excess among human observation and computer support. It is a challenging conversion that we are fronting in confirming security in healthcare systems. Held in the center are the patients-the most important receivers of care. Patient injuries and fatalities connected to health information technologies commonly show up in the news, contrasted with tales of how health experts are being provided financial motivation to approve the products that may be generating damage. Those events are unbelievable and terrifying, however they emphasize on a crucial issue and understanding that we have to be more careful for the safety and protection of our patients.

• 한국원자력학회:학술대회논문집
• /
• 한국원자력학회 2004년도 요약집 춘계학술발표대회
• /
• pp.228-228
• /
• 2004

• 한국신뢰성학회지:신뢰성응용연구
• /
• 제16권3호
• /
• pp.216-223
• /
• 2016

Purpose: This paper suggests the procedure to enhance the reliability of the software of the medical device that is to cure, treat, diagnose, and prevent a disease or an abnormal health conditions. Methods: After test requirements are classified by the software requirements specification for safety and backgrounds, reliability assessment methods are suggested. Results: Verification and validation for function and safety can be performed whether the medical device software are implemented as intended. Conclusion: Procedure on the static analysis, unit test, integration test, and system test are provided for the medical device software.

• International Journal of Internet, Broadcasting and Communication
• /
• 제15권3호
• /
• pp.219-230
• /
• 2023

With the development of autonomous driving technology, as the use of software in vehicles increases, the complexity of the system increases and the difficulty of development increases. Developments that meet ISO 26262 must be carried out to reduce the malfunctions that may occur in vehicles where the system is becoming more complex. ISO 26262 for the functional safety of the vehicle industry proposes to consider functional safety from the design stage to all stages of development. Specifically at the software level, the requirements to be complied with during development and the requirements to be complied with during verification are defined. However, it is not clearly expressed about specific design methods or development methods, and it is necessary to supplement development guidelines. The importance of analysis and verification of requirements is increasing due to the development of technology and the increase of system complexity. The vehicle industry must carry out developments that meet functional safety requirements while carrying out various development activities. We propose a process that reflects the perspective of system engineering to meet the smooth application and developmentrequirements of ISO 26262. In addition, the safety analysis/verification FMEA processforthe safety of the proposed ISO 26262 function was conducted based on the FCAS (Forward Collision Avoidance Assist System) function applied to autonomous vehicles and the results were confirmed. In addition, the safety analysis/verification FMEA process for the safety of the proposed ISO 26262 function was conducted based on the FCAS (Forward Collision Avoidance Assist System) function applied to the advanced driver assistance system and the results were confirmed.

• 산업공학
• /
• 제25권4호
• /
• pp.416-421
• /
• 2012

One of the activities to improve software quality in ISO 26262 is to apply the design principles for software unit design and implementation mentioned in ISO 26262-6, including the evaluation activity. Before evaluation activity, the tool is compared and selected for evaluation. Because the results of the tool a company selected might have an effect on product quality. In this paper, we suggest the method to compare industrial static analysis tools with some of "MISRA C : 2004 Exemplar Suite" and all lessons learned from comparing tools are described. The result on comparison shows that we just couldn't rely on a result of Static Analysis Tool and need to have another appropriate processes and guidelines to evaluate a software.

• Nuclear Engineering and Technology
• /
• 제41권8호
• /
• pp.1065-1072
• /
• 2009

As the use of software increases at nuclear power plants (NPPs), the necessity for including software reliability and/or safety into the NPP Probabilistic Safety Assessment (PSA) rises. This work proposes an application procedure of software reliability growth models (RGMs), which are most widely used to quantify software reliability, to NPP PSA. Through the proposed procedure, it can be determined if a software reliability growth model can be applied to the NPP PSA before its real application. The procedure proposed in this work is expected to be very helpful for incorporating software into NPP PSA.

• 정보과학회 컴퓨팅의 실제 논문지
• /
• 제23권6호
• /
• pp.335-342
• /
• 2017

원자력발전소 안전-필수 소프트웨어를 개발하고 검증 및 확인을 수행하여 규제기관으로부터 인허가를 받기 위하여 단순하게 문서를 읽고 검토해서는 개발, 구현 및 검증활동에 대한 신뢰성과 안전성 확보에 대하여 정확하게 판단하기가 쉽지 않다. 따라서 이러한 활동, 특히 안전보증 활동이 소프트웨어 결함이 허용가능한 수준인지 판단하기 위한 체계적인 평가기술이 필요하다. 본 연구에서는 원전 디지털 원자로보호계통의 비교논리 프로세서와 동시논리 프로세서를 대상으로 제작자가 수행한 개발 및 검증 결과물의 수준과 깊이를 평가하기 위해 안전진술(Safety case) 방법론을 적용하고 그 결과를 분석한다. 안전진술 방법론 적용으로 기존의 안전입증 방법을 효과적으로 보완할 수 있음을 확인하였다.

• 대한안전경영과학회지
• /
• 제5권2호
• /
• pp.165-174
• /
• 2003

This paper analyzes the competitive power of domestic software industries focusing on the subjective rating of software development process. A survey is conducted to perform subjective evaluation of software development process of his/her company. Comparison between SPICE-experienced companies and non-experienced companies, between domestic companies and companies in developed countries are performed.

• International journal of advanced smart convergence
• /
• 제1권1호
• /
• pp.57-60
• /
• 2012

In this paper, we have performed a safety analysis on an automotive evaporator inspection system. We performed the bi-directional analysis on the manufacturing line. Software Fault Tree Analysis (SFTA) as backward analysis and Software Failure Modes, Effects, & Criticality Analysis (SFMECA) as forward analysis are performed alternately to detect potential cause-to-effect relations. The analysis results indicate the possibility of searching and summarizing fault patterns for future reusability.

• 정보처리학회 논문지
• /
• 제13권6호
• /
• pp.278-283
• /
• 2024

소프트웨어를 구현할 때 인간의 생명에 위협이 될 수 있는 부작용이 발생할 수 있습니다. 그러므로 소프트웨어가 안전에 미치는 영향을 측정하고 위협을 완화하고 예방하기 위한 대안을 만드는 것이 필요합니다. 위협 요소에 의한 영향도 측정을 위하여 소프트웨어 안전 진단을 수행하기 위한 구성요소가 필요하다. 본 논문은 소프트웨어의 위협 요인을 내부 요인과 외부 요인으로 분류하고 이러한 위협 요인의 영향을 정량적으로 시연하는 것을 목표로 합니다.