• Management & Information Systems Review
• /
• v.25
• /
• pp.275-296
• /
• 2008

We tested the relationship of elements in influence about software performance. our research is detect the significant element in the software system. we affronted to find relation elements with software quality and seek what relationship is the most important in performance activity. this study's result will be useful for them ; first, give to product a high quality guide line to software developer. second, it will be use for basic information about in software examine research.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.15 no.8
• /
• pp.5227-5232
• /
• 2014

Better quality software can be made by eliminating the software product risk in the early stages. To achieve this task, a risk analysis system that can effectively track and manage risks that have severe effects on software quality is needed. The existing risk analysis systems have some weaknesses as they are applied to organizations. The major problems of those systems are that they require organizations to collect as much risk data at a time without providing a proper explanation and even without the support of a risk management process. This paper resolves those problems by developing a risk analysis system that offers methods of managing risks. In addition, the system provides the guidelines of which risks should be gathered for each step. The system also has functions to generate a range of strategy and analysis information on risks.

• Asia pacific journal of information systems
• /
• v.20 no.2
• /
• pp.39-62
• /
• 2010

As an engineered product, a software package has multiple dimensions that must be designed judiciously to enhance its competitive viability. Functionality, reliability and price are three such common dimensions. However, many software products are sold as bundles of individual components and the competitive impact of bundling has received less attention in the research literature. In this paper, we examine the implications of software vendors using bundling as an element of competitive strategy. A game theoretic model of the actions of an incumbent and a new entrant is developed and the impact on vendor and consumer welfare is analyzed. Numerical experiments with the model show that (i) increasing bundle size is an effective strategy for the incumbent to increase its payoff at the cost of the entrant's payoff and consumer surplus, especially when the entrant's quality is low (ii) in the presence of bundling, the entrant can still increase its own payoff and consumer surplus at the cost of the incumbent's payoff, by increasing product quality up to the level that best segments market demand with the incumbent and (iii) an increase in bundle size by the incumbent, or an increase in quality by the entrant, can both result in an increase of total surplus. Similar results are observed in a related case where the entrant offers free software bundles. Our results provide insights into how software vendors may strategically use bundling and quality as additional product dimensions in order to stay competitive in the market. These results also inform the competing vendors of the impact of bundling related public policy actions on their respective payoffs.

• Journal of KIISE:Software and Applications
• /
• v.36 no.7
• /
• pp.539-547
• /
• 2009

Software product line (SPL) engineering is an emerging paradigm for successful software reuse and has been adopted for various industrial and consumer products to improve their productivity and quality. However, most SPL methods require high initial costs and long development time, which makes many companies hesitate to adopt the SPL paradigm. In this paper we introduce a method to construct an SPL by extracting core assets from legacy components based on the feature model, which requires less initial time and effort. We also present a case study on cable set-top box software to illustrate the applicability of this method, and lessons learned that will provide guidelines for many companies to adopt the SPL paradigm.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.16 no.1
• /
• pp.691-696
• /
• 2015

The interest in software defects is growing. Companies are working on reducing them by various ways with a software development part, customer service part and quality management part. The defect data collected from them will be analyzed according to the condition and purpose to minimize the defect, and it will contribute to improving the quality of products. This study analyzed the software defect progress for companies based on the test maturity model, and set up the defect preventing process. They were applied to the project, and the number of defects decreased from 106 to 16. This study focused on the existing defect, which is a basic requirement for software quality management, and have importance by presenting a way to improve the software product quality with minimum resources.

• Proceedings of the KSR Conference
• /
• 2007.11a
• /
• pp.638-645
• /
• 2007

Computers are increasingly being introduced into safety and reliability critical systems. The safe and reliable operation of these systems cannot be taken for granted. Malfunctions of these systems can have potentially catastrophic consequences and they have already been involved in serious accidents. Software fault prevention, fault tolerance, fault removal and fault forecasting are the techniques to be used, implemented and verified for embedded software in critical systems as the contributors to safety and reliability of the software. To use them when developing a software product, a relationship must be established between them and the development processes, the methods and techniques to be used to develop software, as well as with the different product architectures. Railroad signaling system software is a safety-critical embedded software with realtime and high reliability requirements. The primary purpose of the safety management is to prevent the loss of lives or physical damages arising from potential hazards in the railroad signaling system. This study provides a systematic approach to analysis of potential hazards for their management during the system life cycle to assure the identification and definition of the most appropriate hazards.

