• Journal of Korea Multimedia Society
• /
• v.21 no.9
• /
• pp.1099-1109
• /
• 2018

Most of the automotive electronic systems are equipped with control software. ISO 26262 standard has been published to prevent unreasonable risk due to E/E system malfunction. And many automotive companies apply ISO 26262 for safe series product. In ISO 26262 standard, the product quality improves through deductive and inductive safety analysis in all processes including system and software development phase. However, there are few studies on software safety analysis than systems. In the paper, we study the software FMEA(Failure Mode Effect Analysis) technique for product quality of vehicular embedded software. And we propose an effective guideline of software FMEA as EPB industrial practice.

• IE interfaces
• /
• v.9 no.3
• /
• pp.249-256
• /
• 1996

The Internet e-mail security software and standards, such as PGP (Pretty Good Privacy) and PEM (Privacy Enhanced Mail), have several limitations that should be overcome for their further applications to the Internet and network environments. In order to improve and reengineer those software, details of the As-Is software processing should be analyzed. One of the possible techniques for software analysis is IDEFO function modeling. Although IDEFO has been mainly used for BPR as one of the industrial engineering techniques, it has been rarely applied to the analysis of software processing and reengineering in computer and software engineering fields. Additionally, no sufficient details of PGP and PEM processing are analyzed in the literature. The objective of this paper is to demonstrate the application of the IDEFO to the systems analysis of the Internet e-mail security software as well as to provide software developers with the basis for software improvements.

• Proceedings of the IEEK Conference
• /
• 2002.06a
• /
• pp.409-412
• /
• 2002

The software complexity model makes an estimated of the product software. For a practice of software managed, need to guideline of the static analysis. Especially, Software complexity model introduced for the estimation of software quantity. In case of measurement the software matrices, its need for us to analysis of software qualify and products. In this paper, we represent that the analysis of function point, control structure and interface, volume matrices in various aspect of switching software. Others, their results utilized similar of project and system development.

• Journal of Information Processing Systems
• /
• v.17 no.5
• /
• pp.960-971
• /
• 2021

As the era of the 4th Industrial Revolution enters, the importance of software safety is increasing, but related systematic educational curriculum and trained professional engineers are insufficient. The purpose of this research is to propose the high priority elements for the software safety education program through needs analysis. For this purpose, 74 candidate elements of software safety education program were derived through contents analysis of literature and nominal group technique (NGT) process with five software safety professionals from various industries in South Korea. Targeting potential education participants including industrial workers and students, an on-line survey was conducted to measure the current and required level of each element. Using descriptive statistics, t-test, Borich needs assessment and Locus for focus model, 16 high priority elements were derived for software safety education program. Based on the results, suggestions were made to develop a more effective education program for software safety education.

• 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 Journal of Korean Institute of Communications and Information Sciences
• /
• v.27 no.10C
• /
• pp.887-901
• /
• 2002

Software management model divided into the software project model and design estimation model, software matrices model, reliability growth model, process improvement model(or process maturity model) etc. Among these software management models, software complexity model make an estimated of the product software. For a practice of software managed, need to guideline of the static analysis of software. Especially, Software complexity model introduced for the estimation of software quantity and program complexity. In case of measurement the software matrices, its need for us to analysis of software quality and products. On the other hand, we known that complexity program include many defects and consuming of source cost. So, we apply to complexity model using of the program complexity, control structure and volume matrices, interface metrics, process complexity metrics method. In this paper, we represent that the analysis of fault data detected during the system test. Also, we analysis of program control structure and interface, volume matrices in various aspect of switching software. Others, their results utilized similar of project and system development.

• Journal of Information Technology Services
• /
• v.17 no.3
• /
• pp.171-189
• /
• 2018

To remove software defects and improve performance of software, many developers perform code inspections and use static analysis tools. A code inspection is an activity that is performed manually to detect software defects in the developed source. However, there is no clear criterion which source codes are inspected. A static analysis tool can automatically detect software defects by analyzing the source codes without running the source codes. However, it has disadvantage that analyzes only the codes in the functions without analyzing the relations among source functions. The functions in the source codes are interconnected and formed a social network. Functions that occupy critical locations in a network can be important enough to affect the overall quality. Whereas, a static analysis tool merely suggests which functions were called several times. In this study, the core functions will be elicited by using social network analysis and DEA (Data Envelopment Analysis) for CUBRID open database sources. In addition, we will suggest clear criteria for selecting the target sources for code inspection and will suggest ways to find core functions to minimize defects and improve performance.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.13 no.6
• /
• pp.305-312
• /
• 2018

Software has been used to develop many functions of the modern weapon systems which has a high mission criticality. Weapon system software must consider multi-threaded processing to satisfy growing performance requirement. However, developing multi-threaded programs are difficult because of concurrency faults, such as unintended data races. Especially, it is important to prepare analysis for debugging the data races, because the weapon system software may cause personal injury. In this paper, we present an efficient framework of analysis, called ConDeWS, which is designed to determine the scope of dynamic analysis through using the result of static analysis and fault analysis. As a result of applying the implemented framework to the target software, we have detected unintended data races that were not detected in the static analysis.

• International journal of advanced smart convergence
• /
• v.9 no.4
• /
• pp.124-131
• /
• 2020

As users of internet-based software applications increase, functional and non-functional problems for software applications are quickly exposed to user reviews. These user reviews are an important source of information for software improvement. User review mining has become an important topic of intelligent software engineering. This study proposes a user review mining method for software improvement. User review data collected by crawling on the app review page is analyzed to check user satisfaction. It analyzes the sentiment of positive and negative that users feel with a machine learning method. And it analyzes user requirement issues through topic analysis based on structural topic modeling. The user review mining process proposed in this study conducted a case study with the a non-face-to-face video conferencing app. Software improvement through user review mining contributes to the user lock-in effect and extending the life cycle of the software. The results of this study will contribute to providing insight on improvement not only for developers, but also for service operators and marketing.

• Electronics and Telecommunications Trends
• /
• v.14 no.4 s.58
• /
• pp.1-9
• /
• 1999

In this paper, we summarize the lessons learned from the applications of the software reliability engineering to a large-scale software project. The considered software is the software system of the TDX-10 ISDN switching system. The considered software consists of many components, called functional blocks. These functional blocks serve as the unit of coding and test. The software is continuing to be developed by adding new functional blocks. We are mainly concerned with the analysis of the effects of these software components to software reliability and with the analysis of the reliability evolution. We analyze the static characteristics of the software related to software reliability using failure data collected during system test. We also discussed a pattern which represents a local and global growth of the software reliability as version evolves. To find the pattern of software of the TDX-10 ISDN system, we apply the S-shaped model to a collection of failure data sets of each evolutionary version and the Goel-Okumoto (G-O) model to a grouped overall failure data set. We expect this pattern analysis will be helpful to plan and manage necessary human/resources for a new similar software project which is developed under the same developing circumstances by estimating the total software failures with respect to its size and time.