• KIPS Transactions on Software and Data Engineering
• /
• v.2 no.12
• /
• pp.823-828
• /
• 2013

In this paper, it will improve in quality to adapt a right test process which is formalized from certification of TMMi Level. To do this, we suggest correlative relation through analyzing associations between TMMi and TPI next based on the previous research[10], which provides the guideline for enhancing test process level with measuring Test maturity model. Also schematize test maturity measurement through refining and improving the previous test maturity correlation metrics[6,8,9]. As one example with limited level, it shows the guideline to improve test process of one testing organization through improved correlation metrics with TMMi and TPI next.

• 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 Academia-Industrial cooperation Society
• /
• v.22 no.1
• /
• pp.87-93
• /
• 2021

As the portion of modern weapons systems equipped with electronic components increases, the presence of embedded software has also increased, subsequently drawing interest in quality management and development methods. Unlike mechanical systems, software is logically intangible, hard to troubleshoot, and hard to reuse, making it hard to utilize limited resources when exposed to failures. The United States had successful results in establishing the Capability Maturity Model (CMM) by studying and applying separate processes for development and quality management of defense software. South Korea has also established, and utilizes, a standard of development and quality management for defense software based on international standards. However, some say those standards still remain at a basic level, and should be modified along with the progress in software. If the standard stays at a basic level, compared to software progression, the cost to reuse and restore resources will increase exponentially. This paper discusses improvement in the test processes for defense software through the Test Maturity Model-integration (TMMi)-derived from the CMM-and presents a blueprint for defense software quality management.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.11 no.2
• /
• pp.1217-1233
• /
• 2017

Effective monitoring and testing during each step are essential for document verification in research and development (R&D) projects. In software development, proper testing is required to verify it carefully and constantly because of the invisibility features of software. However, not enough studies on test processes for R&D projects have been done. Thus, in this paper, we introduce a Test Maturity Model integration (TMMi)-based software field R&D test process that offers five integrity levels and makes the process compatible for different types of projects. The Software & Systems Process Engineering Metamodel (SPEM) is used widely in the software process-modeling context, but it lacks built-in enactment capabilities, so there is no tool or process engine that enables one to execute the process models described in SPEM. Business Process Model and Notation (BPMN)-based workflow engines can be a solution for process execution, but process models described in SPEM need to be converted to BPMN models. Thus, we propose an approach to support enactment of SPEM-based process models by converting them into business processes. We show the effectiveness of our approach through converting software R&D test processes specified in SPEM in a case study.