• Journal of Multimedia Information System
• /
• v.2 no.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.

• Proceedings of the Korean Nuclear Society Conference
• /
• 2004.05a
• /
• pp.228-228
• /
• 2004

• Journal of Applied Reliability
• /
• v.16 no.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
• /
• v.15 no.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.

• IE interfaces
• /
• v.25 no.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
• /
• v.41 no.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.

• KIISE Transactions on Computing Practices
• /
• v.23 no.6
• /
• pp.335-342
• /
• 2017

In the verification and validation procedures regarding the safety-critical software of nuclear power plants for the attainment of the requisite license from the regulatory body, it is difficult to judge the safety and dependability of the development, implementation, and validation activities through a simple reading and review of the documentation. Therefore, these activities, especially safety assurance activities, require systematic evaluation techniques to determine that software faults are acceptable level. In this study, a safety case methodology is applied in an assessment of the level and depth of the results of the development and validation of a manufacturer in its targeting of the bistable processor of a digital reactor protection system, and the evaluation results are analyzed. This study confirms the possibility of an effective supplementation of the existing safety demonstration method through the application of the employed safety case methodology.

• Journal of the Korea Safety Management & Science
• /
• v.5 no.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
• /
• v.1 no.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.

• The Transactions of the Korea Information Processing Society
• /
• v.13 no.6
• /
• pp.278-283
• /
• 2024

When implementing software, there can be side effects that pose a threat to human life. Therefore, it is necessary to measure the impact of software on safety and create alternatives to mitigate and prevent threats. To conduct a software safety assessment to measure the impact of threat factors, the following components are necessary. This paper aims to classify the threat factors of software into internal and external factors and quantitatively demonstrate the impact of these threat factors.