• Journal of Information Technology Services
• /
• v.6 no.3
• /
• pp.129-139
• /
• 2007

It is essential to perform the software process improvement activities to reinforce the software quality. Some companies are trying to improve the software process capability by establishing and implementing the software process improvement strategies voluntarily. But, the whole software industry is not active yet in terms of software process improvement. In this paper, we surveyed 'Software Process Capability Level' of software companies, analyzed the strength and weakness of the companies and provided with systematic approaches to improve Software Process capability. So, this paper contributes that software companies vigorously focus on the Software Process Improvement and eventually have the global competitiveness in terms of software quality.

• Journal of Korean Society for Quality Management
• /
• v.30 no.1
• /
• pp.22-46
• /
• 2002

Recently, increasing attention has been paid to building the software quality and software productivity due to ongoing software crisis. To overcome such problem, one of the many alternatives is to use the capability maturity model (CMM) suggested by the Software Engineering Institute(SEI), focusing on the improvement of software progress. This research is proposed the theoretical framework for CMM based on the previous studies, and review the status of software process on the software development organization. We then examine the impact of the software process capability on the organizational performance including financial measures and non-financial measures. Hypotheses on software process capability were tested 144 organizational units. The 62.5% of foreign companies are distribute to the second and third level, the Korean firms in this study are indicated the first level. Result indicate that maturity of software process may be served the key predictor of organizational performance, in particular the positive relationship between the software process and non-financial performance index such as customer service, IT Infrastructure, marketing, supplier and purchaser, production and operation.

• Journal of the Korean Operations Research and Management Science Society
• /
• v.27 no.3
• /
• pp.1-19
• /
• 2002

Recently, increasing attention has been paid to building a successful software process in Information System(IS) implementation. This study establishes software process model as a key predictor of organizational performance. We propose a theoretical framework for capability maturity model derived from the Software Engineering Institute(SEI). This paper identify the process-related variables, financial performance and non-financial performance from the relevant literature and clarify the concept of software process by distinguishing between its component and determinants. We then examine the impact of software process on organizational performance. Hypotheses on software process were tested for 36 enterprises including 118 organizational units. Results indicate that software process capability may serve as a key predictor of organizational performance. Software process maturity found to be positively influenced on the financial and non-financial performance, while investment of information technology as a mediating variable not significantly affected to the performance.

• Proceedings of the Safety Management and Science Conference
• /
• 2007.04a
• /
• pp.437-448
• /
• 2007

This paper introduce information technology of software process assessment. It consists of eight parts such as concepts and introductory guide, a reference model for processes and process capability, performing an assessment, guide to performing assessments, an assessment model and indicator guidance, guide to competency of assessors, guide for use in process improvement, and guide for use in determining supplier process capability.

• Journal of the Korea Safety Management & Science
• /
• v.7 no.4
• /
• pp.141-163
• /
• 2005

The international SPICE (Software Process Improvement and Capability determination) Project ISO/IEC 15504(SPICE : Software Process Improvement and Capability determination) is an emerging International Standard on SPA(Software Process Assessment). A prime motivation for developing this standard has been the perceived need for an internationally recognized software process assessment framework that pulls together the existing public and proprietary models and methods. A SPICE assessment can be considered as one of representative SPA model since assessors assign ratings to indicators and metrics to measure the capability of software process. But this models doesn't provide a systematic measurement procedures and dynamic method for SPI(Software Process Improvement). Through the evaluation of SPICE is capable of providing a substantiated basis for using the notion of capability, as well as providing information for nacessary improvements to the standard using 6sigma process. As a result, this paper propose a measurement procedure and guidelines for application of 6sigma process to guarantee the reliability in SPI and suggest the structure to support SPI on overall organization.

• Journal of Information Technology Services
• /
• v.10 no.4
• /
• pp.191-204
• /
• 2011

Recently, many software companies are trying to improve the software quality and project outcome with more costs and efforts in development time. In the software convergence and integration environments, it is required efforts to gain high quality of software. In other words, it is required to utilize software engineering knowledge and technology for higher software quality and better software project productivity. The Software development productivity can be varied by software process capability according to building a framework for software development, selection and use of appropriate technology, human resource management. Software process capability will influence software project outcome which is the general opinion. This study provides empirical evidence about software engineering efforts and investment approach to lead software project performance. We measured the software engineering efforts by SW engineering level and analyzed the corelation between software engineering level and schedule deviation. And, we verified that this performance is affected by the size of software company. As a result, software process capability is important to build a infrastructure and develop systematically software project. The higher software engineering level can lead to improved software project performance.

• Convergence Security Journal
• /
• v.7 no.2
• /
• pp.49-55
• /
• 2007

Software failure time presented in the literature exhibit either constant, monotonic increasing or monotonic decreasing. For data analysis of software reliability model, data scale tools of trend analysis are developed. The methods of trend analysis are arithmetic mean test and Laplace trend test. Trend analysis only offer information of outline content. From the subdivision of this analysis, new attemp needs the side of the quality control. In this paper, we discuss process capability analysis using process capability indexs. Because of software failure interval time is pattern of nonnegative value, instead of capability analysis of suppose to normal distribution, capability analysis of process distribution using to Box-Cox transformation is attermpted. The used software failure time data for capability analysis of process is SS3, the result of analysis listed on this chapter 4 and 5. The practical use is presented.

• 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 KIEE Conference
• /
• 2006.10d
• /
• pp.244-246
• /
• 2006

Softwares in railway system are being used in the area of railway control system, directly associated to safety. Because the instinct characteristic of Software is uncertainty, Software development without safety insurance is very hazardous situation. In order to derive safety certification process in the railway system, certification and approval processes in the nuclear, aviation, and military area are studied. Software quality should be improved by two aspects : one is product aspect, another is process aspect. GS(Good Software) and ES(Excellent Software) certification can be exemplified in a product aspect approach. In those process certification, CMMI (Capability Maturity Model Integration) or SPICE (Software Process Improvement and Capability dEtermination : ISO/IEC15504) is being used as models for assessing process maturity of organization. Following the studies, safety management procedure in the railway system is suggested.

• Journal of KIISE:Software and Applications
• /
• v.33 no.3
• /
• pp.267-276
• /
• 2006

IS 15504 and CMMI, etc are already proven models as a framework to improve the maturity of enterprise software development. However, these process maturity models can't present the detail and practical methods with which people can enhance the development competence and efficiency of an enterprise. Each company or organization should develop its own model or tailor the above models to make them suitable to its unique environment such as product or technology domain, scale of business or organization and cultural environment, etc for the practical application. This study introduces experiences that organizational and technical capability was reinforced based on our own process capability improvement model to improve software development strength in Samsung Electronics. We modeled our own improvement model which is expanded from IS 15504 against our experience. Our SPI model expanded its capability to organizational and technical issues including newly introduced capability level for evaluating its implementation. We expect that our study would give contribution for presenting industry experience and reference model for reinforcing software development competence.