• Journal of Software Engineering Society
• /
• v.29 no.2
• /
• pp.1-6
• /
• 2020

Software product line development is a development paradigm that efficiently develops a product family by avoiding redundant development based on separation of the common part and the variable part of the product family. In software product line development, the source code that is used to produce a product family is called a product line code base, and when the product line code base is changed and the products of the product family are affected by the change, the activity of testing the affected products is called a product line regression testing. For product line regression testing, instead of conducting regression testing individually on each product of the product family, a more efficient regression testing would be possible if unnecessary testing that are irrelevant to the change can be avoided. This paper introduces SRTS, which is an automated method to efficiently perform software product line regression testing. SRTS divides the product line code base and test cases based on commonality and variability. Then SRTS identifies and selects the test cases affected by the change. Finally, it reduces unnecessary testing by rerunning only the selected test cases.

• KIPS Transactions on Software and Data Engineering
• /
• v.11 no.7
• /
• pp.273-282
• /
• 2022

Testing approaches for configurable software product lines differs significantly from a single software testing, as it requires consideration of common parts used by all member products of a product line and variable parts shared by some or a single product. Test coverage is a measure of the adequacy of testing performed. Test coverage measurements are important to evaluate the adequacy of testing at the software product line level, as there can be hundreds of member products produced from configurable software product lines. This paper proposes a method for measuring code coverage at the product line level in configurable software product lines. The proposed method tests the member products of a product line after hierarchizing member products based on the inclusion relationship of the selected features, and quantifies SPL(Software Product Line) test coverage by synthesizing the test coverage of each product. As a result of applying the proposed method to 11 configurable software product line cases, we confirmed that the proposed method could quantitatively visualize how thoroughly the SPL testing was performed to help verify the adequacy of the SPL testing. In addition, we could check whether the newly performed testing for a member product covers the newly added code parts of a feature.

• Journal of KIISE:Software and Applications
• /
• v.41 no.7
• /
• pp.469-480
• /
• 2014

Software Product Line (SPL) is a software development paradigm that guarantees high productivity, reduced cost, and shorter time-to-market by systematically planning and reusing commonality and variability. In order to maximize the benefits of SPL engineering, testing should be integrated into the SPL engineering lifecycle processes that consist of domain engineering and application engineering and should be performed with as little test efforts as possible. This paper proposes a systematic software product line test cases derivation method using combinatorial test design. By applying combinatorial test design to product line test cases derivation and exploiting commonality between products at the same time, the number of generated test cases is dramatically reduced with the result that they can be effectively reused by the products of the given product line. Case studies conducted in this paper show the efficacy of our method compared with other methods that use only commonality or combinatorial design or neither of them in terms of the number of derived test cases.

• Proceedings of the Korean Institute of Navigation and Port Research Conference
• /
• 2018.05a
• /
• pp.181-182
• /
• 2018

2015년 6월 MSC 95차 위원회에서 e-navigation 소프트웨어 품질 보증 가이드라인이 회람문서로 정식 등재되었다. 이 가이드라인은 소프트웨어 개발 라이프사이클에 따라 소프트웨어를 개발하며 필요한 품질 보증 절차 활동과 사용자의 요구를 만족시킬 수 있는 제품의 개발을 위한 인간중심설계 절차를 제시한다. 본 논문에서는 e-navigation 소프트웨어 품질보증 가이드라인을 심층분석하여 해양 임베디드 응용 소프트웨어 품질보증을 위한 사용성평가 시험절차 개발에 필요한 연관된 국제표준 및 기존 연구를 조사 분석 후 연구하였다.

• 한국IT서비스학회:학술대회논문집
• /
• 2002.06a
• /
• pp.147-151
• /
• 2002

최근 국내 SI 사업체들은 소프트웨어의 가치를 향상시키기 위해 컴포넌트를 적극 도입하고 있다. 그러나 컴포넌트 시장을 활성화 시키기 위해서는 다양한 범주의 고객이 요구하는 양질의 컴포넌트를 풍부하게 갖추고, 고객이 시스템을 직접 개발하는 것보다 적은 비용과 시간을 소모하면서도 시스템을 구축할 수는 환경을 조성해야 한다. 그러한 환경을 구축하기 위한 요소중 고객의 구매 결정과 직결되는 가장 중요한 항목은 컴포넌트의 기술적 가치와 비즈니스적 가치의 평가와 이를 위한 시험 기준이다. 객관적이고 공정한 시험 기준이 마련되지 않는 상태에서 품질 평가가 이루어 지지 못한다면, 잠재적 고객이 구매 또는 사용하고자 하는 컴포넌트가 적절한 가치를 갖고 있는 것인지 판단할 수 있는 근거가 없고 시장 형성 초기부터 불량 컴포넌트 제품이 공급됨으로 인해 신뢰성이 저하되어 컴포넌트를 구매하는 대신 다른 대안을 선택하려 할 것이다. 객관적이고, 유력한 품질 평가 시스템을 구축하기 위해서는 품질 시험 평가를 위한 기준 마련이 선결 조건이다. 품질 시험 평가 가이드라인은 고품질의 소프트웨어 컴포넌트의 생산을 가능하게 하여, 궁극적으로 소프트웨어의 신뢰도를 향상 시키는 가장 유력한 방안이 될 것이다. 이를 통해 컴포넌트 소프트웨어의 유통 촉진 및 시장 성장을 견인, 생산/개발-유통-사용에 이르는 전체 컴포넌트 산업의 완결된 서비스를 제공 할 수 있을 것이다. 본 연구에서는 이러한 기준 마련을 위한 메트릭을 제공한다.

• The KIPS Transactions:PartD
• /
• v.13D no.3 s.106
• /
• pp.383-390
• /
• 2006

Product-line engineering is a dreaming goal in software engineering research. Unfortunately, the current underlying technologies do not seem to be still not much matured enough to make it viable in the industry. Based on our experiences in working on mobile telephony systems over 3 years, now we are in the course of developing an approach to product-line engineering for mobile telephony system software. In this paper, the experiences are shared together with our research motivation and idea. Consequently, we propose an approach to building and maintaining telephony application logics from the perspective of scenes. As a Domain-Specific Language(DSL), Menu Navigation Viewpoint(MNV) DSL is designed to deal with the problem domain of telephony applications. The functional requirements on how a set of telephony application logics are configured can be so various depending on manufacturer, product concept, service carrier, and so on. However, there is a commonality that all of the currently used telephony application logics can be generally described from the point of user's view, with a set of functional features that can be combinatorially synthesized from typical telephony services(i.e. voice/video telephony, CBS/SMS/MMS, address book, data connection, camera/multimedia, web browsing, etc.), and their possible connectivity. MNV DSL description acts as a backbone software architecture based on which the other types of telephony application logics are placed and aligned to work together globally.