• Journal of KIISE:Software and Applications
• /
• v.32 no.3
• /
• pp.163-172
• /
• 2005

Product Line Engineering (PLE) has been widely accepted as a representative software reuse methodology by using core assets. Product line architecture (PLA) is a key element of core assets. However, current research works on designing PLA do not provide sufficient and detailed guidelines of defining PLA and reflecting variability in the architecture. In this paper, we present a reference model of PLA and propose a process to design PLA with detailed instructions. Especially architectural variability is codified by describing decision model depending variation points and traced through PLA activities. The proposed process would make it feasible to apply PLE to practice areas.

• Journal of Information Technology Applications and Management
• /
• v.11 no.2
• /
• pp.15-27
• /
• 2004

Most software projects inevitably involve various types and degrees of uncertainty. Without proper risk assessment and coordination, software projects can easily run out of control and consume significant additional resource. Thus, risk management techniques are critical issues to information system researchers. Previous empirical studies of U.S. software firms support the adoption of development standardization and user requirement analysis techniques in risk-based software project management. Using data collected from software projects developed in Korea during 1999-2000, we conduct a comparative study to determine how risk management strategies impact software product and process performance in countries with dissimilar IT capabilities. In addition, we offer an alternative conceptualization of residual performance risk. We show that the use of residual performance risk as an intervening variable is inappropriate in IT developing countries like Korea where the role of late stage risk control remedies are critical. A revised model is proposed that generates more reliable empirical implications for Korean software projects.

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

• Journal of KIISE:Software and Applications
• /
• v.26 no.12
• /
• pp.1455-1467
• /
• 1999

소프트웨어 품질을 정의하기 위한 여러 가지 소프트웨어 품질 모형(SQM : Software Quality Model)이 개발되어 왔다. 이 모형들은 두 가지 목적을 가진다. 한 가지는 소프트웨어 품질 측정이고, 또 다른 목적은 개발 프로세스에서의 소프트웨어 품질 제어이다. 국제 표준인 ISO/IEC 9126은 소프트웨어 측정을 위한 소프트웨어 품질 모형을 제시하였다. ISO/IEC 9126의 품질 모형은 사용 관점에서 소프트웨어 품질을 정의한 모형이다. 이 모형은 개발 프로세스에서의 품질 제어를 하는 측면에서는 불완전한 모형이다. 소프트웨어의 품질이 프로세스 내에서 어떻게 만들어지는지 볼 수 없는 모형이기 때문이다. 따라서, 개발 관점에서의 소프트웨어 품질 모형이 필요하다.본 논문에서는 사용 관점인 ISO/IEC 9126 품질 모형을 기반으로 하여 개발 관점에서의 소프트웨어 품질 모형을 제안한다. 이 모형은 ISO/IEC 9126과 같이 하위 품질 요소가 중복되지 않는 계층적 품질 모형이면서, 개발 프로세스 내에서 제어 가능한 제품 특성에 기반을 둔 개발 관점의 소프트웨어 품질 모형이다. 본 논문에서는 소프트웨어 품질 모형 구축 시, 품질 속성간의 선후조건관계를 설정하여 품질 속성간 중복되었던 제품 특성을 한 품질 속성 내 귀속시킨다. 품질 속성 별 제품 특성을 기반으로, 프로세스 내에서 제품 특성을 측정하는 메트릭스를 제안한다. 본 논문에서 제안한 품질 모형과 ISO/IEC 9126을 비롯한 기존 품질 모형과 비교 분석한다.Abstract Several SQMs(Software Quality Models) have been developed to define a software quality. These models have two goals. One is to measure a software quality, the other is to control a software quality. The SQM of ISO/IEC 9126 is defined from the user's viewpoint. This model is an incomplete model in controlling a software quality in the development process. Since this model cannot show how to build a high quality software, the SQM of the developer's view is needed.We suggest the SQM of the developer's view. This model is a completely hierarchical model and is based on product properties. For this model, we define implicative relations among quality attributes for 1:m relations of quality attributes and product properties. So, we solve the problem of a quality attribute overlapping with other quality attributes. We suggest metrics based on our SQMs. Further, we evaluate our SQM by comparing our SQM with other SQMs.

• Convergence Security Journal
• /
• v.4 no.2
• /
• pp.71-75
• /
• 2004

The Common Criteria (CC) philosophy is to provide assurance based upon an evaluation of the IT product or system that is to be trusted. Evaluation has been the traditional means of providing assurance. It is essential that not only the customer' srequirements for software functionality should be satisfied but also the security requirements imposed on the software development should be effectively analyzed and implemented in contributing to the security objectives of customer's requirements. Unless suitable requirements are established at the start of the software development process, the re suiting end product, however well engineered, may not meet the objectives of its anticipated consumers. By the security evaluation, customer can sure about the quality of the products or sys tems they will buy and operate. In this paper, we propose a selection guide for If products by show ing relationship between security engineering and security evaluation and make help user and customer select appropriate products or system.

