• KIPS Transactions on Software and Data Engineering
• /
• v.7 no.7
• /
• pp.249-258
• /
• 2018

The importance of software in military weapon systems is increasing, and the software structure is becoming more complicated. We therefore must thoroughly verify its reliability. In particular, the defects from the interaction of the software components that make up the weapon system are difficult to prevent only with static testing and code coverage level dynamic testing. In this paper, we classify dynamic software defect types and analyze the issues reported in the Open Source Software (OSS) used in the US department of defense weapon systems. The dynamic defects classified in this paper usually occur after integration, and it is difficult to reproduce and identify the cause. Based on this analysis, we come to the point that the software integration test must be enhanced in order to verify the reliability of the weapon system.

• Journal of the Korea Society of Computer and Information
• /
• v.14 no.11
• /
• pp.123-134
• /
• 2009

As the embedded software for weapon system is embossed, the information management system is required to service and manage the technical information of embedded software systematically. But the technical information documents are managed by its own organization separately, it's hard to service the information and share it with anyone who need. In this paper, to manage the embedded software information systematically, we analyze the information management system built in 2004 and the defence law/rule. Also we distinguish the software information from defence laws to manage systematically and analyze the requirements of the information system. Based on these, we suggest implementing the management system to increase efficiency of managing the weapon embedded software information. Through this, we can improve the utilization and reusability of the weapon embedded software.

• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.36 no.4B
• /
• pp.332-345
• /
• 2011

As weapon systems are evolving into more advanced and complex ones, the role of the software is becoming heavily significant in their developments. Particularly in the war field of today as represented by the network centric warfare(NCW), the reliability of weapon systems is definitely crucial. In this context, it is inevitable to develop software reliably enough to make the weapon systems operate robustly in the combat field. The reliability engineering activities performed to develop software in the domestic area seem to be limited to the software reliability estimations for some projects. To ensure that the target reliability of software be maintained through the system's development period, a more systematic approach to performing software reliability engineering activities are necessary from the beginning of the development period. In this paper, we consider the software reliability in terms of the development of a weapon system as a whole. Thus, from the systems engineering point of view, we analyze the models and methods that are related to software reliability and a variety of associated activities. As a result, a process is developed, which can be called the software reliability engineering process for weapon systems (SREP-WS), The developed SREP-WS can be used in the development of a weapon system to meet a target reliability throughout its life-cycle. Based on the SREP-WS, the software reliability could also be managed quantitatively.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.23 no.4
• /
• pp.389-398
• /
• 2020

Test cases in the existing weapon system software were created manually by the tester analyzing the test items defined in the software integration test procedure. However, existing test case generation method has two limitations. First, the quality of test cases can vary depending on the tester's ability to analyze the test items. Second, excessive time and cost may be incurred in writing test cases. This paper proposes a method to automatically generate test cases based on the requirements model and specifications to overcome the limitations of the existing weapon system software test case generation. Generate test sequences and test data based on the use case event model, a model representing the requirements of the weapon system software, and the use case specification specifying the requirements. The proposed method was applied to 8 target models constituting the avionics control system, producing 30 test sequences and 8 test data.

• The KIPS Transactions:PartD
• /
• v.13D no.7 s.110
• /
• pp.923-930
• /
• 2006

In this paper we design the system test model for the weapon system embedded software based on the Time Factor Method(TFM) considering time factors and suggest the results through the case study. For doing this, we discuss the features, system tests and the object-oriented model based UML notations of the weapon system embedded software. And we give a test method considering time factors, a measuring method to time factors, and a test case selection algorithm as an approach to the TFM for designing the system test model. The TFM based system test model consists of three factors (X, Y, Z) in the weapon system embedded software. With this model, we can extract test cases through the selection algorithm for a maximum time path in 'X', identify the objects related to the Sequence Diagram in 'Y' and measure the execution time of each objects which is identified by the Timing Diagram in 'Z' Also, we present the method of extracting the system test cases by applying the proposed system test model to the 'Multi-function missile defense system'.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.22 no.3
• /
• pp.310-315
• /
• 2021

In the case of weapon systems used by the military, defense standards are applied for economical and efficient procurement, management, and maintenance. Defense specifications are documents describing procedures and methods for determining whether technical requirements for products and services are consistent and apply to the production of weapon systems, quality assurance, and configuration management. Software is also subject to defense specifications, and is documented and managed in the same way as other defense specifications. Sometimes it happened to be standardized without some(or all) software. In this case, a competitive contract is impossible and it may affect the quality of weapon systems because the manufacturer arbitrarily changes the software without prior approval. So, software standardization is required, but it is very difficult to verify for firmware installed in hardware. This paper proposed a verification method for g software standardization, and we expect it will contribute to the efficient production and quality assurance of weapon systems.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.22 no.5
• /
• pp.387-393
• /
• 2021

This study aimed to improve the software quality in weapon systems by applying ISO/IEC 25023 to the software engineering process. The software engineering process in weapon systems manages the Software Quality Requirement but has restrictively improved the software quality. Software quality items are already defined and used for software engineering processes in weapon systems, but they are defined inconsistently according to individual software development cases. Thus, the methods of quantifying software quality are different, even though the same software quality is defined. In addition, the software quality has been managed differently. The major problems of software engineering processes in weapon systems are the unclear definition of the software quality requirements and the absence of quantifying software quality standards. ISO/IEC 25023 is composed of eight quality characteristics and thirty-one sub-characteristics. ISO/IEC 25023 provides measurement functions that can quantify the software product quality based on its characteristics. To improve the software quality further, the measurement functions in ISO/IEC 25023 are suggested to quantify and manage software quality for software engineering processes in weapon systems. The expected effects of this study were analyzed.

• The Journal of the Korea institute of electronic communication sciences
• /
• v.17 no.4
• /
• pp.663-670
• /
• 2022

This study presents the method for integrating the software assets acquired before the weapon system software reliability test was not formed in the weapon system software development and management manual through JTDLS Batch II case. This paper describes the problems for applying manual's direction to JTDLS Batch II project, and decisions and expected effects.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.22 no.1
• /
• pp.285-293
• /
• 2021

This study evaluated the process of software quality assurance about the initial product in a weapon system. The software quality assurance of the initial product was insufficient before this study. Therefore, the process of the software quality assurance about the initial product in a weapon system is suggested. The process has three parts. First, the completeness of computer files, such as source code and execute files, were checked. Second, the suitability of the software technical data was checked. Finally, the connectivity of software technical data and the Korean defense specification were assessed. Overall, there is a need to toughen the software quality assurance in the research and development step and achieve early stabilization of mass production by preventing the problems that prevent the production of a product due to the insufficient software technical data.

• The KIPS Transactions:PartD
• /
• v.13D no.5 s.108
• /
• pp.717-724
• /
• 2006

The cost estimation of software is getting more important as the portion of software is increasing in acquiring weapon systems. However, the cost estimation of embedded software in a weapon system follows the cost estimation method for general purpose softwares and uses the PRICE S model as a tool. However, any validation result of the estimated cost through an evaluated software size is not well known. Hence, we propose an approach to estimate the cost through evaluating the embedded software site in weapon systems. In order to achieve our research goal, we evaluate the software size of using the line of codes and function points which are produced by the PRICE S model. Finally, we compare the estimated cost data the actual cost data provided by the production company. As a result, we propose an approach to estimate the size and the cost of embedded software in weapon systems which are not easy to estimate objectively. We also expect that the Proposed approach is used for the cost validation and negotiation in the acquisition of weapon systems in the future.