• Journal of Information Technology Services
• /
• v.8 no.3
• /
• pp.159-169
• /
• 2009

The issue of method of software testing process implementation has recently been in the spotlight in korea and some vendor make every effort to improve the software testing process through the evaluation of TMMi. The level of software process is at initial level, nevertheless, so the high quality of software is not guaranteed. This paper apply to the TMMi Level2 Assessment criteria of Automobile control software testing process. The test policy and strategy, test planning, test monitoring and control, test design and execution, test environment goal. The result need to emerge development process connection on the test policy and strategy process, test planning process etc. Also, the study analyzed the infra structure to reach the repeated level via key process area. As the result the process implementation in organization suggests the policy development and the implementation activity. Finally, the practical can refer to this paper in order to implementation the software testing process.

• Journal of Information Processing Systems
• /
• v.14 no.3
• /
• pp.607-620
• /
• 2018

The problem surrounding methods of implementing the software testing process has come under the spotlight in recent times. However, as compliance with the software testing process does not necessarily bring with it immediate economic benefits, IT companies need to pursue more aggressive efforts to improve the process, and the software industry needs to makes every effort to improve the software testing process by evaluating the Test Maturity Model integration (TMMi). Furthermore, as the software test process is only at the initial level, high-quality software cannot be guaranteed. This paper applies TMMi model to Automobile control software testing process, including test policy and strategy, test planning, test monitoring and control, test design and execution, and test environment goal. The results suggest improvement of the automobile control software testing process based on Test maturity model. As a result, this study suggest IT organization's test process improve method.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.22 no.6
• /
• pp.784-796
• /
• 2019

As the size and complexity of software increases, it is important to ensure the quality of software through testing. Many organizations refer to international standards or test process models to improve the quality of software through establishing a systematic test process. However, these standards and process models provide general processes that do not reflect the characteristics of the domain or the organization's test policies and strategies. To establish a test process that reflects the characteristics of the organization, test policies and strategies based on the organization's quality objectives and the organizational and domain characteristics should be reflected. This study proposes specific methods for eliciting activities and information to establish organizational software test policies and strategies that are essential to establishing a test process that reflects the characteristics of the organization and the system.

• Journal of Internet Computing and Services
• /
• v.20 no.6
• /
• pp.37-46
• /
• 2019

A test plan is a high level document detailing objectives, processes, schedules and so on for verifying a developed software. And a test strategy, a component of a test plan, is about how to test software products to guarantee its quality and find bugs in the software in advance. Therefore, establishing effective and suitable test strategies is important for elaborating test processes. However, these tasks are difficult for project managers who write a test plan if they were not trained well in software test processes. And mis-designed test strategies will also mislead entire testing behaviors that testers would do. As a result, there would be a low quality software product in the end. To solve this problem, we propose a new test strategy reuse technique in this paper. By utilizing test plans of already completed software development projects, we lead test planer to reuse suitable and effective test strategies which were used in previous projects. To do so, we evaluate existing test strategies by utilizing ISO/IEC 25010 quality model for evaluating the suitability of test strategies and also use effectiveness metrics for test strategies. And from these evaluations, we predict completeness of new test plan that is written by reused test strategies. It can help the project manager to write an appropriate test plan for the quality characteristics which are selected as objectives for testing and software product. We show the possibility of our approach by implementing a prototype into the existing framework in a case study.

• Journal of the Korean Society of Systems Engineering
• /
• v.2 no.1
• /
• pp.18-23
• /
• 2006

The purpose of this study and report is to provide, to the MND, an independent cost analysis of modernizing software of F-16 fighter fleets to support the use of several weapon system options, including JDAM, AIM-9X and HARM Targeting System etc. The study analyzed each options with software sizing, software cost, enabling hardware cost, flight test cost, system engineering cost, and 3 strategies. And the study proposed and analyzed some alternative strategies: strategy1 is to modernize software only within existing electronic processing capability; strategy2 is a full upgrade of weapons avionics with plug compatible electronics; strategy3 is an approach defined to mirror the USAF Common Configuration Implementation Approach (CCIP). The recommended alternative is strategy2.

• Proceedings of the KSRS Conference
• /
• 2007.10a
• /
• pp.175-178
• /
• 2007

COMS (Communication Ocean Meteorological Satellite) is the geostationary satellite being developed by Korea Aerospace Research Institute for multi-mission: experimental communication, ocean monitoring and meteorological observations. The COMS operation is controlled by the on-board software running on the spacecraft central computer. The software is written in ADA language and developed under the software life cycle: Requirement analysis, Design, Implementation, Component test and Integration test. Most functional requirements are tested at component level on a software component testing tool, ATTOL. ATTOL provides a simple way to define the test cases and automates the test program generation, test execution and test analysis. When two or more verified components are put together, the integration test starts to check the non-functional requirements: real-time aspect, performance, the HW/SW compatibility and etc. This paper introduces the COMS on-board software and explains what to test and how to test the on-board software at component level using ATTOL.

• Proceedings of the KSRS Conference
• /
• 2007.10a
• /
• pp.460-463
• /
• 2007

COMS (Communication Ocean Meteorological Satellite) is the geostationary satellite being developed by Korea Aerospace Research Institute for multi-mission: experimental communication, ocean monitoring and meteorological observations. The COMS operation is controlled by the on-board software running on the spacecraft central computer. The software is written in ADA language and developed under the software life cycle: Requirement analysis, Design, Implementation, Component test and Integration test. Most functional requirements are tested at component level on a software component testing tool, ATTOL. ATTOL provides a simple way to define the test cases and automates the test program generation, test execution and test analysis. When two or more verified components are put together, the integration test starts to check the non-functional requirements: real-time aspect, performance, the HW/SW compatibility and etc. This paper introduces the COMS on-board software and explains what to test and how to test the on-board software at component level using ATTOL.

• 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 Information Technology Applications and Management
• /
• v.27 no.6
• /
• pp.101-116
• /
• 2020

This study attempts to derive critical success factors and prioritize activities for implementing the automation of software test. Software testing proceeds in five steps of test plan, test case design, test scripting & test environment setup, test execution & evaluation, and test closure. From the literature, twenty influence factors in the five steps were identified. Focus Group Interviews with ten experts in software testing selected fourteen factors on the basis of importance and feasibility. Some factors were further divided to clarify their meanings and the number of influence factors finally became twenty one. A survey on the influence factors was conducted with 75 IT professionals. An importance-feasibility analysis was applied to the survey responses and classified the influence factors into four groups of essential factors, critical factors, low priority factors, and minimal factors. Essential factors include objectives for test automation, strategies for test automation, test automation training, test automation education, setting up test automation environment, setting up test environment, test automation tool selection. Critical factors include management's continued support, management's continued interest, role of automation engineers, and skills of automation engineers. This result suggests that a lot of efforts should be put into SW test plan for the successful SW test automation and SW automation should proceed in consideration with the priorities and resource consumption.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 2004.05a
• /
• pp.607-610
• /
• 2004

It is still not sufficient for the famous embedded software test methods such as Finite State Machine, Software Cost Reduction and model coverage based test case generation, to pinpoint where bugs hang around and to figure out what makes the bugs. A new approach to ameliorate the drawbacks is proposed in this paper. In the approach, we define a generic model for embedded software. And we also define failure mechanism for embedded software, and a way to generate test cases based on it.