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

• Journal of Information Technology Application
• /
• v.3 no.4
• /
• pp.119-134
• /
• 2001

Improving software product quality is a key to increasing user satisfaction and to achieving competitive edge. There are two approaches to assure high software product quality; development process-oriented and product-oriented. There have been many efforts for improving software quality through process certification, for example, CMM, ISO 9000 family, ISO/IEC 12207, SPICE and Bootstrap. However, a good process alone cannot guarantee good product quality. A need for the evaluation of software product quality by an independent third party is growing rapidly for several reasons. We are concerned with an application of Statistical Quality Control (SQC) to the evaluation of software product quality to obtain the efficiency of evaluation processes and the objectivity of evaluation results. Methods for selecting test cases using a random sampling approach have been discussed and methods for selecting acceptance criteria with respect to software product quality have also been suggested.

• Journal of Information Technology Applications and Management
• /
• v.24 no.3
• /
• pp.73-92
• /
• 2017

Usability is one of the most important concepts regarding software quality. It can be interpreted as the goodness associated with using the software product. This paper distinguishes the goodness of an individual using experience and the goodness of a product for using. This paper proposes a software quality view model which classifies software quality views into two broad categories of end view and means view. End view includes long-term view and short-term view which is classified further into performer's view on software activity and third party's view on software activity. Means view includes intrinsic view and contingency view. The analysis of ISO 25000 Series SQuaRE demonstrates the necessity to decompose product quality model and quality in use model into five models corresponding to the software quality views respectively. The analysis on playability shows that the universal definition of usability may be an illusion. The results provide the theoretical basis to build a comprehensive and consistent body of knowledge regarding software quality, which is consisted with the set of quality models and the theories explaining the relationships among the elements of the models.

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

• The KIPS Transactions:PartD
• /
• v.12D no.3 s.99
• /
• pp.395-408
• /
• 2005

Ubiquitous computing spans a very broad range of technologies and needs very complicated user's requirements. There are many scenarios and technologies involved in ubiquitous computing. We need new software development tools and methodology to meet the requirements. A software product line is one of promising new technology for it. A software product line is a set of software intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets. Software architecture-based development is the exploration and maturation of the role of software architecture in the product line life cycle. In this thesis, we identify the foundational concepts underlying software product lines and the essential activities to develop the mobile application systems. So, we define, design, and implement the Mobile Application System Architecture(MASA) that includes the development process for applying into mobile business domain and encompass scoping and gathering requirements for the Product line based on Component Based Development(CBD).

• Journal of Software Engineering Society
• /
• v.24 no.3
• /
• pp.77-89
• /
• 2011

Software product line engineering is a software reuse paradigm that helps organizations improve software productivity and quality by developing software products from reusable core assets. For the satisfaction of common and variable requirements among products in the product line, the core assets must be configurable according to the selection of variable features. Therefore, unlike software architecture model of a single product, product line architecture model must embed and express variabilities among the products. Many researches have proposed methods of embedding and expressing variabilities in the product line architecture models, but there are few comparative studies on the proposed methods. In this paper we discuss strong points and weak points of the proposed methods and compare expressiveness of the methods, which helps select a proper method.

• Journal of Internet Computing and Services
• /
• v.7 no.4
• /
• pp.11-22
• /
• 2006

Software product-lines methodology is the software development paradigm to build the target system by customizing the variable part of software assets according to requirements. To attain this, the commonalities and variabilities of the system family should be modeled explicitly at early stage. Although the researches on general software product-lines are active, the researches on component-based real-time embedded software product-lines are rather inactive. In this paper a code generation system to support the functional variabilities via feature model and generate the code for synchronization via state model is proposed to increase the productivity of the development of the real-time embedded software product-lines.

• Journal of Information Technology Services
• /
• v.4 no.2
• /
• pp.47-59
• /
• 2005

S/W product line is a S/W product or a set of S/W system, which has common functions. We can develop a specific S/W product, which satisfiesrequirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed S/W architecture through the S/W product line. S/W development methodology based on the S/W product line can develop a S/W more easily and fast by reusing the developed S/W core asset. An advanced country of S/W technology selects S/W product line as a core field of S/W production technology, and support technology development. In case of USA, CMU/SEI (Carnegie Mellon University / Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Ministry of National Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. In this paper, we aim to construct reference architecture of S/W product line for production of the S/W product line.

• The Journal of Society for e-Business Studies
• /
• v.6 no.2
• /
• pp.73-85
• /
• 2001

Usability is defined by the effectiveness, efficiency and satisfaction with which specified users can achieve specified goal in particular environment. Today, many factors such as software acquisition, business re-engineering and the trend of software market have software industry considers usability as an important quality of software products. Therefore, the specification and measurement method for establishing the acceptable usability level of software is required during software development acquisition and evaluation. To evaluate whether software products is usable or not, we need evaluation method for software usability. This paper is not only to provide a framework for specifying the usability attributes of a product and establishing a comprehensive set of usability criteria, but also assessing usability metrics of the software. The usability metrics and checklist is developed based on the properties of the user interface using ISO standard and general usability principles with product-oriented view which means the Product has attributes contributing to determine the usability. This paper also suggested the way to weight the relative importance of the individual usability item depending on the software categories.

• Journal of Information Technology Applications and Management
• /
• v.23 no.3
• /
• pp.71-86
• /
• 2016

This paper proposes a new software quality model composed of a hierarchy of software quality views and three software quality characteristics models. The software view hierarchy is composed of two levels : end view and means view at the first level, contingency view and intrinsic view as sub-views of means view. Three software quality characteristics models are activity quality characteristics model, contingency quality characteristics model, and intrinsic quality characteristics model, which correspond to end view, contingency view, and intrinsic view respectively. This paper also reclassifies characteristics of ISO/IEC 25000 series SQuaRE's software product quality model according to the proposed software quality model. The results illustrate clearly the shortcomings of SQuaRE's product quality model and how to overcome them. First of all, most of SQuaRE's product characteristics should be redefined and conceptually clarified according to the views on which they are really rested. Much more characteristics should be supplemented too. After that, rigorous empirical researches will become relevant. Causal relationships between activity quality characteristics and characteristics of means view should be empirically researched.