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

• 정보기술응용연구
• /
• 제3권4호
• /
• pp.119-134
• /
• 2001

소프트웨어 제품의 품질을 높이는데는 소프트웨어 개발프로세스 중심과 제품 중심의 2가지 접근방법이 있다 CMM, ISO 9000 패밀리나 ISO/IEC 12207, SPICE 등이 프로세스의 인증을 통해서 소프트웨어 품질을 향상시키려는 시도라고 할 수 있다. 그렇지만 ‘좋은’ 프로세스만으로는 ‘좋은’ 제품의 품질을 보장하기가 어렵다. 최근 독립적인 제3자에 의한 소프트웨어 제품의 품질을 평가하기 위한 필요가 점점 증가하고 있다. 본 연구에서는 소프트웨어 제품의 품질을 평가하는데 SQC 기법을 응용하여 평가프로세스의 효율을 기하고 평가결과의 객관성을 확보하는 방안을 다룬다. 랜덤추출법에 의한 테스트 케이스를 선정하는 방법을 소개하고 소프트웨어 제품의 품질에 대한 적합성 기준을 선정하는 방안을 제시한다.

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

• 한국산학기술학회논문지
• /
• 제22권1호
• /
• pp.285-293
• /
• 2021

군수품 최초양산품 품질관리는 연구개발 이후 최초로 양산 계약된 군수품을 대상으로 개발 후 완성된 규격에 따라 개발품의 양산 실현 가능성과 적합성 평가를 목적으로 수행한다. 하지만 본 연구를 통한 무기체계 최초양산품 소프트웨어 품질보증을 수행하기 이전까지 최초양산품 품질보증은 하드웨어 중심으로 수행되어 소프트웨어에 대한 품질보증은 미흡한 상태였다. 이로 인해 후속 양산단계에서 소프트웨어의 문제점들이 발견됐을 경우 불가피한 기술변경에 따라 많은 시간과 비용이 소요되었다. 본 논문에서는 소프트웨어 기술자료의 충분성 및 적합성을 점검하기 위한 무기체계 최초양산품 소프트웨어 품질보증 프로세스 연구를 수행한 결과를 보인다. 그 결과 컴퓨터 파일의 완전성 점검, 소프트웨어 기술문서의 적합성 점검, 소프트웨어 기술자료와 그 외 국방규격의 연계 여부를 점검하는 프로세스를 정립하고 이 프로세스를 적용하여 최초양산품 소프트웨어 품질보증을 수행한 결과를 분석하여 최초양산품 소프트웨어 품질보증 프로세스의 효용성을 보인다. 소프트웨어 기술자료의 완전성을 확보하여 양산단계에서 발생할 수 있는 소프트웨어 문제점을 사전에 식별하여 소프트웨어의 선제적인 품질 확보에 기여할 수 있음을 보인다.

• 경영과정보연구
• /
• 제18권
• /
• pp.201-222
• /
• 2006

As the competition between countries has become higher and the notion of software quality has been widely spread. it has been necessary to develop technologies that can ensure and produce high quality software. With the advent of information-oriented society. quality control has to transfer to the quality control activities focused on software system instead of those activities focused on hardware system. If so, how do we get to handle the quality control on the basis of the new approach. Also, as software applications have grown. so too has the importance of software quality. In order to manage software quality, the technology to specify and evaluate both the software product quality and development process quality objectively quantitatively is most important. To produce products of good quality, we need a more progressive quality control system according to the need of software development life cycle. In other words, we do software right the first time or build quality in the process. On the basis intermediate and final time or build quality in the process. On the basis of data achieved, we can evaluate the products according to the consequences of the data, What are the problems to contrive the software quality control system?, we con promote the quality of products. To achieved that goal, we con provide a suitable the technique and method of software quality control.

• 한국IT서비스학회지
• /
• 제8권2호
• /
• pp.1-22
• /
• 2009

Recently, improving service quality for customer satisfaction is one of the most important issues and the task for the growth of company. Furthermore, plenty studies are going on progress to develop service quality in IT industry. There have been so many researches of product quality on package software but yet the service quality of package software has been rarely studied before. Thus, the purpose of this study is to formulate a scheme on how to enhance the competitivity of package software company by analyzing the impacts of these two factors on the customer satisfaction, Word-of-Mouth intention and the reuse intention. The study models have been designed and the hypotheses have been made through the examination of the precedent literature about package software product and service quality. A questionnaire survey was performed to collect information, and the unit of analysis was a person who used package software. This study used the statistical technique such as regression analysis. This study may be utilized as basic data for building marketing strategies when package software companies offer service to customers.

• 한국정보처리학회논문지
• /
• 제6권10호
• /
• pp.2680-2692
• /
• 1999

Software quality is classified by quality of process and product. In experience of Quality Management, it is known that quality level of product as it depends on goodness and badness of process and organization. As a result, improvement of software process has been important subject. According as this trends, ISO 12207 is publicated as standard of software life cycle process by ISO. For UML based object oriented development process, it is necessary that we should research detailed definition of activity and task of ISO 12207 process which is added, deleted or tailored in according to organization and project characteristics. In this thesis, by according with ISO 12207 software life cycle process, UML based object oriented development process is proposed. This process is composed of 7 steps and 19 activities including development phase, activity and product to improve quality of reliability. Usefulness of object oriented process for improvement of software quality is proved at three ways, which are comparative analysis of process characteristics, SPICE process evaluation and SPICE rick analysis.

• 시스템엔지니어링학술지
• /
• 제8권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.

• 한국항행학회논문지
• /
• 제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 통합운영국 소프트웨어의 제품 보증을 위한 소프트웨어 생명 주기 별 활동 및 소프트웨어 품질 모델, 메트릭을 제안한다.