• 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 Information Technology Applications and Management
• /
• v.22 no.3
• /
• pp.143-167
• /
• 2015

This paper addresses the issue how the total life cycle cost may be minimized and how the cost should be allocated to the acquirer and developer. This paper differentiates post life cycle change (PLCC) endeavors from PLCC activities, rigorously classifies PLCC endeavors according to the result of PLCC endeavors, and rigorously defines the life cycle cost of a software product. This paper reviews classical definitions of software 'maintenance' types and proposes a new typology of PLCC activities too. The proposed classification schemes are exhaustive and mutually exclusive, and provide a new paradigm to review existing literatures regarding software cost estimation, software 'maintenance,' software evolution, and software architecture from a new perspective. This paper argues that the long-term interest of the acquirer is not protected properly because warranty period is typically too short and because the main concern of warranty service is given to removing the defects detected easily. Based on the observation that defects are caused solely by errors the developer has committed for software while defects are often induced by using for hardware (so, this paper cautiously proposes not to use the term 'maintenance' at all for software), this paper argues that the cost to remove defects should not be borne by the acquirer for software.

• Journal of Applied Reliability
• /
• v.16 no.2
• /
• pp.134-146
• /
• 2016

Purpose: Many domestic companies have to make out quantitative evaluation table in their proposal when they conduct the software R&D project. However, most of companies have a difficulty to select the evaluation items and criteria, also to derive a quantitative results. Therefore, we propose a method to derive the quantitative evaluation index by utilizing the ISO/IEC 9126-2. Methods: Analyzing ISO/IEC 9126-2, and we classify the quality metrics as high-classification and sub-classification for Web/App software, Embedded software and Installation software. Next, Conduct the metrics selection survey depending on importance and necessity. Then, carry out the case study. Verify the correspondence between evaluation items and criteria from original suggestion of company and from outcome by utilizing the ISO/IEC 9126-2 quality metrics. Results: It is possible to classify into two metrics, one for common software or one another for only special software. Furthermore, there is quality metrics that is more important and more necessary depending upon characteristics of the software. Conclusion: ISO/IEC 9126-2 quality metrics can be used to make an evaluation items and criteria for quantitative evaluation table of software product.

• Journal of Information Technology Applications and Management
• /
• v.24 no.2
• /
• pp.71-80
• /
• 2017

Software reliability is one of the most elementary and important problems in software development In order to find the software failure occurrence, the instantaneous failure rate function in the Poisson process can have a constant, incremental or decreasing tendency independently of the failure time. In this study, we compared the reliability performance of the software reliability model using the parameters of Pareto life distribution with the intensity decreasing pattern and the shape parameter of Erlang life distribution with the intensity increasing and decreasing pattern in the software product testing. In order to identify the software failure environment, the parametric estimation was applied to the maximum likelihood estimation method. Therefore, in this paper, we compare and evaluate software reliability by applying software failure time data. The reliability of the Erlang and Pareto life models is shown to be higher than that of the Pareto lifetime distribution model when the shape parameter is higher and the Erlang model is more reliable when the shape parameter is higher. Through this study, the software design department will be able to help the software design by applying various life distribution and shape parameters, and providing basic knowledge using software failure analysis.

• Journal of KIISE:Software and Applications
• /
• v.33 no.12
• /
• pp.1008-1021
• /
• 2006

Product line engineering(PLE) is one of the recent and effective reuse approaches that enables developing a number of applications by instantiating a core asset. Elements of a core asset are product line architecture(PLA), component, and decision model. Among these elements, PLA is the key element since it defines the overall structure of the core asset. Although numerous PLE methodologies have been introduced, it is still unclear what should be the elements of a PLA and how to systematically instantiate it for specific applications. Formal specifications can play a key role in defining detailed and precise instantiation process. In this paper, we first present a meta model of PLA and show how to specify PLA in a formal language, Object-Z. Then, we propose instantiation rules using formal specification and those rules precisely define constraints for instantiating PLA. By applying the proposed formal specification, we believe PLA instantiation can be carried out precisely and correctly, yielding high quality software development.

