• Journal of Information Technology Applications and Management
• /
• v.25 no.3
• /
• pp.17-28
• /
• 2018

In this paper, an activity-oriented usability model is proposed. The usability model contains two types of characteristics: special-type characteristics of usability and sub-characteristics of usability. Workability, study-ability, and playability are, but do not exhaust, examples of special-type characteristic of usability. They correspond to working, studying, and playing using the software product, respectively. They represent the goal of using and can overlap each other. They are usability too by themselves. Navigate-ability, data-prepare-ability, data-input-ability, response-wait-ability, output-examine-ability, and output-utilize-ability are typical examples of sub-characteristics of usability. They correspond to navigating, preparing data, inputting data, waiting response, examining output, and utilizing the output data, respectively. They are not usability by themselves. They constitute usability together as a group. Assessing is the fundamental and indispensable aspect of quality. Without assessing, the concept of quality has little practical value. Satisfaction, effectiveness, and efficiency are the most typical sub-characteristics of usability in existing quality models, which correspond to the evaluation criteria of usability. In the activity-oriented usability model, however, only the user's satisfaction is included: Satisfaction is regarded as the operational definition of usability in the user's view. As the result, usability can be interpreted as the 'goodness for using, which is evaluated by the user. 'Three fundamental principles regarding software quality models are proposed too in this paper: Principles of Parsimony, Cohesiveness, and Inheritance. Discussions illustrate well that typical existing usability models violate these basic principles. Many authors have tried to define general usability models which can be applied to most kinds of software. The dream of the general and universal usability model, however, may be an illusion. The activity-oriented usability model is expected to serve as a prototype from which specialized usability models can be derived.

• Journal of the Korea Convergence Society
• /
• v.10 no.3
• /
• pp.59-65
• /
• 2019

In this paper, we propose a software quality measurement metrics of ISO / IEC 25023, which is newly proposed for software quality evaluation, to compare the difference with ISO / IEC 9126-2 which was used for software quality evaluation. In this paper, we propose a method for evaluating the quality of reliability based on the software reliability growth model among the eight quality characteristics presented in ISO / IEC 25023. Based on ISO / IEC 25023, software-quality evaluations demonstrate that there is some risk in evaluating reliability when based on data.

• KIPS Transactions on Software and Data Engineering
• /
• v.7 no.10
• /
• pp.383-386
• /
• 2018

As the importance of software has been recognized, the impact of embedded software quality on product quality has become increasingly important. Therefore, in this study, reliability is extracted according to the embedded characteristics and it is described that the reliability evaluation of the embedded software is made easier.

• 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 Digital Convergence
• /
• v.11 no.3
• /
• pp.293-298
• /
• 2013

We consider about software quality nowadays. The company considers about software quality more and more compare to software development. We analyze the software testing data in this paper. We find the software effect according to the number of testing, the number of testing date, the number of fault according to characteristics. Also, we analyze the result by regression. Also, we propose the testing effect by sex.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.25 no.12
• /
• pp.1956-1959
• /
• 2021

AIS(Automatic Identification System) provides navigational information including identification, position, a ship's course and status to ground and other vessels. To obtain AIS Marine Equipment Approval Service, various requirements are required and meet the requirements International Standards. However, most of the requirements are to identify essential functions, response time, hardware requirements, and communication protocols of AIS. The requirements for the quality of SW are not sufficient or detailed, and the weight is relatively low. As role of SW grows and types become more diverse, AIS SW quality inspection is essential. In this paper, We apply eight-quality characteristics of ISO/IEC 25023 standard to improve SW coverage quality of AIS. Suggest additional AIS SW requirements based on the eight quality characteristics of ISO/IEC 25023 standard.

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

• The Journal of Information Technology and Database
• /
• v.7 no.1
• /
• pp.113-130
• /
• 2000

As software projects become larger and more complex, we need to take a more systematic approach to quality assurance. One plausible approach is the use of SQA (software quality assurance) methodology. Since this SQA methodology was not available, our study presents a SQA methodology. This methodology has a repository in which a set of quality assurance tasks with their related techniques and deliverables is defined and from which one can select only appropriate tasks based upon characteristics of project. This study further suggests a rule-based approach for supporting task selection process.

• Journal of Korean Society for Quality Management
• /
• v.29 no.4
• /
• pp.92-102
• /
• 2001

Software testing during development and operation should exercise to obtain the desired software quality and leave failure data set. So far, many software reliability models are classified and can be used to measure a software reliability only based on its failure history But, in practice, developers or testers of software systems must decide which existing software reliability model can be fitted. In this paper, we will show that an appropriate reliability model can be selected by considering relations between characteristics of each testing environment and models' assumptions. Several methods of software testing are presented and discussed. Also, unit test, integrated test, function test and system test that are sequentially exercised during development will be introduced.

• Journal of the Korean Operations Research and Management Science Society
• /
• v.25 no.3
• /
• pp.109-124
• /
• 2000

For rational human value judgement and evaluation, provision of clear evaluation data, objective value judgement criteria, and properly generalized methods are required. For instance, this is true for software quality evaluation, and the measure of software quality and the weighting method of evaluation target directly affect final decisions. However it is not easy to find a generalized method for the software quality evaluation or product selection, because of its complex characteristics. In this paper, we apply the qualitative preference method based on quantitative belief functions to find a general weighing method for the software quality evaluation. In particular, the qualitative preference method, in which the differentiated preference expression is possible, is conceptually expanded for general applications in future. For this purpose, we hierarchically differentiate the strong preference relation from the weak preference relation, and show an example of quantification of software quality evaluation on different applications, by comparing the qualitative preference method with AHP. We believe that the application domain of this method is not limited to the software quality evaluation and it is very useful to apply this results to other SE areas, e.g., metric selection with different views and riority determination of practices to be assessed in the SPICE.