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

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.16 no.5
• /
• pp.1561-1583
• /
• 2022

Context: Testing is one of the techniques that can assure the quality of software including the domain of Software Product Line (SPL). Various techniques have been deliberated to enhance the quality of SPL including Model-based Testing (MBT). Objective: The objective of this study is to analyze and classify trends of MBT in SPL covering the solutions, issues and evaluation aspects by using taxonomy form. Method: A Systematic Literature Review (SLR) was conducted involving 63 primary studies from different sources. The selected studies were categorized based on their common characteristics. Results: Several findings can guide future research on MBT for SPL. The important finding is that the multiple measurements are still open to improving current metrics to evaluate test cases in MBT for SPL. The multiple types of measurement required a trade-off between maximization and minimization results to ensure the testing method which could satisfy multiple test criteria for example cost and effectiveness at the same time.

• Journal of Korean Society for Quality Management
• /
• v.17 no.2
• /
• pp.17-26
• /
• 1989

This paper is concerned with forecasting the existing number of errors in the computer software and optimizing the stopping time of the software test based upon the forecasted number of errors. The most commonly used models have assessed software reliability under the assumption that the software failure late is proportional to the current fault content of the software but invariant to time since software faults are independents of others and equally likely to cause a failure during testing. In practice, it has been observed that in many situations, the failure rate decrease. Hence, this paper proposes a mathematical model to describe testing situations where the failure rate of software limearly decreases proportional to testing time. The least square method is used to estimate parameters of the mathematical model. A cost model to optimize the software testing time is also proposed. In this cost mode two cost factors are considered. The first cost is to test execution cost directly proportional to test time and the second cost is the failure cost incurred after delivery of the software to user. The failure cost is assumed to be proportional to the number of errors remained in the software at the test stopping time. The optimal stopping time is determined to minimize the total cost, which is the sum of test execution cast and the failure cost. A numerical example is solved to illustrate the proposed procedure.

• Journal of Korean Society for Quality Management
• /
• v.22 no.2
• /
• pp.33-40
• /
• 1994

Most software reliability models and other methods attempt to estimate some measures based on its fault history. There are several phases of the software life cycle including testing phase. We can propose it's stopping rule to decide when to stop the testing and pass it on to the next phase by considering the detailed structure of software and calculating the failure rate when each fault was detected. Downs (1985) proposed a method which was developed for estimating the failure rate applicable only to two-level profiles. In this paper, I extended to profiles involving more levels.

• Journal of Korean Society for Quality Management
• /
• v.30 no.3
• /
• pp.186-194
• /
• 2002

In this paper we introduce formulae for estimating the failure rate of a large scaled software by using the Bayesian rule when a black-box random testing which selects an element(test case) at random with equally likely probability, is performed. A program or software can be treated as a mathematical function with a well-defined (input)domain and range. For a large scaled software, their input domains can be partitioned into multiple subdomains and exhaustive testing is not generally practical. Testing is proceeding with selecting a subdomain, and then picking a test case from within the selected subdomain. Whether or not the proportion of selecting one of the subdomains is assumed probability, we developed the formulae either case by using Bayesian rule with gamma distribution as a prior distribution.

• The KIPS Transactions:PartD
• /
• v.9D no.1
• /
• pp.103-110
• /
• 2002

In component-Based Software Development, the quality of indivisual component is play an important role in quality decision of the whole software. So we need the practical strategy for component testing. In general, component testing can divide focus into producer position and consumer position. In this paper, because the consumer position uses output of the producer position, testing domain is deployed in the producer position. We propose RUP based five step testing processes for component quality evaluation and implements a case study of EJB environment for appling our testing process. This paper shows that proposed five step processes are applicable to component quality evaluation.

• Journal of Aerospace System Engineering
• /
• v.7 no.3
• /
• pp.58-64
• /
• 2013

The paper presents the comprehensive studies of ISTQB(International Software Testing Qualification Board) for the reliable software development system in term of various aspects. It is critical to understand how the software testing is achieved is to efficiently manage the development process, to reduce the development cost, and to ultimately ensure the safety of the entire software system. This study may provide an enriched understanding about the rationale and true intent the behind software development model and testing design methods of ISTQB on software developer, test analysts, test engineers. In addition, this paper may serve as a useful supplementary material for the avionic engineers to establish the new regulations in avionic industries.

• Journal of the Korean Society of Systems Engineering
• /
• v.8 no.2
• /
• pp.19-25
• /
• 2012

As modern weapon systems have evolved into embedded software systems, the capability to develop, install, and maintain high-quality software products is becoming increasingly valuable in today's competitive aerospace and defense industry. It is desirable, especially for government-contracted projects whose end-users are military personnel, that specific types of software quality elements are assured early during product development; namely, functionality and usability. Motivated by this need to approach improving software quality from a user's perspective, this paper presents a case study that analyzes system-level software integration testing results for a weapon system indigenously developed in the Republic of Korea. Quantitative data, such as software defect ratios and configuration change rates, are computed to observe meaningful trends with respect to functionality - represented by tests designed to verify the system's electrical signal interfaces - and usability, which is evaluated in terms of how often the initial human-computer interface had to be re-designed. Insights gained from these exercises are subsequently presented as a set of "lessons learned" to take into account when developing new software items for complex weapon systems.

• Journal of the Korea Convergence Society
• /
• v.8 no.10
• /
• pp.37-43
• /
• 2017

In this paper, we propose a method for estimation software quality in terms of software test data, and it is necessary to predict the period of time required for software test evaluation. We need a model to understand of estimation of software quality. In this paper, we propose a model to estimate the number of days for software test using the data obtained through the tester's sex, and present a model for analysing the number of errors according to six quality characteristics by software type.

• IE interfaces
• /
• v.25 no.4
• /
• pp.416-421
• /
• 2012

One of the activities to improve software quality in ISO 26262 is to apply the design principles for software unit design and implementation mentioned in ISO 26262-6, including the evaluation activity. Before evaluation activity, the tool is compared and selected for evaluation. Because the results of the tool a company selected might have an effect on product quality. In this paper, we suggest the method to compare industrial static analysis tools with some of "MISRA C : 2004 Exemplar Suite" and all lessons learned from comparing tools are described. The result on comparison shows that we just couldn't rely on a result of Static Analysis Tool and need to have another appropriate processes and guidelines to evaluate a software.