• The Journal of Information Systems
• /
• v.19 no.2
• /
• pp.97-118
• /
• 2010

Software Process Improvement(SPI) has been a challenging issue to software organizations. The factors affecting SPI were analysed for improving software development processes. Numerous studies suggested influencing factors, and assessment models were utilized for software improvement. This research suggested that SPI factors affecting on an organizational performance may vary according to the CMM(Capability Maturity Model) level. The moderating effects of organizational maturity level between the SPI factors and the organizational performance were empirically tested. This research found that all six SPI factors except for the resistance to change affected the organizational performance. The moderating effects of management support, goal alliances, participation, and effect analyses were empirically supported. These results can provide several implications or a practical guidance to academic and industry professionals.

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

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

• 한국IT서비스학회:학술대회논문집
• /
• 2005.05a
• /
• pp.418-426
• /
• 2005

• The KIPS Transactions:PartD
• /
• v.17D no.3
• /
• pp.203-208
• /
• 2010

This study improves the productivity of software development of open-market systems using agile methodology. The current processes of an open-market system are analyzed and inefficient processes are identified which are changed by applying the agile practice principles in Lean software. This study analyzes the process lead times and defects after the processes are changed to see the improvement effect.

• The Transactions of the Korea Information Processing Society
• /
• v.5 no.4
• /
• pp.904-914
• /
• 1998

BPR(Business Process Reengineering), a radical improvement approach of business process, has been paying attention, and work-flow management and automation has been concentrated on progress velocity of business process and productivity of engineers. In software engineering, software process engineering which focus to process begin to be watched, and for the purpose of software productivity and quality progress and reduction of development term, study on SPR(Software Process Reengineering) is being progressed. In this paper, made workflow analysis and design method for construction of work-flow management system of software process to stand firm process reengineering methodology. In other words, we studied modeling process methods for SPR process, and software process structure and workflow analysis method which construct software process workflow model and specification definition method of workflow software.

• The Journal of Industrial Distribution & Business
• /
• v.7 no.1
• /
• pp.11-14
• /
• 2016

Purpose - The study aims to show the successful application of Six Sigma in software companies for process improvement. Research design, data and methodology - A mixed methodology has been used which include both qualitative and quantitative research. In the qualitative research methodology part, a detailed and comprehensive literature study have been carried out. The literature study consists of articles, books, web materials, discussion forms and others. In the quantitative research methodology part, interviews have been conducted. Results - Six sigma is the practical application of a theoretical statistical measurement that equates to 3.4 defects per million opportunities -a position of practically zero defects for any process or service. Initially originating in Motorola Inc. in 1985 as a response to drastic quality improvement pressures from the threat of Japanese competition, it quickly gained many followers particularly G.E., Allied Signal, Ford Motor Company etc. and more recently attentions have shifted to service environments. There are still some problems and misconceptions existed about the applicability of Six Sigma in software companies. Conclusions - The paper concludes that Six Sigma can bring large benefits for software companies too. Furthermore, software companies have already started to implement Six Sigma approach, like Ericsson, Tata Consultancy Service, etc.

• The Korean Journal of Applied Statistics
• /
• v.28 no.6
• /
• pp.1257-1273
• /
• 2015

The development process of Embedded Software (SW) is gathering interest due to the increased importance of SW in mobile products. According to tough competition and the growing size of the Embedded SW, there is a demand for a new effective way to improve the SW development process, based on customer and market quality aspects, rather than focusing on defect removals in individual SW modules. We review 103 SW improvement projects from the area of mobile phones in order to check the effectiveness of Six Sigma which is the standard for the process improvement statistical tools and methods.

• The KIPS Transactions:PartD
• /
• v.15D no.4
• /
• pp.523-530
• /
• 2008

There are many defects that cause the process improvement of lifecycle problems during software development. This paper propose the management method of risk items that removes and manages the lifecycle problems as well. For the similar projects, we can estimate defects and prepare to solve them by using domain expert knowledge and the state analysis of defect items, which can greatly improve the software process. This research provides solution of management of risk items problem and detection of defect transition and its prevention and causes that happen on software development. Also, In this paper propose to making quantity of degree and transition phase.

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