• Journal of Internet Computing and Services
• /
• v.3 no.2
• /
• pp.109-119
• /
• 2002

Usability is defined by the effectiveness efficiency and satisfaction with which specified users can achieve a specified goal in the particular environment. This paper is not only to provide a framework for specifying the usability attributes of a product and establishing a comprehensive set of usability criteria, but also to asses usability metrics of the software. The Evaluation Tool for Software Usability are developed based on the properties of the a user interface using ISO standard and general usability principles with product-oriented view. It means that product has attributes contributing to determine the usability. This paper also suggests the way to weight the relative importance of the individual usability item depending on the software categories.

• KIPS Transactions on Software and Data Engineering
• /
• v.12 no.1
• /
• pp.1-18
• /
• 2023

Similar software is often developed with the Clone-And-Own (CAO) approach that copies and modifies existing artifacts. The CAO approach is considered as a bad practice because it makes maintenance difficult as the number of cloned products increases. Software product line engineering is a methodology that can solve the issue of the CAO approach by developing a product family through systematic reuse. Migrating product families that have been developed with the CAO approach to the product line engineering begins with finding, integrating, and building them as reusable assets. However, cloning occurs at various levels from directories to code lines, and their structures can be changed. This makes it difficult to build product line code base simply by finding clones. Successful migration thus requires unifying the source code's file path, class name, and method signature. This paper proposes a clustering method that identifies a set of similar codes scattered across product variants and some of their method full paths are different, so path unification is necessary. In order to show the effectiveness of the proposed method, we conducted an experiment using the Apo Games product line, which has evolved with the CAO approach. As a result, the average precision of clustering performed without preprocessing was 0.91 and the number of identified common clusters was 0, whereas our method showed 0.98 and 15 respectively.

• Journal of KIISE:Software and Applications
• /
• v.32 no.9
• /
• pp.835-846
• /
• 2005

A Product Line (PL) is a set of products (applications) that share common assets in a domain. Product Line Engineering (PLE) is a set of principles, techniques, mechanisms, and processes that enables the instantiation of produce lines. Core assets, the common assets, are created and instantiated to make products in PLE. Model Driven Architecture (MDA) is a new software development paradigm that emphasizes its feasibility with automatically developing product. Therefore, we can get advantages of both of the two paradigms, PLE and MDA, if core assets are represented as PIM in MDA with predefined automatic mechanism. PLE framework in the PIM level has to be interpreted by MDA tools. However, we do not have a standard UML profile for representing core assets. The research about representing PLE framework is not enough to make automatically core assets and products. We represent core asset in PIM level in terms of structural view and semantic view. We also suggest a method for representing architecture, component, workflow, algorithm, and decision model. The method of representing framework with PLE and MDA is used to improve productivity, applicability, maintainability and qualify of product.

• Corrosion Science and Technology
• /
• v.23 no.2
• /
• pp.131-138
• /
• 2024

This paper introduces Primetals Technologies' Through-Process Optimization (TPO) Services and Through-Process Quality Control (TPQC) System, which integrate domain knowledge, software, and automation expertise to assist steel producers in achieving operational excellence. TPQC collects high-resolution process and product data from the entire production route, providing visualizations and facilitating quality assurance. It also enables the application of artificial intelligence techniques to optimize processes, accelerate steel grade development, and enhance product quality. The main objective of TPO is to grow and digitize operational know-how, increase profitability, and better meet customer needs. The paper describes the contribution of these systems to achieving operational excellence, with a focus on quality assurance. Transparent and traceable production data is used for manual and automatic quality evaluation, resulting in product quality status and guiding the product disposition process. Deviation management is supported by rule-based and AI-based assistants, along with monitoring, alarming, and reporting functions ensuring early recognition of deviations. Embedded root cause proposals and their corrective and compensatory actions facilitate decision support to maintain product quality. Quality indicators and predictive quality models further enhance the efficiency of the quality assurance process. Utilizing the quality assurance software package, TPQC acts as a "one-truth" platform for product quality key players.