• Journal of Information Technology Applications and Management
• /
• 제26권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
• /
• 제23권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.

• Journal of Information Technology Applications and Management
• /
• 제24권3호
• /
• pp.73-92
• /
• 2017

Usability is one of the most important concepts regarding software quality. It can be interpreted as the goodness associated with using the software product. This paper distinguishes the goodness of an individual using experience and the goodness of a product for using. This paper proposes a software quality view model which classifies software quality views into two broad categories of end view and means view. End view includes long-term view and short-term view which is classified further into performer's view on software activity and third party's view on software activity. Means view includes intrinsic view and contingency view. The analysis of ISO 25000 Series SQuaRE demonstrates the necessity to decompose product quality model and quality in use model into five models corresponding to the software quality views respectively. The analysis on playability shows that the universal definition of usability may be an illusion. The results provide the theoretical basis to build a comprehensive and consistent body of knowledge regarding software quality, which is consisted with the set of quality models and the theories explaining the relationships among the elements of the models.

• The Transactions of the Korea Information Processing Society
• /
• 제6권10호
• /
• pp.2680-2692
• /
• 1999

Software quality is classified by quality of process and product. In experience of Quality Management, it is known that quality level of product as it depends on goodness and badness of process and organization. As a result, improvement of software process has been important subject. According as this trends, ISO 12207 is publicated as standard of software life cycle process by ISO. For UML based object oriented development process, it is necessary that we should research detailed definition of activity and task of ISO 12207 process which is added, deleted or tailored in according to organization and project characteristics. In this thesis, by according with ISO 12207 software life cycle process, UML based object oriented development process is proposed. This process is composed of 7 steps and 19 activities including development phase, activity and product to improve quality of reliability. Usefulness of object oriented process for improvement of software quality is proved at three ways, which are comparative analysis of process characteristics, SPICE process evaluation and SPICE rick analysis.

• Management & Information Systems Review
• /
• 제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 Information Technology Applications and Management
• /
• 제25권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.

• IE interfaces
• /
• 제25권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 the Korean Society of Industry Convergence
• /
• 제20권4호
• /
• pp.265-273
• /
• 2017

Major industries in Gyeongnam area include robot and automobile manufacturing, shipbuilding, and aviation. According to the research, the mechanical part of the products has been advanced, but awareness over the improvement of quality of the software still lacks. The quality performance test presently conducted by the companies in Gyeongnam is mostly the manual performance test performed by the program manager. In order to systematize this and extend the range of using software testing tools, the current study intends to suggest the necessity for conducting a survey on demand to improve performance and securing testing tools such as measured data analysis. Accordingly, this study is going to investigate 33 companies in Gyeongnam related with software in each of the major business areas centering around the actual field and examine activities related to software quality. And after figuring out the current status of retaining testing tools, the study will suggest the ways to enhance recognition over software quality and propose ultimate solutions to solve the problems on the current stage by finding out how to share information as much as possible in order to lay the foundation for extending the range of activity for the sake of software quality.

• The Transactions of the Korea Information Processing Society
• /
• 제4권8호
• /
• pp.1995-2006
• /
• 1997

Because of formlessness and sightlessness of software, sytematic quality management is hard to implement. But we attemped collective quality management as hardware production by configuration management and settled on software quality management standard outlines. We are implementing efficient quality management by software quality management according as these standard guidelines. In this study, we study error management supporting functions as an attempt of development of software quality management supporting system which can support quality management activity by reduction and early finding of error input, and represent various visual output elements which can help error management supporting functions. And we represent the background of construction of this software quality management system and searched effects which we can get when we use the error management supporting function.

• Journal of KIISE:Software and Applications
• /
• 제36권7호
• /
• pp.531-538
• /
• 2009

Domestic software market is struggling with product's low quality and low return-on-investment. The cause for the problems is due to unclear requirements at the early stage of software project. Studies show that, to lessen the problem, the requirements specification must reflect the right project scope and quantifiable quality goal. To achieve such features, this paper describes a standard guideline for SRS (Software Requirements Specification), which helps in defining the scope of project, measuring and quantifying quality, linking and tracing of requirements, and improving usability. The proposed SRS enables separating the requirements analysis activity from implementation activity and thus can improve subcontract management process in software project.