• Journal of Korean Society for Quality Management
• /
• v.31 no.1
• /
• pp.76-89
• /
• 2003

Recently, CMM have been recognized as a critical factor to validate the competitiveness of software organizations, even if the organizations have already achieved the ISO9001 certification. Furthermore, the new version of ISO9001:2000 is being required instead of ISO9001:1994. Both CMM and ISO9001 have a common point that they pursuit quality improvement for the organizations processes and products. Therefore, it is important to understand the similarities of specific requirements between the two models in software organizations which attempt to employ both of the models. From this background, this paper compares CMM and ISO9001 by considering the versions in 1994 and 2000 of ISO9001. The results of this research are likely to help software organizations ma]fe a decision for a strategy to adopt CMM and ISO9001.

• Proceedings of the Korea Inteligent Information System Society Conference
• /
• 2003.05a
• /
• pp.287-296
• /
• 2003

Recently, CMM have been recognized as a critical factor to validate the competitiveness of software organizations, even if the organizations have already achieved the ISO9001 certification. Furthermore, the new version of ISO9001:2000 is being required instead of ISO9001:1994. Both CMM and ISO9001 have a common point 1ha t they pursuit quality improvement fur the organizations processes and products. Therefore, it is important to understand the similarities of specific requirements between the two models in software organizations which attempt to employ both of the models. from this background, this paper compares CMM and ISO9001 by considering the versions in 1994 and 2000 of ISO9001. The results of this research are likely to help software organizations make a decision for a strategy to adopt CMM and ISO9001.

• The KIPS Transactions:PartD
• /
• v.10D no.4
• /
• pp.719-726
• /
• 2003

A SPICE (Software Process Improvement and Capability dEtermination) and CMM (Capability Maturity Model) assessment can be considered as representative software process assessment models since assessors assign ratings to indicators and metrics to measure the capability of software precesses. But ail of process assessment models don't provide a subjective measurement procedure and metrics. In this paper we define basic quality process metrics and propose standard metrics for each process based on SPICE and CMM. This study also proposed a guideline for a subjective measurement procedure and the metrics are effectively use to SPI.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2003.11c
• /
• pp.1571-1574
• /
• 2003

소프트웨어 제품 및 서비스의 품질 향상을 위한 방법으로 개발 프로세스의 개선을 목적으로 시작된 SPA & SPI(Software Process Assessment & Software Process Improvement)가 그 효과와 필요성을 인정받고 국내에서도 서서히 기업에 널리 확산되는 추세이다. 하지만 기업 문화의 차이와 시간적, 공간적, 비용적 이유로 SPA의 확산 및 수행에 어려움이 있다. 본 논문에서는 SPA에 GDSS(Group Decision Support System)를 적용하여 좀 더 원활하게 수행하고자 ISO/IEC TR 15504를 모델로 하는 심사 도구의 개발을 위한 연구를 하였다.

• Journal of the Korea Society of Computer and Information
• /
• v.18 no.2
• /
• pp.127-140
• /
• 2013

We explored the relationship between the level of change awareness and deployment of software process improvement (SPI) approaches using a competing values framework. To measure awareness level of organization's change, we used DICE framework provides means for predicting the outcome of change management initiatives. The four factors for organizaton's change: duration, integrity, commitment, and effort are evaluated and a score is calculated. The DICE(R) score is used to classify projects into win, worry, or woe zones. In this paper, we apply the DICE(R) score as an independent variable to predict the outcome of a software process improvement. Our results indicated that the Organization have a higher chance of success have the better outcome in software process improvement.

• Journal of Advanced Navigation Technology
• /
• v.13 no.6
• /
• pp.861-875
• /
• 2009

In order to make high quality software and high reliability software, systematic development management and organizational support are essential needed. Since 1990's Software process models such as ISO/IEC 15504 and CMMI have been used to improve organization capability. But these models have problems that are used to apply on large scaled organization or large project and so many practices are actually required. We present characteristics of ISO/IEC 15504, CMMI and K-model can easily apply to small and medium sized business or project, and propose the standard quality metric and accreditate procedure based on K-model for measuring quantitative quality level.

