• Proceedings of the Korean Society for Quality Management Conference
• /
• 1998.11a
• /
• pp.43-50
• /
• 1998

The cause of software crisis is that software quality and productivity can not meet the requirement of software market. In order to resolve the software crisis, there are many approaches to be proposed. Software reuse is one of the high potential approaches to improve software quality and productivity. Some high-tech countries (like USA, Japan) have proposed and studied the topics of software reuse in 1970 and got several results. In software development procedure, the products of detailed design and implement phases are simple, definite and suitable for reuse. In this paper, the necessary documents of reusable software component will be proposed, and how to select and evaluate the software components with high reuse potential and high quality will be discussed and recommended.

• Management & Information Systems Review
• /
• v.18
• /
• pp.201-222
• /
• 2006

As the competition between countries has become higher and the notion of software quality has been widely spread. it has been necessary to develop technologies that can ensure and produce high quality software. With the advent of information-oriented society. quality control has to transfer to the quality control activities focused on software system instead of those activities focused on hardware system. If so, how do we get to handle the quality control on the basis of the new approach. Also, as software applications have grown. so too has the importance of software quality. In order to manage software quality, the technology to specify and evaluate both the software product quality and development process quality objectively quantitatively is most important. To produce products of good quality, we need a more progressive quality control system according to the need of software development life cycle. In other words, we do software right the first time or build quality in the process. On the basis intermediate and final time or build quality in the process. On the basis of data achieved, we can evaluate the products according to the consequences of the data, What are the problems to contrive the software quality control system?, we con promote the quality of products. To achieved that goal, we con provide a suitable the technique and method of software quality control.

• Journal of Information Technology Applications and Management
• /
• v.26 no.2
• /
• pp.111-123
• /
• 2019

In this paper, software activity, software activity instance, and the quality of the activity instance are defined as the 'activity which is performed on the software product by a person or a group of persons,' the 'distinctive and individual performance of software activity,' and the 'performer's evaluation on how good or bad his/her own activity instance is,' respectively. The representative values of the instance quality population associated with a product and its sub-population are defined as the (software) activity quality and activity quality characteristic of the product, respectively. The activity quality model in this paper classifies activity quality characteristics according to the classification hierarchy of software activity by the goal. In the model, a quality characteristic can have two types of sub-characteristics : Special sub-characteristic and component sub-characteristic, where the former is its super-characteristic too simultaneously and the latter is not its super-characteristic but a part of its super-characteristic. The activity quality model is parsimonious, coherent, and easy to understand and use. The activity quality model can serve as a corner stone on which a software quality body of knowledge, which constituted with a set of models parsimonious, coherent, and easy to understand and use and the theories explaining the cause-and-relationships among the models, can be built. The body of knowledge can be called the (grand) activity-centric quality model of software.

• Journal of Information Technology Applications and Management
• /
• v.23 no.3
• /
• pp.71-86
• /
• 2016

This paper proposes a new software quality model composed of a hierarchy of software quality views and three software quality characteristics models. The software view hierarchy is composed of two levels : end view and means view at the first level, contingency view and intrinsic view as sub-views of means view. Three software quality characteristics models are activity quality characteristics model, contingency quality characteristics model, and intrinsic quality characteristics model, which correspond to end view, contingency view, and intrinsic view respectively. This paper also reclassifies characteristics of ISO/IEC 25000 series SQuaRE's software product quality model according to the proposed software quality model. The results illustrate clearly the shortcomings of SQuaRE's product quality model and how to overcome them. First of all, most of SQuaRE's product characteristics should be redefined and conceptually clarified according to the views on which they are really rested. Much more characteristics should be supplemented too. After that, rigorous empirical researches will become relevant. Causal relationships between activity quality characteristics and characteristics of means view should be empirically researched.

• Management & Information Systems Review
• /
• v.15
• /
• pp.245-262
• /
• 2004

