• 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 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 KIISE:Software and Applications
• /
• v.35 no.5
• /
• pp.288-296
• /
• 2008

Software in defense domain requires high quality since defense specific characteristics. To assure high quality products, development and testing activities based on well defined process must be performed. If those activities cannot support software acquisition process, the quality of acquired software product is low and combat power decreases. In this paper, we propose MND-TMM(Ministry of National Defense-Testing Maturity Model), which can help enhance software quality through testing process improvements. This paper also introduces the contents of MND-TMM architecture. MND-TMM is constituted to reflect the characteristics of defense software, development process, and testing process so as to solve the problems associated with software testing. MND-TMM is comprised of 5 maturity levels and 4 categories which have number of related TPA(Testing Process Area)s. It is expected that MND-TMM can help assess testing maturity of defense software organizations and provides guidelines to improve software testing process.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.15 no.8
• /
• pp.2974-2992
• /
• 2021

Crowd-based outsourcing is an emerging trend in testing, which integrates advantages of crowd-based outsourcing in software testing. Open call format is used to accomplish various network tasks involving different types of testing levels and techniques at various places by software testers. Crowd-sourced software testing can lead to an improper testing process as if it does not allocate the right task to the right crowd with required skills and not choose the right crowd; it can lead to huge results, which become time-consuming and challenging crowd-source manager for the identification of improper one. The primary purpose of this research is to make crowd-based outsourced software testing more effective and reliable by relating association between the software tester, personality characteristic, and different levels of software testing, i.e., unit, integration, and system, in order to find appropriate personality characteristic for required testing level. This research has shown an observed experiment to determine which software testing level suits which personality characteristic tester in a crowd-based software testing environment. A total of 1000 software testers from different software houses and firms in Pakistan were registered to perform tasks at different software testing levels. The Myers-Briggs Type Indicator (MBTI) test is used to identify each tester's personality characteristic involved in this research study.

• 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 Korean Society for Quality Management
• /
• v.34 no.3
• /
• pp.73-78
• /
• 2006

In this paper, we propose a software reliability growth model based on the testing domain in the software system, which is isolated by the executed test cases in software testing. In particular, our model assumes an imperfect debugging environment in which new faults are introduced in the fault-correction process, and is formulated as a nonhomogeneous Poisson process(NHPP). Further, it is applied to fault-detection data, the results of software reliability assessment are shown, and comparison of goodness-of-fit with the existing software reliability growth model is performed.

• Journal of Information Technology Applications and Management
• /
• v.12 no.2
• /
• pp.1-13
• /
• 2005

This paper proposes a software-reliability growth model incoporating the amount of testing effort expended during the software testing phase after developing it. The time-dependent behavior of testing effort expenditures is described by a Logistic curve. Assuming that the error detection rate to the amount of testing effort spent during the testing phase is proportional to the current error content, a software-reliability growth model is formulated by a nonhomogeneous Poisson process. Using this model the method of data analysis for software reliability measurement is developed. After defining a software reliability, This paper discusses the relations between testing time and reliability and between duration following failure fixing and reliability are studied. SRGM in several literatures has used the exponential curve, Railleigh curve or Weibull curve as an amount of testing effort during software testing phase. However, it might not be appropriate to represent the consumption curve for testing effort by one of already proposed curves in some software development environments. Therefore, this paper shows that a logistic testing-effort function can be adequately expressed as a software development/testing effort curve and that it gives a good predictive capability based on real failure data.

• Journal of Internet Computing and Services
• /
• v.19 no.2
• /
• pp.43-48
• /
• 2018

Various artifacts that are produced as software R&D project progresses contain research plan, research report, software requirements and design descriptions, etc. When conducting a software R&D project, it is necessary to confirm that the developed system has implemented its research requirements well. However, various research results make it difficult to design appropriate tests. So, there is a practical need for us to comprehensively handle the planning, execution, and reporting of software test for finding and verifying information related to the research. In this paper, we propose a useful method for software test process in R&D project which supports model based software testing. The proposed method supports automation of test design and generation of test data by explicitly separating each step of System Under Test (SUT). The method utilizes the various models representing the control flow of the function to extract the information necessary for testing the system. And it supports a systematic testing process based on TMMi and ISO 29119. Finally, we show the validity of the method by implementing a prototype with basic functionality to generate test data from software behavioral models.

• The Korean Journal of Applied Statistics
• /
• v.23 no.3
• /
• pp.573-584
• /
• 2010

This paper considers the differences in the software execution environments in the testing phase and the operational phase to determine the optimal release time and warranty period of software systems. We formulate equations for the total expected software cost until the end of the software life cycle based on the NHPP. In addition, we derive the optimal release time that minimizes the total expected software cost for an imperfect debugging software reliability model. Finally, we analyze the sensitivity of the optimal testing and maintenance design related to variation of the cost model parameters based on the fault data observed in the actual testing process, and discuss the quantitative properties of the proposed model.

• International Journal of Reliability and Applications
• /
• v.4 no.1
• /
• pp.1-12
• /
• 2003

Many software reliability growth models (SRGM's) based on a nonhomogeneous Poisson process (NHPP) have been proposed by many researchers. Most of the SRGM's which have been proposed up to the present treat the event of software fault-detection in the testing and operational phases as a counting process. However, if the size of the software system is large, the number of software faults detected during the testing phase becomes large, and the change of the number of faults which are detected and removed through debugging activities becomes sufficiently small compared with the initial fault content at the beginning of the testing phase. Therefore, in such a situation, we can model the software fault-detection process as a stochastic process with a continuous state space. In this paper, we propose a new software reliability growth model describing the fault-detection process by applying a mathematical technique of stochastic differential equations of an Ito type. We also compare our model with the existing SRGM's in terms of goodness-of-fit for actual data sets.