• 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 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 the Korea Society of Computer and Information
• /
• v.15 no.12
• /
• pp.189-196
• /
• 2010

Domestic software test maturity level is the most Level 2 below based on TMMi. The first condition of enhancement of test maturity is that know exactly what the current maturity. There is no Level 1 definition in TMMi, but even the same level of maturity level of an organization, there are clear differences. In this study, grasp a maturity level of Level 1 organization, while less effort to improve in Level organization, the ways to achieve Level 2 is presented. Sub practices with dependencies in Level 2 is grouped with the corresponding process areas and define a Level 1 newly at 3 phases. If sub practices with dependencies are tied and improve a process, it will produce the effect which attains the practices all at once. Verify the adequacy of three phases, as a result, an organization clearly identify Test Maturity Level 1, we know that the organization can set specific improvement goals and direction.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2015.04a
• /
• pp.546-548
• /
• 2015

최근에는 자동차 전장용 소프트웨어 결함으로 인한 피해로 자동차 리콜 사태가 일어나는 것을 종종 볼 수 있다. 소프트웨어 검사와 TMMi 프로세스를 전장용 소프트웨어에 이용한다면 소프트웨어 결함을 줄이며 사고 발생률 역시 감소될 수 있다. 전장용 소프트웨어에 이를 적용해 볼 때, 검사 방법에 적합한 방향으로 검사 프로세스를 개선할 수 있으며, 고품질 소프트웨어 또한 구현할 수 있다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2012.11a
• /
• pp.1504-1506
• /
• 2012

소프트웨어 개발 생태계의 변화에 따른 소프트웨어 개발의 다양화 및 Time-to-Market으로 인해 사용자들이 요구하는 소프트웨어 품질수준이 높아졌다. 그러나, 소프트웨어 품질을 향상하는 여러 가지가 방법의 하나로 완벽한 테스트를 통해 가능하다. 하지만, 완벽한 테스트를 수행하는 것은 불가능하다. 이를 해결하기 위해 정형화된 올바른 테스트 프로세스를 적용하여 품질을 높이고자 한다. 본 논문에서는 조직의 테스트 성숙도 수준을 평가할 수 있는 TMMi와 테스트 프로세스를 개선할 수 있는 TPI next의 매핑을 기반으로 조직의 테스트 성숙도 측정과 함께 테스트 프로세스 수준 향상을 위한 가이드를 제공하고자 한다. 이를 위한 절차로 TMMi(level2)와 TPI next의 매핑, 비/공통 요소 추출을 통해 조직의 테스트 프로세스 개선을 위한 가이드를 제공하고자 한다.

• Journal of KIISE:Software and Applications
• /
• v.41 no.8
• /
• pp.533-544
• /
• 2014

The hardware-based software has been loaded in almost all industrial fields including the embedded system field. As it is increasingly important to control product quality, the more businesses are expending great quality cost. However, most domestic corporations in Korea are bent on spending more money solving problems caused by poor quality rather than prevention of quality loss cost. Therefore, it's time to improve to use quality prevention cost efficiently. As for this, there has been a growing interest in controlling quantitative quality, but the managing activities for quantitative quality require a high maturity process, belonging to Level 4 and 5. So it is necessary that statistical quality control activities should be fulfilled. This study introduces various measures to build up quality control among the process areas of TMMi Level 5 to help establish the high maturity test processes of statistical quality control.

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

• Proceedings of the Korean Information Science Society Conference
• /
• 2012.06b
• /
• pp.89-91
• /
• 2012

무기체계 개발에 있어서 내장형 소프트웨어의 비중과 그 중요도가 점점 증가하고 있고, 고객 또한 무기체계 소프트웨어 개발 및 관리지침을 제정하여 소프트웨어 신뢰성 시험수준에 대한 놓은 요구사항을 제시하고 있다. 이렇게 대내외 환경이 변화하고 있음에 따라 당사는 고품질의 소프트웨어를 고객에게 납품하기 위해서 내장형 소프트웨어 신뢰성 향상활동을 수년간 수행해오고 있다. 업체주관 개발사업 증가와 무기체계 외주개발 비중 증가에 따라 고품질의 협력개발 소프트웨어의 획득이 중요해지고 있다. 하지만, 납품 받은 소프트웨어를 체계 통합하는 시기에 소프트웨어 결함이 많이 내재되어 있어 문제점이 많이 발생되고 있으며, 납품 이후에도 많은 결함수정과 재 작업이 발생하여 추가비용이 많이 발생하고 있다. 본 논문에서는 협력개발 소프트웨어 제품의 신뢰성 향상을 위해 TMMi 시험 프로세스를 적용하여 협력회사의 소프트웨어 시험 역량을 강화하고 고품질의 소프트웨어를 획득할 수 있는 방안을 제안하고자 한다.

• 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 Software Assessment and Valuation
• /
• v.16 no.2
• /
• pp.87-98
• /
• 2020

Recently, IoT, artificial intelligence, cloud, big data, and mobile fields have converged, leading to a new industrial era called the 4th industrial revolution. This 4th industrial revolution has been expanded to all industry area and Software has been taken as important role in this revolution. Thus Software Safety is the huge factor because Software is highly relevant to human safety in accordance with Software expansion. However this Software Safety has been focused on not organization improvement activities but current design/development, In this paper, to solve this issue, Software Safety Maturity level and relevant Process Area is defined. This study is expected to contribute to systematic software safety activities.