As the competition between countries has become higher and the notion of software quality has been widely spread. it has been necessary to develop technologies that can ensure and produce high quality software. With the advent of information-oriented society. quality control has to transfer to the quality control activities focused on software system instead of those activities focused on hardware system. If so, how do we get to handle the quality control on the basis of the new approach. Also, as software applications have grown, so too has the importance of software quality. In order to manage software quality, the technology to specify and evaluate both the software product quality and development process quality objectively quantitatively is most important. To produce products of good quality, we need a more progressive quality control system according to the need of software development life cycle. In other words, we do software right the first time or build quality in the process. On the basis intermediate and final time or build quality in the process. On the basis of data achieved, we can evaluate the products according to the consequences of the data, What are the problems to contrive the software quality control system?, we con promote the quality of products. To achieved that goal, we con provide a suitable the technique and method of software quality control.

• Journal of Korean Society for Quality Management
• /
• v.29 no.2
• /
• pp.120-130
• /
• 2001

In this paper, the QFD(quality function deployment) technique is used to acquire the quality requirements of package software which is sold in commercial software shop. To select the principal quality characteristics of package software, an user survey was conducted for a quality model developed based on the international standards and the previous research. The software user is divided into three groups: the general user, the expert, and the developer. Based on the survey results, the top 10 quality characteristics are selected including accuracy, suitability, installability, de-installability, and maturaty. Then, the QFD technique is applied to choose the software quality attributes which have strong correlation with the selected quality characteristics, some of which are traceability, accuracy, modularity, completeness, and self-descriptiveness. The developed procedure can be used in evaluating the quality of package software with lower costs and efforts.

• The Journal of the Korea institute of electronic communication sciences
• /
• v.6 no.2
• /
• pp.219-224
• /
• 2011

The quality management for mobile internet voice services currently being used widely cannot be achieved by the conventional quality management depending on a specific measurement equipment. For more systematic quality management, a real-time or preventive quality management scheme is proposed. The proposed scheme required a quality management software installed in a service user's terminal. In order to implement and realize the proposed scheme, it is a very important issue to ensure the reliability of the measurement results from the developed quality management software. Therefore, we have performed a large number of tests to verify the reliability of the software and discuss on the results in this paper.

• Journal of Digital Convergence
• /
• v.13 no.8
• /
• pp.91-99
• /
• 2015

Reviewing the previous researches related to SW quality, we find that they are mostly quality evaluation models for SW quality improvement and maturity-design models for software project management evaluation. There are few studies for the appropriateness of SW quality management by Quality Control(QC) functions. Moreover, they are bound for government's SW R&D projects in the view of the third party. Therefore, we propose means for the objective evaluation of SW quality management's appropriateness by QC functions. For this reason, there are three research proposes in our study as follows. Firstly, we produce problems for the evaluation of the existing government's SW R&D project management's appropriateness. Secondly, to overcome the drawbacks for the evaluation of the appropriateness of SW quality management, new appropriateness evaluation methods are proposed. Lastly, we investigate the availability and effectiveness of the appropriateness evaluation methods for WBS projects.

• Journal of Korean Society for Quality Management
• /
• v.25 no.4
• /
• pp.115-130
• /
• 1997

SQM (Software Quality Metrics) is a methodology whose primary objective is the measurement of compliances to requirements using a set of software life cycle properties called quality factors, which is based on the hierachical relationshiips between factors, criteria and elements. For this study, two factors (Correctness, Maintainability) and five criteria were selected. In addition, several tens of quality elements were developed to su, pp.rt them. Qualities of three computer programs which are being used for engineering purpose were measured. As a result, it is concluded that SQM is a valuable method for continuously monitoring the pulse of software quality development and that it can be used as a tool for software quality assurance.

• Journal of Korean Society for Quality Management
• /
• v.20 no.2
• /
• pp.94-108
• /
• 1992

This study involves an experiment for the cognitive experiment design and the human reliability in software engineering. Its overall objectives are to analyze common-cause human domain error and reliability in human-software interaction. A laboratory study was performed to analyze software engineers' task behavior in software production and to identify software design factors contributing to the effects in common cause failure redundancy. Common-cause model and its function were developed, then the main experiment using programming experts was conducted in order to define a new cognitive paradigm, in the aspects of identification, pattern recognition, and behavior domain for human reliability and quality control in software development. The results and analytical procedures developed in this research can be applied to reliability improvement and cost reduction in software development for many applications. Results are also expected to provide guidelines for software engineering quality control and for more effective design of human-software interface system.