• 제목/요약/키워드: Software Quality Management

검색결과 688건 처리시간 0.027초

Applying Software Reuse to Improve Software Quality and Productivity

  • Lai Sen-Tarng
    • 한국품질경영학회:학술대회논문집
    • /
    • 한국품질경영학회 1998년도 The 12th Asia Quality Management Symposium* Total Quality Management for Restoring Competitiveness
    • /
    • pp.43-50
    • /
    • 1998
  • The cause of software crisis is that software quality and productivity can not meet the requirement of software market. In order to resolve the software crisis, there are many approaches to be proposed. Software reuse is one of the high potential approaches to improve software quality and productivity. Some high-tech countries (like USA, Japan) have proposed and studied the topics of software reuse in 1970 and got several results. In software development procedure, the products of detailed design and implement phases are simple, definite and suitable for reuse. In this paper, the necessary documents of reusable software component will be proposed, and how to select and evaluate the software components with high reuse potential and high quality will be discussed and recommended.

  • PDF

Software 품질의 정량적 측정과 평가 (A Quantitative Measurement and Evaluation of Software Product Quality)

  • 임대혁
    • 경영과정보연구
    • /
    • 제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.

  • PDF

An Activity-Centric Quality Model of Software

  • Koh, Seokha
    • 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.

Cause-and-Effect Perspective on Software Quality : Application to ISO/IEC 25000 Series SQuaRE's Product Quality Model

  • Koh, Seokha
    • 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.

소프트웨어 품질관리 방법에 관한 연구 (A Study on Method for software Quality control)

  • 임대혁;장영숙
    • 경영과정보연구
    • /
    • 제15권
    • /
    • pp.245-262
    • /
    • 2004
  • 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.

  • PDF

QFD 기법을 이용한 패키지 소프트웨어의 품질 요구사항 획득 (Acquiring Quality Requirements of Package Software using Quality Function Deployment Technique)

  • 유영관;이종무
    • 품질경영학회지
    • /
    • 제29권2호
    • /
    • pp.120-130
    • /
    • 2001
  • In this paper, the QFD(quality function deployment) technique is used to acquire the quality requirements of package software which is sold in 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. Based on the survey results, the top 10 quality characteristics are selected including accuracy, suitability, installability, de-installability, and maturaty. Then, the QFD technique is applied to choose the software quality attributes which have strong correlation with the selected quality characteristics, some of which are traceability, accuracy, modularity, completeness, and self-descriptiveness. The developed procedure can be used in evaluating the quality of package software with lower costs and efforts.

  • PDF

와이브로와 HSDPA를 통한 모바일 인터넷 전화 서비스 품질 측정 및 비교 (Service Quality Measurement and Comparison of Mobile Internet Telephony Services over WiBro and HSDPA)

  • 김범준
    • 한국전자통신학회논문지
    • /
    • 제6권2호
    • /
    • pp.219-224
    • /
    • 2011
  • 현재 널리 확산되고 있는 모바일 인터넷 음성 서비스의 품질 관리는 기존의 계측기를 동원한 사후 측정 기반으로는 불가능하다. 보다 체계적인 품질 관리를 위하여 서비스 이용자 단말기에 품질 측정 소프트웨어를 설치하고 서비스 품질을 상시 측정하는 실시간 혹은 사전 품질 관리 체계가 제안된 바 있다. 제안된 품질 관리 체계가 실현되기 위한 필수적인 조건은 품질 측정 소프트웨어의 신뢰성이다. 따라서 본 논문에서는 개발된 품질 측정 소프트웨어의 신뢰성을 검증하기 위한 품질 측정을 실시하였고 그 결과에 대해서 논하고자 한다.

융복합 시대의 국가 SW R&D 프로젝트에 대한 품질활동관리 적정성 평가 방안 연구 (A study of appropriateness evaluation method for quality activity management of Software R&D Project)

  • 서영욱;채성욱
    • 디지털융복합연구
    • /
    • 제13권8호
    • /
    • pp.91-99
    • /
    • 2015
  • 최근에 소프트웨어(SW) 융복합 시대를 맞아 SW품질관리의 중요성에 대한 관심이 높아지고 있다. 이에 본 연구에서는 품질관리전담기관의 SW품질활동관리 적정성을 객관적으로 평가 할 수 있는 방안에 대하여 기존의 품질 활동관리 적정성 사례를 기반으로 새로운 적정성 평가 방안을 제안하고자 한다. 이를 위하여 다음과 같이 연구 목적을 세 가지로 설정한다. 첫째, 기존의 국가 SW R&D 프로젝트의 SW품질활동관리 적정성 평가의 문제점을 도출하고 분석한다. 둘째, 기존의 SW품질활동관리 적정성 평가에 대한 문제점을 극복할 수 있는 새로운 적정성 평가 방법을 제안한다. 셋째, 새로운 적정성 평가 방법을 WBS(World Best Software) 프로젝트를 대상으로 적용해서 그 가능성과 효과성에 대하여 살펴본다. 본 연구에서 새롭게 제시한 국가 SW R&D 품질활동관리 적정성 평가 프레임워크를 대형 SW R&D 프로젝트인 WBS 프로젝트의 2개 과제에 실질적으로 적용해봄으로써 새로운 품질활동관리 적정성 평가 프레임워크의 효과성과 실무 적용 가능성을 입증하였다.

Software Quality Metrics를 이용한 공학용 전산 프로그램의 품질특성 측정 (Quality Evaluation of Engineering Computer Programs Using Software Quality Metrics)

  • 조문성;남지희
    • 품질경영학회지
    • /
    • 제25권4호
    • /
    • pp.115-130
    • /
    • 1997
  • SQM (Software Quality Metrics) is a methodology whose primary objective is the measurement of compliances to requirements using a set of software life cycle properties called quality factors, which is based on the hierachical relationshiips between factors, criteria and elements. For this study, two factors (Correctness, Maintainability) and five criteria were selected. In addition, several tens of quality elements were developed to su, pp.rt them. Qualities of three computer programs which are being used for engineering purpose were measured. As a result, it is concluded that SQM is a valuable method for continuously monitoring the pulse of software quality development and that it can be used as a tool for software quality assurance.

  • PDF

Experiment design and human reliability in software quality control system

  • Park, Peom
    • 품질경영학회지
    • /
    • 제20권2호
    • /
    • pp.94-108
    • /
    • 1992
  • This study involves an experiment for the cognitive experiment design and the human reliability in software engineering. Its overall objectives are to analyze common-cause human domain error and reliability in human-software interaction. A laboratory study was performed to analyze software engineers' task behavior in software production and to identify software design factors contributing to the effects in common cause failure redundancy. Common-cause model and its function were developed, then the main experiment using programming experts was conducted in order to define a new cognitive paradigm, in the aspects of identification, pattern recognition, and behavior domain for human reliability and quality control in software development. The results and analytical procedures developed in this research can be applied to reliability improvement and cost reduction in software development for many applications. Results are also expected to provide guidelines for software engineering quality control and for more effective design of human-software interface system.

  • PDF