An Activity-Centric Quality Model of Software

Seokha Koh 한국데이타베이스학회 2019 Journal of information technology applications & m Vol.26 No.2

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 subcharacteristic 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-andrelationships among the models, can be built. The body of knowledge can be called the (grand) activitycentric quality model of software.

무기체계 소프트웨어 품질 개선을 위한 ISO/IEC 25023의 소프트웨어 개발 프로세스 적용 방안

윤경환(Gyeonghwan Yoon),류지선(Jiseon Yu) 한국산학기술학회 2021 한국산학기술학회논문지 Vol.22 No.5

본 연구에서는 기존의 무기체계 소프트웨어 개발 프로세스에 ISO/IEC 25023의 소프트웨어 품질 평가 모델을 적용하여 기존보다 무기체계 소프트웨어의 품질을 향상시킬 수 있는지 확인하였다. 현재 무기체계 소프트웨어 개발 프로세스는 소프트웨어 품질 요구사항을 관리하고 있지만 소프트웨어 품질은 제한적으로만 향상시키고 있었다. 소프트웨어 품질 요구사항에서 품질 특성을 정의하고 관리하였지만 개별적인 사업에 따라 품질 특성이 다르게 정의되었기 때문이다. 따라서 소프트웨어 품질 요구사항의 품질 특성이 동일하여도 산출물이 다르고 사업에 따라 품질 관리의 차이가 컸다. 무기체계 소프트웨어 개발 프로세스 내에서 소프트웨어 품질 관리 제한점의 원인은 소프트웨어 품질 특성에 대한 일관된 정의 부족과 정량적으로 측정되지 않는 산출물로 파악하였다. 국제표준 소프트웨어 품질평가 메트릭인 ISO/IEC 25023은 소프트웨어를 8가지 주특성 및 31가지 부특성으로 구분하여 품질 특성을 정의하고 정량적으로 소프트웨어 제품 품질을 평가할 수 있는 기준을 제시한다. ISO/IEC 25023을 무기체계 소프트웨어 개발 프로세스에 적용하여 소프트웨어 품질을 향상시키는 방안을 검토하고 소프트웨어 품질 향상 효과를 분석하였다. This study aimed to improve the software quality in weapon systems by applying ISO/IEC 25023 to the software engineering process. The software engineering process in weapon systems manages the Software Quality Requirement but has restrictively improved the software quality. Software quality items are already defined and used for software engineering processes in weapon systems, but they are defined inconsistently according to individual software development cases. Thus, the methods of quantifying software quality are different, even though the same software quality is defined. In addition, the software quality has been managed differently. The major problems of software engineering processes in weapon systems are the unclear definition of the software quality requirements and the absence of quantifying software quality standards. ISO/IEC 25023 is composed of eight quality characteristics and thirty-one sub-characteristics. ISO/IEC 25023 provides measurement functions that can quantify the software product quality based on its characteristics. To improve the software quality further, the measurement functions in ISO/IEC 25023 are suggested to quantify and manage software quality for software engineering processes in weapon systems. The expected effects of this study were analyzed.

An Activity-Centric Quality Model of Software

Koh, Seokha Korea Data Strategy Society 2019 Journal of information technology applications & m Vol.26 No.2

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.

An Activity-Centric Quality Model of Software

고석하 한국데이터전략학회 2019 Journal of information technology applications & m Vol.26 No.2

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.

소프트웨어 공학수준과 소프트웨어 품질비용의 관계분석

김승권(Seung-Gweon Kim),고병선(Byung-Sun Ko),조성현(Sung-Hyun Cho),이상은(Sang-Eun Lee) 한국정보과학회 2011 정보과학회논문지 : 소프트웨어 및 응용 Vol.38 No.10

소프트웨어의 역할과 소프트웨어 품질의 중요성이 증대됨에 따라, 많은 기업들이 소프트웨어의 품질향상을 위해 다양한 노력과 비용을 투입하고 있다. 기업들의 품질 향상을 위한 적극적인 노력과 투자가 궁극적으로 기업의 이익에 주는 영향에 대해서는 서로 상반된 의견이 존재한다. 품질비용은 좋은 품질의 소프트웨어를 만들기 위한 경제적 이익의 상충관계를 이해하는데 도움을 주는 유용한 개념이며, 제조업이나 서비스 분야를 중심으로 활발한 연구가 진행되었다. 하지만 소프트웨어 품질비용에 대한 연구는 제조업이나 서비스 분야에 비해 활발하지 못한 실정이다. 본 논문은 국내 소프트웨어 개발 프로젝트의 품질비용구조를 분석하고, 미 CMMI 모델을 근간으로 만들어진 소프트웨어 공학수준 등급에 따라 품질비용의 차이가 존재하는지를 통계적 방법론인 붓스트랩 기법과 일원분산분석을 통해 살펴보았다. 분석결과, 국내의 소프트웨어 품질비용은 전체 프로젝트 비용의 62% 정도의 품질비용을 지출하고 있는 것으로 나타났으며, 소프트웨어 공학수준 등급별로 차이가 존재하는 것으로 분석되었다. 즉, 소프트웨어 공학수준이 높을수록, 적은 품질비용이 투입되는 것으로 나타났다. 이는 기업들이 자신들의 소프트웨어 품질향상과 소프트웨어 품질비용 절감을 위해 소프트웨어 공학수준을 높이기 위한 지속적인 노력이 필요하다는 것을 보여주고 있다. With the increasing role and importance of software quality, a number of software enterprises are focused to improve the quality and efficiency of software through a wide variety of costs and efforts. It has produced some conflicting opinions whether their aggressive endeavors and investment would gain a good profit. Software quality cost is an essential factor to understand an economic trade-off in relation for high-quality software. A fewer research on software industry has been conducted actually than in the manufacturing business and the service industry. However the concerns and management for software quality cost is one of useful methods to advance the software quality. The purpose of this study lies in showing us the structure of software quality cost in domestic software development projects through a survey. We examine the difference of software quality costs among software engineering levels which are referenced by Software Engineering Institute's Capability Maturity Model Integrated. The collected data are analyzed through using Bootstrap and one-way ANOVA method. Our results show that software quality cost is taking the average 62% of total software development costs in domestic software development projects. And the software quality cost differs with software engineering level. In other words, the higher the SW engineering level, the lower the SW quality cost. This conclusion indicates that every software company should spare no efforts to elevate their SW engineering level for high-quality software and low-cost software quality.

