• Journal of the Korea Society of Computer and Information
• /
• v.23 no.12
• /
• pp.115-122
• /
• 2018

As the proportion of software in weapon systems increases, the impact of software on the overall system is growing. As a result, software quality management becomes important, and related regulations and work manuals for quality assurance activities at each stage in the R & D process are becoming more sophisticated. However, due to the characteristics of the weapon system software that is developed as a customized form for the purpose of a specific mission, there are limits to specifying and definitizing the detailed requirements (upper and lower level) according to various operational concepts during the development process. Due to this, software modification (patch change, shape change due to upgrade, etc.) occurs on account of many defects and performance improvement in the mass production and operation stage after the development is completed. In this study, we analyze the characteristics of these weapon system softwares and propose quality improvement methods based on ISO / IEC / IEEE 29119 test method.

• Journal of the Korea Society of Computer and Information
• /
• v.26 no.11
• /
• pp.101-110
• /
• 2021

The Weapon Control Software performs the function of supporting weapon operation within the Naval Combat System in connection with the Weapon System. As Weapon Control Software depends on an Weapon System, it has the characteristic that software modification is unavoidable with the change in Interface information. Modification of software causes an increase in development costs since it must take verification step such as software reliability test. In this paper, We design the standard architecture of weapon control software to minimize the modification elements of existing weapon control software. For Interface information management, Feature Model were applied to make a division between common factor and variable factor. In addition, Strategy Pattern were applied to improve the software design. Software evaluation test results show that new architecture provides better modifiability and reuse than existing software as well as the cost of development decrease.

• Journal of Applied Reliability
• /
• v.17 no.4
• /
• pp.296-304
• /
• 2017

Purpose: Recent weapon systems in defense have increased the complexity and importance of software when developing multifunctional equipment. In this study, we analyze the accuracy of the proposed software reliability model when applied to weapon systems. Methods: Determine the similarity between software reliability analysis results (prediction/estimation) utilizing data from developing weapon systems and system failures data during operation of weapon systems. Results: In case of a software reliability prediction model, the predicted failure rate was higher than the actual failure rate, and the estimation model was consistent with actual failure history data. Conclusion: The software prediction model needs to adjust the variables that are appropriate for the domestic weapon system environment. As the reliability of software is increasingly important in the defense industry, continuous efforts are needed to ensure accurate reliability analysis in the development of weapon systems.

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

• Journal of Software Engineering Society
• /
• v.28 no.1
• /
• pp.7-12
• /
• 2019

Recently, as the weight of software in the weapon system increases, the quality of the software becomes a very important factor. In order to improve the quality of the weapon system software, DAPA(Defense Acquisition Program Administration) has institutionalized software reliability in Weapon System Software Development and Management Manual. The manual presents specific methods and procedures to improve the weapon system software quality. In order to meet the required reliability test standards specified in the manual, it is necessary to continuously detect and correct defects throughout the entire development period. However, it is difficult to build proper reliability test environment due to the cost of software reliability tools, setting up secured and separated network environment, and etc. Therefore, in this study, we propose an efficient environment construction method for software reliability test of defense industry field in restricted development environment and limited resources.

• Journal of the Korea Society of Computer and Information
• /
• v.27 no.1
• /
• pp.51-59
• /
• 2022

As the weapon system's dependence on software functions increased, software became a key factor in controlling the weapon system. In addition, as software development becomes more important domestically and internationally, software verification becomes an issue. The recent defense market has recognized this point and is demanding a plan for weapon system software maintenance. In this paper, we propose a weapon system software maintenance plan using Automatic Test Equipment. The specific method is to use a simulator to check the software function and identify failure cases. This is an effective way for developers to reduce the Total Corrective Maintenance Time(TCM) of the weapon system by reducing the time it takes to identify failure cases. It has been proven that the proposed Automatic Test Equipment can achieve software maintenance and excellent Maintainability and Operational Availability compared to the existing ones.

• KIPS Transactions on Software and Data Engineering
• /
• v.8 no.7
• /
• pp.265-274
• /
• 2019

The reliability test performed when developing the weapon system software is classified into static test and dynamic test. In static test, checking the coding rules, vulnerabilities and source code metric are performed without executing the software. In dynamic test, its functions are verified by executing the actual software based on requirements and the code coverage is measured. The purpose of this static/dynamic test is to find out defects that exist in the software. However, there still exist defects that can't be detected only by the current reliability test on the weapon system software. In this paper, whether defects that may occur in the software can be detected by static test and dynamic test of the current reliability test on the weapon system is analyzed through experiments. As a result, we provide guidance on improving the reliability test of weapon system software, especially the dynamic test.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.21 no.6
• /
• pp.178-186
• /
• 2020

In the domain of Korean weapon system development, issues about software reliability have become crucial factors when developing a weapon system. There is a process required for weapon system software development and management that includes certain activities required to improve the reliability of software. However, these activities are biased toward static and dynamic analyses of source code and do not include activities necessarily required by the international standard. IEEE std. 1633-2016 defines a process for software reliability engineering and describes software reliability estimation as an essential activity in the process. Software reliability estimation means that collecting defective data during the test and estimating software reliability by using the statistical model. Based on the estimated model, developers could estimate the failure rate and make comparisons with the objective failure rate to determine termination of the test. In this study, we collected defective data and applied reliability estimation models to analyze software reliability in the development of a weapon system. To achieve objective software reliability, we continuously tested our software and quantitatively calculated software reliability. Through the research, we hope that efforts to include activities described by the international standard will be carried out in the domain of Korean weapon system development.

• Journal of the Korean Society of Systems Engineering
• /
• v.8 no.2
• /
• pp.19-25
• /
• 2012

As modern weapon systems have evolved into embedded software systems, the capability to develop, install, and maintain high-quality software products is becoming increasingly valuable in today's competitive aerospace and defense industry. It is desirable, especially for government-contracted projects whose end-users are military personnel, that specific types of software quality elements are assured early during product development; namely, functionality and usability. Motivated by this need to approach improving software quality from a user's perspective, this paper presents a case study that analyzes system-level software integration testing results for a weapon system indigenously developed in the Republic of Korea. Quantitative data, such as software defect ratios and configuration change rates, are computed to observe meaningful trends with respect to functionality - represented by tests designed to verify the system's electrical signal interfaces - and usability, which is evaluated in terms of how often the initial human-computer interface had to be re-designed. Insights gained from these exercises are subsequently presented as a set of "lessons learned" to take into account when developing new software items for complex weapon systems.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.12 no.4
• /
• pp.13-24
• /
• 2016

Defense Acquisition Program Administration's weapon system software development and management guideline specifies the criteria of software reliability tests including static and dynamic tests mainly on C/C++ languages. Recently, Defense Acquisition Program Administration expanded the scope of software reliability test for the various languages including C#, java etc. but specific criteria for them are not established. This study suggests the reliability test procedures and standards on C# programming software in weapon system. For the static test, considering the nature of the C# which depends on .NET framework, this paper introduces applying coding rules recommended by Microsoft Corp. Visual Studio 2012. Block coverage provided by Visual Studio is applied on dynamic tests and the achievement objectives for block coverage according to the software levels(A, B, C) are suggested. Also, the software reliability test procedures and standards proposed by this paper are properly verified through the case study. The result of this study can be used for establishing the specific criteria of the software reliability test for C# programming software in weapon system.