• The Transactions of the Korea Information Processing Society
• /
• v.1 no.2
• /
• pp.194-201
• /
• 1994

Recently, as application fields of software is extended, relative importance of software make a gradual increase and importance of development cost is being increased. However, as former evaluation model of development cost evaluate at the functional point of view for the most part, at this paper, I intend to propose evaluation model of software development cost COSMOS-Q(COSt MOdel for Subcontract-Quality) which one evaluate also in quality as well as function. The model proposed in this paper set the goal at software orderer evaluate software cost exactly with only order specification information. At this paper, I proposed cost evaluation model and evaluated it's validity refering to review result in ISO/SC7 about a software quality feature with extraction of quality feature factor which produce change of cost and set up the evaluation measure adoptable as order condition.

• IE interfaces
• /
• v.25 no.4
• /
• pp.416-421
• /
• 2012

One of the activities to improve software quality in ISO 26262 is to apply the design principles for software unit design and implementation mentioned in ISO 26262-6, including the evaluation activity. Before evaluation activity, the tool is compared and selected for evaluation. Because the results of the tool a company selected might have an effect on product quality. In this paper, we suggest the method to compare industrial static analysis tools with some of "MISRA C : 2004 Exemplar Suite" and all lessons learned from comparing tools are described. The result on comparison shows that we just couldn't rely on a result of Static Analysis Tool and need to have another appropriate processes and guidelines to evaluate a software.

• Journal of Information Technology Applications and Management
• /
• v.27 no.2
• /
• pp.37-50
• /
• 2020

This paper is very exploratory and addresses the issue 'Is a general quality model of software possible?'. If possible, how specific can/should it be?' ISO 25000 Series SQuaRE is generally regarded as a general quality model which can be applied to most kinds of software. Usability is one of the 8 characteristics of SQuaRE's Product Quality Model. It is the main issue associated with SQuaRE's Quality in Use Model too. it is the most important concept associated software quality since using is the only ultimate goal of software products. Playability, however, is generally regarded as a special type of usability, which can be applied to game software. This common idea contradicts with the idea that SQuaRE is valid for most kinds, at least many kinds, of software. The empirical evidences of this paper show that SQuaRE is too specific to be a general quality model of software.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2006.11a
• /
• pp.479-482
• /
• 2006

소프트웨어의 품질 특성은 크게 6가지로 나누어 평가되어지고 있다. 가능성, 신뢰성, 사용성, 효율성, 유지보수성, 이식성의 품질 특성중에서 신뢰성에 대한 평가가 상당히 중요하다는 인식을 받고 있다. 본 연구에서는 소프트웨어 신뢰성에 대한 평가 방법을 제시하고 소프트웨어를 시험하는 기관이나 소프트웨어 개발업체에서 작용할 수 있는 소프트웨어 신뢰성 평가 방법론에 대해서 연구하고 고장데이터를 적용하여 소프트웨어 신뢰성을 평가하는 평가 결과를 제시하였다.

• Journal of Information Processing Systems
• /
• v.7 no.3
• /
• pp.473-518
• /
• 2011

Software measurement is a key factor in managing, controlling, and improving the software development processes. Software quality is one of the most important factors for assessing the global competitive position of any software company. Thus the quantification of quality parameters and integrating them into quality models is very essential. Software quality criteria are not very easily measured and quantified. Many attempts have been made to exactly quantify the software quality parameters using various models such as ISO/IEC 9126 Quality Model, Boehm's Model, McCall's model, etc. In this paper an attempt has been made to provide a tool for precisely quantifying software quality factors with the help of quality factors stated in ISO/IEC 9126 model. Due to the unpredictable nature of the software quality attributes, the fuzzy multi criteria approach has been used to evolve the quality of the software.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.18 no.10
• /
• pp.2451-2461
• /
• 2014

Mobile application is software executing on smart devices regardless of the time and place. Many individuals and companies have provided a lot of mobile applications services. However, there is not certain standard in terms of application's quality evaluation because study is deficient compared with increase amount of development of mobile application. Moreover, mobile application basically has many special characteristics. For these reasons mobile application is required special standard of quality different from general software. To satisfy these needs, I design and propose mobile application evaluation model. Evaluation model is mapped by characteristics of mobile application based on ISO/IEC 25000's quality characteristics and propose each quality characteristics and metrics. For verification, scenario-based studies were applied to quality model and carried out.

• 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 the Korea Institute of Information and Communication Engineering
• /
• v.20 no.7
• /
• pp.1342-1354
• /
• 2016

As Internet, and hardware technology are in rapid process, using rate and penetration rate of Internet of Things are increasing. Internet of Things is the physical objects with network which embedded with electronics, software, sensors, and network. Smart Home-kit to operate refrigerators, washing machines, light bulbs, and such internet of things by a smartphone has been realized. However, it is difficult to use a good quality of software based on IoT. It is because that the study related to quality evaluation of software based on IoT is deficient compared with increase amount of IoT devices. Software based on IoT includes mobility, transportability, real time accessibility and hardware characteristics. Therefore, it is necessary to have differentiated quality standards and quality model. Software quality evaluation model for IoT is proposed to satisfy these needs. Evaluation model is mapped by characteristics of IoT software based on ISO/IEC 25000's quality characteristics. Scenario based studies were applied to quality model for verification.

• Journal of The Korean Association of Information Education
• /
• v.2 no.1
• /
• pp.35-51
• /
• 1998

Software reliability growth model is one of the evaluation methods, software quality which quantitatively calculates the software reliability based on the number of errors detected. For correct and precise evaluation of reliability of certain software, the reliability model, which is considered to fit dose to real data should be selected as well. In this paper, the optimal model for specific test data was selected one of among five software reliability growth models based on NHPP(Non Homogeneous Poission Process), and in result reliability estimating scales(total expected number of errors, error detection rate, expected number of errors remaining in the software, reliability etc) could obtained. According to reliability estimating scales obtained, Software development and predicting optimal release point and finally in conducting systematic project management.

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