• Journal of Information Technology Applications and Management
• /
• 제23권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.

• Journal of Information Technology Applications and Management
• /
• 제26권2호
• /
• pp.111-123
• /
• 2019

In this paper, software activity, software activity instance, and the quality of the activity instance are defined as the 'activity which is performed on the software product by a person or a group of persons,' the 'distinctive and individual performance of software activity,' and the 'performer's evaluation on how good or bad his/her own activity instance is,' respectively. The representative values of the instance quality population associated with a product and its sub-population are defined as the (software) activity quality and activity quality characteristic of the product, respectively. The activity quality model in this paper classifies activity quality characteristics according to the classification hierarchy of software activity by the goal. In the model, a quality characteristic can have two types of sub-characteristics : Special sub-characteristic and component sub-characteristic, where the former is its super-characteristic too simultaneously and the latter is not its super-characteristic but a part of its super-characteristic. The activity quality model is parsimonious, coherent, and easy to understand and use. The activity quality model can serve as a corner stone on which a software quality body of knowledge, which constituted with a set of models parsimonious, coherent, and easy to understand and use and the theories explaining the cause-and-relationships among the models, can be built. The body of knowledge can be called the (grand) activity-centric quality model of software.

• Journal of Information Technology Applications and Management
• /
• 제24권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.

• 산업경영시스템학회지
• /
• 제40권3호
• /
• pp.27-37
• /
• 2017

As the global uncertainty of manufacturing has increased and the quality problem has become global, the recall has become a fatal risk that determines the durability of the company. In addition, as the convergence of PSS (product-service system) product becomes common due to the development of IT convergence technology, if the function of any part of hardware or software does not operate normally, there will be a problem in the entire function of PSS product. In order to manage the quality of such PSS products in a stable manner, a new approaches is needed to analyze and manage the hardware and software parts at the same time. However, the Fishbone diagram, FTA, and FMEA, which are widely used to interpret the current quality problem, are not suitable for analyzing the quality problem by considering the hardware and software at the same time. In this paper, a quality risk assessment model combining FTA and FMEA based on defect rate to be assessed daily on site to manage quality and fishbone diagram used in group activity to solve defective problem. The proposed FTA-FMEA based risk assessment model considers the system structure characteristics of the defect factors in terms of the relationship between hardware and software, and further recognizes and manages them as risk. In order to evaluate the proposed model, we applied the functions of ITS (intelligent transportation system). It is expected that the proposed model will be more effective in assessing quality risks of PSS products because it evaluates the structural characteristics of products and causes of defects considering hardware and software together.

• Journal of Information Technology Applications and Management
• /
• 제27권2호
• /
• pp.37-50
• /
• 2020

This paper is very exploratory and addresses the issue 'Is a general quality model of software possible?'. If possible, how specific can/should it be?' ISO 25000 Series SQuaRE is generally regarded as a general quality model which can be applied to most kinds of software. Usability is one of the 8 characteristics of SQuaRE's Product Quality Model. It is the main issue associated with SQuaRE's Quality in Use Model too. it is the most important concept associated software quality since using is the only ultimate goal of software products. Playability, however, is generally regarded as a special type of usability, which can be applied to game software. This common idea contradicts with the idea that SQuaRE is valid for most kinds, at least many kinds, of software. The empirical evidences of this paper show that SQuaRE is too specific to be a general quality model of software.

• 한국정보과학회논문지:소프트웨어및응용
• /
• 제26권12호
• /
• pp.1455-1467
• /
• 1999