What Should Using a Software Product and Usability of the Software Product Be?

Koh, Seokha,Jiang, Jialei Korea Data Strategy Society 2017 Journal of information technology applications & m Vol.24 No.3

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.

The Impact of Community and Commercial Open Source Software on the Quality Strategies of Software Producers

Mingqing Xing,Lu Shen 보안공학연구지원센터 2016 International Journal of u- and e- Service, Scienc Vol.9 No.6

This study investigates how open source software can play influences on the quality choices of commercial open source and proprietary software providers. It considers two types of open source software: community open source and commercial open source, and assumes that the usability of commercial open source software is better than community open source substitute but inferior to proprietary substitute. It finds that: (i) the functional quality of proprietary software decreases as the functional quality of community open source software increases, but it may increase as the usability of community open source software increases; (ii) even if commercial open source producers must open the source codes of their quality contributions, they have incentive to enhance the functional quality of community open source software; (iii) the influence of community open source software’s quality (usability or functional quality) or commercial open source software’s usability on the functional quality of commercial open source and proprietary software may be not same; (iv) the appearance of commercial open source software may lead to proprietary software producers lowering their software functional quality.

소프트웨어 품질측정을 위한 소프트웨어 품질매트릭 방법론과 적용 연구

이성기 한국국방경영분석학회 1996 한국국방경영분석학회지 Vol.22 No.2

Research issues in software engineering in recent may be object oriented methodology and software quality. Since Halstead has proposed metric-software science in 1977, software quality area has been studied in steady but inactively until 1980s. As international standards such as ISO 9000-3, 9126 were enacted in 1990s early, interest in software quality is increased but many problems such as how to validate metric, measure quality or apply metric are remained. This paper proposes software quality metric methodology which software developer or project manager can use in measuring quality and validating metric during software development. The methodology is classified by several phases: establishment of quality requirement, identification of quality metric, data collection, metric implementation, metric validation. In order to show its applicability, test program, metrics and data are applied to each phase of the methodology. Consideration of this methodology as a methodology for software quality measurement similar to development methodology for software development is needed.

Integrated Software Quality Evaluation: A Fuzzy Multi-Criteria Approach

Challa, Jagat Sesh,Paul, Arindam,Dada, Yogesh,Nerella, Venkatesh,Srivastava, Praveen Ranjan,Singh, Ajit Pratap Korea Information Processing Society 2011 Journal of information processing systems Vol.7 No.3

Software measurement is a key factor in managing, controlling, and improving the software development processes. Software quality is one of the most important factors for assessing the global competitive position of any software company. Thus the quantification of quality parameters and integrating them into quality models is very essential. Software quality criteria are not very easily measured and quantified. Many attempts have been made to exactly quantify the software quality parameters using various models such as ISO/IEC 9126 Quality Model, Boehm's Model, McCall's model, etc. In this paper an attempt has been made to provide a tool for precisely quantifying software quality factors with the help of quality factors stated in ISO/IEC 9126 model. Due to the unpredictable nature of the software quality attributes, the fuzzy multi criteria approach has been used to evolve the quality of the software.

소프트웨어 품질역량 개선방안에 대한 연구

김지관 ( Jie-kwan Kim ),이윤홍 ( Yun-hong Lee ),이상용 ( Sang-yong Rhee ) 대한설비관리학회 2017 대한설비관리학회지 Vol.22 No.1

In software, the function and usability of the product are the top priority but the quality of the software including all of these factors is the most important factor in the life cycle of the software. Especially, the software market has grown explosively since 2002 when system intelligence has been launched in earnest, and will become a bigger market after 2020 when the fourth industrial revolution is expected to start. The use of such software will be even higher in the Fourth Industrial Revolution and it will surely be the determining factor for the completion of the Fourth Industrial Revolution. Therefore, increasing the quality capability of software has become a pending issue in industry not just software. Unlike the emphasis on the importance of software, building a systematic software quality management system and a quantitative software development management system is delayed due to cost problems. Also, the perception of system users` quality of software is not analyzed accurately. In this paper, we analyze the quality characteristics of software and propose improvement of quality capability of software by comparing and analyzing cases of improving quality competitiveness of domestic and foreign companies.