• Journal of the Korea Society of Computer and Information
• /
• v.19 no.2
• /
• pp.209-219
• /
• 2014

With rapid convergence of information technology and expending role of software, many organizations have taken interested in We explore the relationship between the level of change awareness and deployment of software process improvement (SPI) approaches using a competing values framework. To measure awareness level of organization's change, DICE framework which provides means for predicting the outcome of change management initiatives is used. The four factors for organizaton's change: duration, integrity, commitment, and effort are evaluated and a score is calculated. In this paper, we apply the DICE(R) score as an independent variable to predict the outcome of a software process improvement. Our results indicated that the Organization have a higher chance of success have the better outcome in software process improvement.

• The KIPS Transactions:PartD
• /
• v.13D no.3 s.106
• /
• pp.415-424
• /
• 2006

There are increasing numbers of foreign and domestic organizations that are using CMM/CMMI to establish their processes and keep improving them. CMMI and IDEAL models of SEI provide the best practices of processes and guide the organization using them based on processes maturity levels. However, they do not deal with their tools or methods that describe how to implement the processes in the organization. Therefore, in this paper, we developed a method in which various tools and statistical methodology of 6 sigma are applied to identify the process areas to be improved, to extract problems in those areas and to prioritize them. We expect this paper can contribute to the organizations that are searching for practical way of implementing CMMI based software process improvement and of identifying improvement items systematically. Also this method will be used to understand the result of improvement activities quantitatively.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2006.05a
• /
• pp.235-238
• /
• 2006

최근 많은 기업들은 효과적인 소프트웨어 프로세스 개선을 위해 SPICE와 CMMI 프로세스 심사 표준을 도입하려는 노력을 하고 있다. 이러한 표준을 통해 효과적인 개선하기 위해서는 개선점과 위험을 식별하고 이들 이슈들을 소프트웨어 개발환경(software development environment)에 적용시켜서 조직의 비젼(organization vision)에 대응한 작업성능(work performance)를 높여야한다. 지속적인 개선을 필요로 하는 조직은 현재의 작업성능을 측정하고 이를 개선하기 위한 개선점을 찾아내는 능력과 경험을 축적하여 체계적으로 관리하는 것이 중요하다. 하지만 기존의 SPI 모델들은 무엇을 수행해야 하는지에 대한 지침은 제공하고 있지만, 정량적인 작업성능 측정 및 특정 환경의 소프트웨어 개발 조직의 SPI를 위해 필요한 구체적인 지침을 제시하고 있지는 않다. 따라서, 본 논문에서는 이러한 조직의 작업성능 측정 및 조직의 개선경험을 축적하여 프로세스를 개선전략에 반영하여 조직의 비젼에 최적한 전략을 제공해주는 OTEM(Opportunity Tree Enterprise Model)을 제안한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2012.04a
• /
• pp.1167-1170
• /
• 2012

SW 기업들이 SW 프로세스 개선(Software Process Improvement; SPI)을 개선하기 위해 많은 관심과 노력을 투입해 왔음에도 불구하고, 이런 SW 프로세스 개선 활동이 풀질, 비용, 납기준수에 어떠한 영향을 주는지에 대한 구체적인 자료들이 부족한 편이다. 사례를 기반으로 하는 기존 연구의 결과는 대기업을 대상으로 특정 방법론의 효과성에 초점을 맞추고 있다. 본 연구에서는 SW 프로세스 개선활동들에 대한 이해의 폭을 넓히기 위해 국내 SW 개발 조직의 프로젝트 관리자를 대상으로 SW 프로세스의 이행과 프로젝트 비용에 대한 데이터를 수집하였다. 이를 기반으로 SW 프로세스 개선 모델이 제시하고 있는 가정사항인 SW 프로세스 능력수준이 높으면 프로젝트 성과가 좋은지를 분석하였다.