• Journal of KIISE:Software and Applications
• /
• v.33 no.5
• /
• pp.449-459
• /
• 2006

Product Line Engineering (PLE) has been widely accepted as a representative software reuse methodology by using core assets. As a key element of core assets, product line architecture (PLA) should be generic to a set of applications in the product line (PL). However, the difference between PLA and single system architecture has not been treated well enough, so evaluating PLA still remains as one of the difficult tasks in PLE. In this paper, we identify two intrinsic but overlooked issues in PLA; variability propagation chain and conflicts between architectural elements. And, we present a metric-based methodto evaluate PLA from the perspective of the two issues. We believe that the two issues in PLA and the evaluation method would make designing high-quality PLA more feasible and effective.

• The KIPS Transactions:PartD
• /
• v.12D no.1 s.97
• /
• pp.91-102
• /
• 2005

In the past it was generally felt that software quality was the same as product quality. But as the software industry is getting bigger and more complex, it has become hard to develop quality software that meets customers' needs just depending on product quality. Therefore, lately many domestic and foreign companies are making efforts to upgrade product quality by implementing Process Improvement. Measurement in Process Improvement activities enhances the effect of Process Improvement, and also identifies and helps the activities. In support of this paper, research on the measurement program was conducted based on the CMMI adopted by many domestic and foreign companies for their process improvement model. MA process area that deals with measurement process setup is one of the CMMI process areas and was the basis of the structure of the measurement program. This study presents differences of the measurement program for each level of CMMI and how to apply it. The results of this study can help a business to apply CMMI-based Process Improvement by backing up the structure of the measurement program. Furthermore, it can offer a roadmap for progress of the measurement program for each level.

• The Journal of Information Systems
• /
• v.18 no.4
• /
• pp.131-153
• /
• 2009

Due to the deterioration of the business environment, many companies become more interested in IT adoption to strengthen their internal competence. The recent expansion of the ERP adoption in the small and medium-sized enterprises (SMEs) can be interpreted as an example for this. However there are still a number of questions over the outsourcing effectiveness and its performance of IT adoption by characteristics of SMEs. This study aims to investigate the relationship between the software process quality and the product quality, and additionally the moderating effect of IT adoption factors, from the case of SMEs' ERP adoption by the outsourcing. For this purpose, the empirical analysis through the structural equation model has been carried out, based on the software quality model defined in ISO/IEC 15504 and ISO/IEC 9126. The result of analysis shows that the acquisition process quality can affect the product quality characteristics, currently applied in the national software quality certification, and this supports the practical usefulness of the ISO standard of software engineering. But another result shows that there is little moderating effect by IT adoption factors, in contrast to the expectation, and this can be explained due to the inappropriate measurement and the data constraint such as short duration-time of IT adoption. These can be used as an informative reference for continuing studies of the quality model application and the effect of IT adoption factors in SMEs.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 2004.05a
• /
• pp.39-43
• /
• 2004

A research shows that a new category of software, Collaborative Product Commerce (CPC), is now emerging, allowing discrete manufacturers to once again distinguish themselves on their products and innovations. CPC permits discrete manufacturers to significantly improve the core processes around the management functions associated with the complete product life cycle that are the basis of their existence. As a way to develop computing tools of CPC to support a design process of product, a web-based design supporting system was constructed in the paper. The system consists of C-Product system and Net Meeting Communication system to improve communications between designers and persons for verification of design. The product data files of C-Product system were designed by Pro/Engineer and converted to 3D Viewer format for being used in the web browser. Also, Net Meeting Communication system and Database were developed using ASP and Microsoft SQL 2000 Server to share diverse files that can be utilized to design on the web in real time.

• 한국전자현미경학회:학술대회논문집
• /
• 2005.11a
• /
• pp.201-202
• /
• 2005