• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 2003.11a
• /
• pp.297-300
• /
• 2003

This paper considers formal verification methods for enhancing software reliability. The formal method verifies that a software is correctly implemented according to its specification by using a mathematical formalism. This paper presents a partial survey on the formal methods and discusses possible applications for the improved software implementation. Finally, some topics are remarked as further studies.

• Proceedings of the KSR Conference
• /
• 2007.05a
• /
• pp.1000-1007
• /
• 2007

Recently, many critical control systems are developed using formal methods. When software applied to such systems is developed, the employment of formal methods in the software requirements specification and verification will provide increased assurance for such applications. Earlier error of overlooked requirement specification can be detected using formal specification method. Also the testing and full verification to examine all reachable states using model checking to undertake formal verification are able to be completed. In the comparison of other formal specification methods, we choose the Z formal language for applying to the train control system. Using Z is able to realize higher correctness in the requirement specification, and we propose the Statemate of the best solution in formal verification tools for the system modeling and verification. The Statemate makes it possible to prove thoroughly the system execution from the simple graphical modeling of the complicated train control system. Then we can expect that the model-based formal method combining Z with Statemate will be utilized widely for the railway systems due to various strong points.

• Electronics and Telecommunications Trends
• /
• v.34 no.1
• /
• pp.142-153
• /
• 2019

In this paper, we focus on the process of using open source software (OSS) and factors that should be considered when using project-based OSS. We also elaborate on how to avoid using OSS licenses in an OSS-based technology development process, why dual OSS licenses and security threats should be avoided, and the method of notification after use. In addition, the OSS license verification method and environment are described in the course of project development. In the verification method, the OSS license used for technology development in the course of project execution is validated in advance by the person who decides whether or not to use the OSS, and then additional verification using the tool after technology development. It is expected that this paper will be helpful for establishing the OSS usage consideration and the license verification procedure, and environment in the future.

• Journal of Advanced Navigation Technology
• /
• v.19 no.1
• /
• pp.15-21
• /
• 2015

WA-DGNSS is a system to service for users using a satellite which received correction data from ground station that calculates the relative errors of the tracked GNSS signals and sends to a satellite. Users are guaranteed the reliability of the GNSS signal and the accuracy of positioning. ICAO recommends the application of WA-DGNSS for the airplane taking off and landing process. In this paper, we suggests methods to verify of the pre-developed WA-DGNSS reference software constituting modules and an integration test process refer to the RTCA DO-278 which is a document for the development process of an aeronautics software. Also, we statistically verified the reference software test through our methods. And then, we confirmed to performance the function of the reference software properly.

• KIPS Transactions on Software and Data Engineering
• /
• v.4 no.1
• /
• pp.1-8
• /
• 2015

Safety critical systems require exhaustive verification of safety properties, because even a single corner-case fault can cause a critical safety failure. However, existing verification approaches are too costly in terms of time and computational resource required, making it hard to be applied in practice. In this paper, we implemented a tool for minimizing the size of the verification target w.r.t. verification properties to check, based on program slicing technique[1]. The efficacy of program slicing using our tool is demonstrated in a case study with a verification target Trampoline[3], which is an open source automotive operating system compliant with OSEK/VDX[2]. Experiments have shown enhanced performance in verification, with a 71% reduction in the size of the code.

• Journal of Software Engineering Society
• /
• v.11 no.1 s.37
• /
• pp.3-21
• /
• 1998

• Proceedings of the Korean Society for Quality Management Conference
• /
• 2004.04a
• /
• pp.114-119
• /
• 2004

Software verification and validation(V&V) is a means to develop high-quality software and assure safety and reliability for software. Also, we can achieve the desired software quality through systematic V&V activities. The software to be applied safety critical system like nuclear power plants is required to setup the V&V methodology that comply with licensing requirements for nuclear power plants and should be performed V&V activities according to it. In this paper, we classified safety-critical, safety-related and non-safety for software according to safety function to be peformed and define V&V activities to be applied software grade. Also, we defined V&V activities, procedures and documentation for each phase of software development life cycle and showed techniques and management to perform V&V. Finally, we propose the V&V framework to be applied software development of SMART(System-integrated Modular Advanced ReacTor) MMIS (Man-Machine Interface System) and to comply with domestic licensing requirements.

• 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.

• Proceedings of the IEEK Conference
• /
• 2000.11b
• /
• pp.204-207
• /
• 2000

Verification is one of the most critical and time-consuming tasks in today's design process. This paper describes the basic idea of Co-verification and the environment setup for the design of DVD Servo with TeakLite DSP core by using Seamless CVE, Hardware/software Co-verification too1.

• Journal of Information Processing Systems
• /
• v.14 no.2
• /
• pp.309-321
• /
• 2018

In the conventional computing environment, users use only a small number of software systems intensively. So it had been enough to check and guarantee the functional correctness and safety of a small number of giant systems in order to protect the user systems and their information inside the systems from outside attacks. However, checking the correctness and safety of giant systems is not enough anymore, since users are using various software systems or web services provided by unskilled developers. To prove or guarantee the safety of software system, a lot of research has been conducted in diverse areas of computer science. We will discuss the on-going approaches for guaranteeing or verifying the safety of software systems in this paper. We also discuss the future research challenge which must be solved with better solutions in the near future.