• Proceedings of the Safety Management and Science Conference
• /
• 2001.05a
• /
• pp.77-81
• /
• 2001

Burn-in is a test procedure to find and eliminate the inherent initial failure of a product during or at the final stage of production process. Software testing is the validation and verification process which is used to cut off the faults from a software. The two have the common function and objective of "debugging". This article summarizes some significant models on the optimal hardware and software burn-in time, and provides the relevant paper lists. The need for the development of the unified burn-in policy of a hardware-software system is addressed.addressed.

• Journal of the Korea Society of Computer and Information
• /
• v.10 no.3 s.35
• /
• pp.89-99
• /
• 2005

The testing time and cost of developed software can be reduced by automation of the whole or part of testing process. Since the testing automation tools to be used currently have been developed without their interoperability, test case information such as test procedures, test data, and expectation of test results generated at the stage of test execution cannot be shared and reused in other testing automation tools, In order to reduce testing time and cost, in this thesis, we have proposed a software testing automation framework which makes it possible to share and reuse the test case information generated in testing process. To prove the availability and effectiveness of proposed testing automation framework, three testing automation tools that are available in current market were experimented by the test scenario. As a result of experiment, the testing time and cost could be reduced by sharing and reusing the test case information in software testing automation framework.

• Journal of the Korean Society for Aviation and Aeronautics
• /
• v.15 no.1
• /
• pp.61-67
• /
• 2007

The importance and cost of avionics system in the integration of an aircraft is continuously increasing. And we can expect enlarged software portion in the system integration for the more intelligent, reliable, and automated avionics system. Both military and commercial avionics community have moved toward commercial-off-the-shelf(COTS) equipment and open systems architecture not only to increase affordability but also to reduce acquisition cost, shorten development time and risk. The same concept is applied in developing avionics test system used for the avionics system integration test. In this paper, we present important topics in the development of avionics system including real-time operating system, interconnect data bus, software development methodology, software development process, and system integration test.

• Journal of the Semiconductor & Display Technology
• /
• v.16 no.3
• /
• pp.71-77
• /
• 2017

As the automobile industry has shifted to software, the Automotive SPICE standard has been established to ensure efficient product development process and quality. In the assessment model, the HIS Scope is the minimum standard for small and medium automotive electric companies to meet OEM requirements. However, in order to achieve the HIS Scope, the output of each process stage that meets the verification criteria of Automotive SPICE must be created. In particular, the test phase takes a lot of resources, which is a big burden for small and medium-sized companies. In this paper, we propose a methodology for creating test cases of software integration test phase based on UML sequence diagram, which is a software design phase of Automotive SPICE HIS Scope, by applying behavior model based testing method. We also propose a tool chain for automating the creation process. This will reduce the resources required to create a test case.

• 한국IT서비스학회:학술대회논문집
• /
• 2003.11a
• /
• pp.713-721
• /
• 2003

The time to market and productivity of embedded system needs a quality measurement process management of embedded software. But, defect management without preemptive analysis or prediction is not useful for quality measurement process management. This subject is focused on the defect that is one of the most important attributes of software measure in the process. Defining of defect attribute and quality measurement process management is according to understanding of embedded sw characteristics and defect data. So, this study contributes to propose the good method of the quantitative based on defect management in the test phase of sw lifecycle.

• The KIPS Transactions:PartD
• /
• v.13D no.2 s.105
• /
• pp.259-270
• /
• 2006

Because a medical embedded software is the software that control the medical devices that are relevant to a human life, it requires high qualify level. It is requires to develop and apply the quality test module that suitable for the requirements to meet the high quality requirements of the medical embedded software. Also, it needs to develop the process that complement the quality defects of software by feedback of the test result. In this study, we developed test module and quality inspection table which can test medical embedded software and produce result based on ISO/IEC 12119.

• Journal of the Korea Society of Computer and Information
• /
• v.9 no.1
• /
• pp.17-23
• /
• 2004

Testing tools help software developers and test engineers to automate a part or the whole of test process and reduce the time and cost of software test. However. no automatic tools meet a variety of test requirements with various domains In this paper, we suggest a categorical taxonomy of automatic testing tools and analyze numerous commercial testing tools on its basis. Then we propose a development roadmap of software automatic testing tools. As a result of those analysis. we try to understand the complementary relations of the testing tools and seek for the direction of further development of the testing tools.

• Convergence Security Journal
• /
• v.7 no.2
• /
• pp.49-55
• /
• 2007

Software failure time presented in the literature exhibit either constant, monotonic increasing or monotonic decreasing. For data analysis of software reliability model, data scale tools of trend analysis are developed. The methods of trend analysis are arithmetic mean test and Laplace trend test. Trend analysis only offer information of outline content. From the subdivision of this analysis, new attemp needs the side of the quality control. In this paper, we discuss process capability analysis using process capability indexs. Because of software failure interval time is pattern of nonnegative value, instead of capability analysis of suppose to normal distribution, capability analysis of process distribution using to Box-Cox transformation is attermpted. The used software failure time data for capability analysis of process is SS3, the result of analysis listed on this chapter 4 and 5. The practical use is presented.

• Journal of Korean Society for Quality Management
• /
• v.13 no.2
• /
• pp.61-65
• /
• 1985

The quality of a final SOFTWARE PACKAGE depends on many complicated factors in the software development process. This paper describes ststistical methods for establishing relationships between final quality and development process factors. The final software quality is represented by the number of errors through the system test phase. The data presented here were gathered during the course of a real IS-month development project. Regression theory is used for data analysis. Some of the interesting results include the observation that specification changes during the development process have an adverse effect on final software quality.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.18 no.3
• /
• pp.633-652
• /
• 2024

Software testing is an important phase as it ensures the software quality. The software testing process comprises of three steps: generation, execution, and evaluation of test cases. Literature claims the usage of single and multiple 'Unified Modeling Language' (UML) diagrams to generate test cases. Using multiple UML diagrams increases test case coverage. However, the existing approaches show limitations in test case generation from UML diagrams. Therefore, in this research study, we propose an approach to generate the test cases using UML State Chart Diagram (SCD), Activity Diagram (AD), and Sequence Diagram (SD). The proposed approach transforms UML diagrams into intermediate forms: SCD Graph, AD Graph, and SD Graph respectively. Furthermore, by integrating these three graphs, a System Testing Graph (STG) is formed. Finally, test cases are identified from STG by using a traversal algorithm such as Depth First Search (DFS) that is an optimization method. The results show that the proposed approach is better compared to existing approaches in terms of coverage and performance. Moreover, the generated test cases have the ability to detect faults at the unit level, integration, and system level testing.