• 경영정보학연구
• /
• 제6권2호
• /
• pp.195-208
• /
• 2004

소프트웨어 규모가 대형화 됨에 따라 개발에 소요되는 시간과 인력도 대형화 되고 있으며, 또한 원하는 수준의 소프트웨어 품질을 얻기 위해 필요한 테스트 비용도 점점 더 증가하고 있다. 소프트웨어 프로젝트 개발 과정에서 품질 관리를 위해 다양한 결함 제거 기법들이 사용되고 있으나, 이러한 결함제거 기법과 결함 제거 시간이 전체 일정에 미치는 영향은 아직까지 체계적으로 분석되지 못하고 있다. 본 논문에서는 일정한 소프트웨어 품질 수준을 달성하기 위해 소요되는 시간을 소프트웨어 개발 일정 관리에 반영한 새로운 일정관리 모델을 제안한다. 제안된 모델은 CMU의 PSP/TSP (Personal Software Process/Team Software Process)를 적용하는 개발 과정에서 수집된 결함 정보, 결함 제거 시간, 평균 결함 제거시간 및 단계별 결함 제거율을 사용하여 일정 지연 여부를 실시간으로 추적할 수 있도록 하고 있다. 이를 위해 본 논문에서는 소프트웨어 품질 달성에 필요한 작업량을 일정 관리 측정체계와 동일한 측정체계에서 사용할 수 있도록 하는 품질 지수(Quality Value)를 새로 제안한다. 본 연구의 결과는 일정과 품질을 분리하여 관리하는 기존의 일정 관리 방법을 보완하여 프로젝트 관리자를 비롯한 모든 관계자가 품질 관리의 중요성을 인식하고 품질 저하 문제를 사전에 예방하는데 활용될 수 있을 것으로 기대된다.

• 한국정보처리학회논문지
• /
• 제4권8호
• /
• pp.1995-2006
• /
• 1997

소프트웨어의 무형성, 비가시성으로 인해 체계적인 품질관리를 실시하는데 어려움이 있으나 구성관리를 통해 소프트웨어를 하드웨어 생산과 같이 일괄적인 품질관리의 시도와 함께 소프트웨어 품질관리 표준요강을 제정하여 이 표준지침에 따라 소프트웨어의 품질을 관리함으로써 효율적인 품질관리를 실시하고 있다. 본 연구에서는 오류의 입력감소 및 조기발견이라는 기본 방침하에 이러한 품질관리활동을 지원하기 위한 소프트웨어 품질관리 지원시스템을 개발하려는 시도로서 소프트웨어 품질관리 시스템을 장해관리 지원기능을 중심으로 살펴보고 장해관리 지원기능을 보조할 수 있는 각종 시각적인 출력 요소들을 정리하였다. 또한, 이러한 소프트웨어 품질관리 시스템을 구축하게 된 배경을 살펴봄으로써 품질관리 표준화에 따르는 문제점 및 기존의 품질관리 도구에서 제기되는 문제점을 고려하여 시스템 구축을 위한 과제와 그 대책을 수립하였으며 끝으로 장해관리 지원기능을 이용했을 때의 효과를 기술하였다.

• Journal of Information Technology Applications and Management
• /
• 제13권4호
• /
• pp.237-255
• /
• 2006

This study was exploratively performed to demonstrate the management behavior of the public software project in korea. In this study, 167 auditing reports on the public software project which were carried out during $1999{\sim}2003$, were employed and surveyed. Survey reveals that quality management was the most neglected in process of software project management relative to other 12 management areas. And configuration management, risk management, time management, and scope management follow up in order in its vulnerability in software project management.

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

• 품질경영학회지
• /
• 제27권3호
• /
• pp.94-112
• /
• 1999

It is booming to use computer and information owing to the information society. As software applications have grown, so too has the importance of software quality. Therefore, software quality measurement and evaluation are necessary to satisfy the users who are using computers. The ISO/IEC 9126 defines six quality characteristics and twenty-one subcharacteristics including forty inter quality characteristics. We developed software measurement and evaluation technique using the check list in accordance with the ISO/IEC 9126 in design phase. We applied idea and concept of Total Quality Management in order to evaluate and measure the quality of software. Namely, it is the concept such as "you should do it right the first time." or "you have to build quality in the process." We executed the quantitative evaluation of software, also had shown the distinctive result in order that users and developers can find the errors easily. We evaluated the quality of academic softwares in order to verify developing technique at S college. As a result of the evaluation, this college has found it necessary to maintain the software as soon as possible because academic systems are not adequate for users at this present time.

• 경영과정보연구
• /
• 제25권
• /
• pp.275-296
• /
• 2008

We tested the relationship of elements in influence about software performance. our research is detect the significant element in the software system. we affronted to find relation elements with software quality and seek what relationship is the most important in performance activity. this study's result will be useful for them ; first, give to product a high quality guide line to software developer. second, it will be use for basic information about in software examine research.

• 품질경영학회지
• /
• 제34권3호
• /
• pp.1-18
• /
• 2006

CMMI(Capability Maturity Model Integration) has been recognized as a critical method to validate the competitiveness of software development organization since its introduction. CMMI imposes additional requirements on the software development organization which has been established and certified to the ISO 9001 quality management system. This paper reviews the similarities and differences between CMMI and ISO 9001. This paper also examines what ate required to deploy the CMMI on the aircraft software development organization which has been certified to ISO 9001. The results of this study will help software development organization to provide the direction for implementing CMMI. Some suggestions are presented to identify and strengthen the weak portion of the software process quality management system.

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

• 대한안전경영과학회:학술대회논문집
• /
• 대한안전경영과학회 2001년도 춘계학술대회
• /
• pp.167-171
• /
• 2001

In this paper, the QFD(quality function deployment) technique is used to acquire the quality requirements of package software which is sold in a commercial software shop. To select the principal quality characteristics of package software, an user survey was conducted for a quality model developed based on the international standards and the previous research. The software user is divided into three groups：the general user, the expert, and the developer. The method of QFD is applied to choose the software quality attributes which have strong correlation with the selected quality characteristics.

• 대한안전경영과학회지
• /
• 제3권3호
• /
• pp.213-220
• /
• 2001

This paper presents the interrelationship between software quality character and engineering attributes. The software quality characteristics and subcharacteristics are excerpted from IS0/IEC 9126 standards, and the engineering attributes are from Deutsch and Willis〔4〕. Based on the previous studies a subjective judgement, trisected interrelationship(strong, medium, weak) bet these two groups are derived. The results are summarized in a table, and can be used as a quick reference guide to the software quality engineering application such as quality evaluations for software products, selection of key engineering attributes for high-quality software production, and so forth.