• Journal of Information Technology Services
• /
• v.10 no.3
• /
• pp.189-201
• /
• 2011

Feature models are widely used to model commonalities and variabilities among products during software product line development. Feature configurations are generated by selecting the features to be included in individual products. Automated tools to identify errors or inconsistencies in the feature models and configurations are essential to successful software product line engineering. This paper proposes a verification technique and tool based on semantic web technologies such as OWL, SWRL and Protege API. This approach checks the feature model and configuration based on predefined rules and provides information on existence of errors as well as the kinds of those errors. This approach is extensible due to ease of rule modification and may be easily applied to other environments because semantic web technologies can be easily integrated with other programming environments. This paper demonstrates how various semantic web-related technologies can support automatic verification of one kind of software development artifact, the feature model.

• Proceedings of the KSRS Conference
• /
• 1999.11a
• /
• pp.337-342
• /
• 1999

Satellite images without value-added processing may be nothing but artistic painting. That is in order to benefit from satellite images acquired from money-drinking satellites, we should utilize the paramount information in scientific world and practical lift that can be extracted from image. Hence, the Satellite Technology Research Center has developed a integrated software called "Valadd-Pro". In this paper, the main components of the Valadd-Pro are briefly introduced, its value-added product are compared with PCI$^{\circledR}$ commercial software. Based on the results, the performance of the Valadd-Pro is superior to that of PCI$^{\circledR}$ on 6000$\times$6000 SPOT panchromatic images.

• Proceedings of the Korea Information Assurance Society Conference
• /
• 2004.05a
• /
• pp.141-144
• /
• 2004

The Common Criteria (CC) philosophy is to provide assurance based upon an evaluation of the IT product or system that is to be trusted. Evaluation has been the traditional means of providing assurance. It is essential that not only the customer' srequirements for software functionality should be satisfied but also the security requirements imposed on the software development should be effectively analyzed and implemented in contributing to the security objectives of customer's requirements. Unless suitable requirements are established at the start of the software development process, the resulting end product, however well engineered, may not meet the objectives of its anticipated consumers. By the security evaluation, customer can sure about the quality of the products or systems they will buy and operate. In this paper, we propose a selection guide for If products by showing relationship between security engineering and security evaluation and make help user and customer select appropriate products or system.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.15 no.7
• /
• pp.2455-2475
• /
• 2021

Patient Navigation Program (PNP) is considered as an important implementation of health care systems that can assist in patient's treatment. Due to the feasibility of PNP implementation, a systematic reuse is needed for a wide adoption of PNP computerized system. SPL is one of the promising systematic reuse approaches for creating a reusable architecture to enabled reuse in several similar applications of PNP systems which has its own variations with other applications. However, stakeholder decision making which result from the imprecise, uncertain, and subjective nature of architecture selection based on quality attributes (QA) further hinders the development of the product line architecture. Therefore, this study aims to propose a quality-driven approach using Multi-Criteria Decision Analysis (MCDA) techniques for Software Product Line Architecture (SPLA) to have an objective selection based on the QA of stakeholders in the domain of PNP. There are two steps proposed to this approach. First, a clear representation of quality is proposed by extending feature model (FM) with QA feature to determine the QA in the early phase of architecture selection. Second, MCDA techniques were applied for architecture selection based on objective preference for certain QA in the domain of PNP. The result of the proposed approach is the implementation of the PNP system with SPLA that had been selected using MCDA techniques. Evaluation for the approach is done by checking the approach's applicability in a case study and stakeholder validation. Evaluation on ease of use and usefulness of the approach with selected stakeholders have shown positive responses. The evaluation results proved that the proposed approach assisted in the implementation of PNP systems.

• Journal of the Korea Society for Simulation
• /
• v.19 no.4
• /
• pp.179-188
• /
• 2010

The concern of Software Product Line(SPL) engineering is spreading widely because the program or product developers are able to satisfy the customer's demands quickly and give a way to handle maintenance efficiently. SPL is a reuse paradigm that reuse common parts and adopts variable parts optionally to form a differentiated product by analyzing domains. Purposes of this paper are to design an architecture which has a dynamic reconfiguration function and to develop basic components which are the basic unit of reconfiguration to raise the reuse level of the guided weapon system using the SPL. Initially we design an architecture and define basic components for developing a dynamic reconfigurable components based on SPL. Then we develop the composer for physical components and behavior components referenced by behavior models of OneSAF.