소프트웨어 품질을 정의하기 위한 여러 가지 소프트웨어 품질 모형(SQM : Software Quality Model)이 개발되어 왔다. 이 모형들은 두 가지 목적을 가진다. 한 가지는 소프트웨어 품질 측정이고, 또 다른 목적은 개발 프로세스에서의 소프트웨어 품질 제어이다. 국제 표준인 ISO/IEC 9126은 소프트웨어 측정을 위한 소프트웨어 품질 모형을 제시하였다. ISO/IEC 9126의 품질 모형은 사용 관점에서 소프트웨어 품질을 정의한 모형이다. 이 모형은 개발 프로세스에서의 품질 제어를 하는 측면에서는 불완전한 모형이다. 소프트웨어의 품질이 프로세스 내에서 어떻게 만들어지는지 볼 수 없는 모형이기 때문이다. 따라서, 개발 관점에서의 소프트웨어 품질 모형이 필요하다.본 논문에서는 사용 관점인 ISO/IEC 9126 품질 모형을 기반으로 하여 개발 관점에서의 소프트웨어 품질 모형을 제안한다. 이 모형은 ISO/IEC 9126과 같이 하위 품질 요소가 중복되지 않는 계층적 품질 모형이면서, 개발 프로세스 내에서 제어 가능한 제품 특성에 기반을 둔 개발 관점의 소프트웨어 품질 모형이다. 본 논문에서는 소프트웨어 품질 모형 구축 시, 품질 속성간의 선후조건관계를 설정하여 품질 속성간 중복되었던 제품 특성을 한 품질 속성 내 귀속시킨다. 품질 속성 별 제품 특성을 기반으로, 프로세스 내에서 제품 특성을 측정하는 메트릭스를 제안한다. 본 논문에서 제안한 품질 모형과 ISO/IEC 9126을 비롯한 기존 품질 모형과 비교 분석한다.Abstract Several SQMs(Software Quality Models) have been developed to define a software quality. These models have two goals. One is to measure a software quality, the other is to control a software quality. The SQM of ISO/IEC 9126 is defined from the user's viewpoint. This model is an incomplete model in controlling a software quality in the development process. Since this model cannot show how to build a high quality software, the SQM of the developer's view is needed.We suggest the SQM of the developer's view. This model is a completely hierarchical model and is based on product properties. For this model, we define implicative relations among quality attributes for 1:m relations of quality attributes and product properties. So, we solve the problem of a quality attribute overlapping with other quality attributes. We suggest metrics based on our SQMs. Further, we evaluate our SQM by comparing our SQM with other SQMs.

• 정보처리학회논문지:소프트웨어 및 데이터공학
• /
• 제3권1호
• /
• pp.1-6
• /
• 2014

모든 기업들은 높은 품질의 정보시스템과 높은 생산성을 가지는 소프트웨어 제품을 만들기 위해 소프트웨어 제품라인 공학(software product line engineering)을 도입하고 있다. 소프트웨어 제품라인 방법론은 다양한 모델들을 가지고 있으며, 각 모델은 추상화 관점과 수준이 서로 다르다. 이러한 모델에 존재하는 요소들간 추적성(traceability)과 가변성(variability) 정보의 일관성(consistency)을 유지하는 것이 중요하다. 본 연구에서는 휘처(feature)의 가변성과 다른 산출물에 정의한 가변성의 일관성을 검증하는 규칙을 제시하였다.

• 한국항행학회논문지
• /
• 제24권1호
• /
• pp.28-36
• /
• 2020

KASS(Korea Augmentation Satellite System)는 국토교통부에서 2014년부터 개발 중인 한국형 위성항법보강시스템이다. KASS는 항공기 안전에 영향을 미칠수 있는 항공용 시스템이기 때문에 KASS의 각 소프트웨어는 안전성 분석을 통해 할당된 DO-178B의 소프트웨어 레벨에 따라 개발이 수행된다. KASS의 하위시스템인 통합운영국의 경우 일부 소프트웨어를 제외하고는 DO-178B 레벨E를 할당 받았으며 DO-178B 레벨E 소프트웨어의 경우 제품 보증을 위해 ECSS-Q-ST-80C 카테고리 D를 준수하여 개발하도록 하고 있다. 본 논문에서는 ECSS-Q-ST-80C를 만족하기 위해 ECSS-E-ST-40C, ECSS-Q-HB-80-04A를 분석하여 KASS 통합운영국 소프트웨어의 제품 보증을 위한 소프트웨어 생명 주기 별 활동 및 소프트웨어 품질 모델, 메트릭을 제안한다.

• 한국정보과학회논문지:소프트웨어및응용
• /
• 제30권7_8호
• /
• pp.618-641
• /
• 2003

소프트웨어 제품의 품질을 평가하기 위한 방법으로써 품질 요소, 품질 항목 및 여러 가지 메트릭을 이용한 품질 모델들이 제시되어 왔다. 하지만, 소프트웨어의 품질을 보다 정확하게 평가하기 위해서는 각각의 특징에 맞는 특화된 모델이 필요하다. 본 논문에서는 소프트웨어 컴포넌트 개발에 있어서 개발이 진행중인 상태의 소프트웨어 내부 속성에 적절한 메트릭을 적용시킨 결과를 이용하여 개발 완료 후의 소프트웨어가 가지게 되는 외부 품질을 어떻게 추정하는지에 대한 외부 품질 추정 모델을 제시한다. 소프트웨어 품질을 측정하기 위한 메트릭을 적용한 결과로써 품질 자체를 측정하는데 한정하지 않고, ISO 9126에서 제시하는 소프트웨어의 내부 속성을 이용하여 소프트웨어 컴포넌트 개발의 각 산출물에 어떻게 적용시키는지에 대한 모델을 예제를 통하여 제시한다.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• 제16권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.