• 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 Korean Society of Systems Engineering
• /
• v.14 no.2
• /
• pp.83-88
• /
• 2018

Software has become an integral part of almost any system, triggered by the ever-growing demand for automation and artificial intelligent throughout engineering domains. The complexities of software-centric systems are also increasing, which make software test efforts become essential in software development projects. In this study, we applied systems engineering methodology in generating software test cases. We found out the similarities between requirements analysis and traceability concept of systems engineering and test specification contents of software test. In terms of acceptance test, software test cases could be considered as validation requirements. We also suggested a method to determine test order using a SysML modeling tool.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.7 no.3
• /
• pp.135-142
• /
• 2012

The Quality of embedded system depends on the embedded software. As the complexity and the size of embedded software have been increasing, it is more likely that the software may include faults, and the reliability and stability issues are getting more important. In this paper, we propose a remote test tool for software based on VxWorks by using fault injection method. The test tool consists of test server and test client for testing on the cross development environment. The test server operates in the host system and user can not only test but also monitor the software by using it. The test client operates in the target system and it controls kernel objects and sends the input data into the software when receiving the control and data from the test server. We developed the prototype software and demonstrated the ability of testing software robustness by injecting faults.

• Proceedings of the KSRS Conference
• /
• 2008.10a
• /
• pp.84-87
• /
• 2008

ATTOL is a software unit testing tool produced by the ATTOL Testware SA in France. It automates the entire software unit testing process: test plan template and test program generation, test program execution, test result analysis and test report generation. ATTOL is suited for the development of embedded software as it allows programmers to operate in native and cross development environments. Particularly, it is used for the development of the flight software which is embedded in the Communication Ocean Meteorological Satellite (COMS). As the flight software is mission-critical, it requires the strict software quality and high testing constraints. The flight software of COMS is verified by ATTOL in native and cross platforms. In 2002, ATTOL was taken over by the IDM Rational Software and has been supplied with the name of Test RealTime (TestRT). The test process of TestRT becomes different from that of ATTOL as TestRT provides the new functionalities that were absent from ATTOL. TestRT provides the new features in the test script language, as well. In this paper, we compare the test process of ATTOL to TestRT With an example of COMS and explain what has been changed in the test script language.

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

• 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 Advanced Information Technology and Convergence
• /
• v.8 no.2
• /
• pp.111-118
• /
• 2018

Information communication authority module software contains various functions and services. A software test is the only acceptance test step. Recently, however, all development steps have become important. In particular, the software acceptance step is very high, and a study of the effective use of limited time and resources on acceptance step is needed. This study examined the efficiency of the Test Design Technique for Software Test. The proposed Test Design process was applied to the domain systems of info-communication and the degree of improvement was measured. This paper establishes Software Test design process Infrastructure based on the developed software.

• Proceedings of the KSR Conference
• /
• 2004.06a
• /
• pp.1477-1478
• /
• 2004

Science the change of development methods and environment of the software is rapidly kept going in industry, previous manual test methods will not be able to guarantee the quality of software. Therefore the software test automation tools is being developed actively. And many of the tools which is reliable is applied and used in domestic organizations. Indirect test techniques currently are used For the improvement of the software quality, such as formal specification and design, structural programming. And also the various do direct test techniques are used to the measurement of software quality through the fault detection and modification, such as black box, which box and test automation tools. In this survey, the software test automation tools which predicate and access the software quality at the software development phase for the improvement of the software quality should be introduced.