• Journal of Advanced Marine Engineering and Technology
• /
• v.32 no.4
• /
• pp.611-617
• /
• 2008

In ubiquitous environments, the content adaptable services can be dynamically provided to adapt the frequent changes of contexts. These services have common things that the kinds of context factors are limited to ubiquitous environment, though the contexts are flexible. To reuse service architecture can be reasonable for effective adaptable service. In this paper, we design a software architecture with product line techniques for content adaptable applications in ubiquitous environment. Description of product line is to define variation points and their variants, to find out the dependencies between them and to keep the model based architecture, their alternatives.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.04a
• /
• pp.673-675
• /
• 2001

본 논문에서는 Product line 개념을 활용하여 체계적으로 각 어플리케이션에 적합한 소프트웨어 테스트 프로세스를 생성할 수 있도록 하는 1)“소프트웨어 테스트 프로세스의 재사용 방안”을 제안하고, 2) 이를 자동화한 “소프트웨어 테스트 프로세스 생성 도구”프로토타입을 제시한다. “소프트웨어 테스트 프로세스의 재사용 방안”은 product line 개념에 따라 표준, 방법론과 도메인을 위한 개발 프로세스들의 공통점과 차이점을 분석하여 core asset들을 CBD개념의 컴포넌트들로 개발하고, 이 core asset들을 가지고 컴포넌트의 맞춤 패턴을 이용하여 손쉽게 각 어플리케이션에 적합한 테스트 프로세스를 생성할 수 있도록 한다. “소프트웨어 테스트 프로세스 생성도구”는 “소프트웨어 테스트 프로세스 재사용 방안”의 core asset 개발 단계에서 개발된 core asset들을 저장소에 재사용을 목적으로 저장하며, 프로덕트 개발 단계를 자동화하여 각 어플리케이션에 적합한 테스트 프로세스를 생성한다.

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

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

• Management & Information Systems Review
• /
• v.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.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.13 no.8
• /
• pp.4191-4211
• /
• 2019

Software product lines (SPLs) are complex software systems by nature due to their common reference architecture and interdependencies. Therefore, any form of evolution can lead to a more complex situation than a single system. On the other hand, software product lines are developed keeping long-term perspectives in mind, which are expected to have a considerable lifespan and a long-term investment. SPL development organizations need to consider software evolution in a systematic way due to their complexity and size. Addressing new user requirements over time is one of the most crucial factors in the successful implementation SPL. Thus, the addition of new requirements or the rapid context change is common in SPL products. To cope with rapid change several researchers have discussed the evolution of software product lines. However, for the evolution of an SPL, the literature did not present a systematic process that would define activities in such a way that would lead to the rapid evolution of software. Our study aims to provide a requirements-driven process that speeds up the requirements engineering process using social network sites in order to achieve rapid software evolution. We used classification, topic modeling, and sentiment extraction to elicit user requirements. Lastly, we conducted a case study on the smartwatch domain to validate our proposed approach. Our results show that users' opinions can contain useful information which can be used by software SPL organizations to evolve their products. Furthermore, our investigation results demonstrate that machine learning algorithms have the capacity to identify relevant information automatically.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.35 no.2
• /
• pp.57-63
• /
• 2012

Software release planning model of software product lines was formulated as a precedence-constrained multiple 0-1 knapsack problem. The purpose of the model was to maximize the total profit of an entire set of selected features in a software product line over a multi-release planning horizon. The solution approach is a dynamic programming procedure. Feasible solutions at each stage in dynamic programming are determined by using backward dynamic programming approach while dynamic programming for multi-release planning is forward approach. The pre-processing procedure with a heuristic and reduction algorithm was applied to the single-release problems corresponding to each stage in multi-release dynamic programming in order to reduce the problem size. The heuristic algorithm is used to find a lower bound to the problem. The reduction method makes use of the lower bound to fix a number of variables at either 0 or 1. Then the reduced problem can be solved easily by the dynamic programming approaches. These procedures keep on going until release t = T. A numerical example was developed to show how well the solution procedures in this research works on it. Future work in this area could include the development of a heuristic to obtain lower bounds closer to the optimal solution to the model in this article, as well as computational test of the heuristic algorithm and the exact solution approach developed in this paper. Also, more constraints reflecting the characteristics of software product lines may be added to the model. For instance, other resources such as multiple teams, each developing one product or a platform in a software product line could be added to the model.

• Proceedings of the Korean Society for Technology of Plasticity Conference
• /
• 1997.03a
• /
• pp.136-139
• /
• 1997

Applications of commercial software DEFORM-3DTM for 3-D simulation in extrusion process are developed for the analysis of twisting of extruded products. Because the elliptical shape has at least one line symmetry, the twisting is not occured during the extrusion. But, the results of extrusion simulation of the elliptical shape show that the twisted boundary of the die surface makes the material inside die surface rotate with the constant angular velocity. Otherwise, the simulation results of the S shaped product show that the twisting can be occured by the only 180$^{\circ}$rotation symmetry of S shape without no line symmetry and show that the angular velocity increases by the only 180$^{\circ}$rotation symmetry without no twisted die surface between on the die entrance section and on the die exit section. The results of the analysis show that the angular velocity of the extruded product changes with die length and friction condition.

• 한국IT서비스학회:학술대회논문집
• /
• 2005.05a
• /
• pp.365-371
• /
• 2005

S/W 제품계열(S/W Product Line)은 공통의 유사한 기능을 지닌 S/W 제품 또는 S/W 시스템의 집합을 의미한다. S/W 제품 계열을 통해 특정 영역의 시장과 용도의 요구사항을 만족하여 특정 S/W 제품 개발시 미리 구축된 S/W 아키텍처 등의 S/W 핵심 자산을 재사용하여 개발한다. S/W 제품계열 기반의 S/W 개발방식은 미리 구축된 S/W 핵심자산을 재사용함으로 처음부터 전체 시스템을 개발하는 방식보다 쉽고, 빠르게 S/W를 생산할 수 있다. S/W 기술 선진국들은 S/W 제품계열을 S/W 생산기술의 핵심 분야로 선장하고 중점적으로 기술 개발을 지원하고 있다. 미국의 CMU/SEI는 산업체 및 국방성과 함께 제품계열 프레임워크 4.0 (Product-Line Framework 4.0)을 개발하였고 유럽은 ITEA(IT for European Advancement) 프로그램에서 제품계열 기술 개발을 지원하고 있다. 그러나 국내의 경우 S/W 개발의 생산성 향상 방안으로 제품계열 기반 S/W 생산기술의 필요성을 인식하고 있으나, 기술 개발 투자는 미흡한 상황이다. 본 논문에서는 이러한 S/W 제품계열 생산을 위한 S/W 제품계열의 공통 아키텍처를 정립하는 것을 목표로 하고 있다.

• The KIPS Transactions:PartD
• /
• v.13D no.1 s.104
• /
• pp.51-60
• /
• 2006

Product Line Engineering(PLE) is an effective software development technique which produces applications using core assets. Because of reusing the core assets, PLE can save cost for developing products in a domain but increase reusability. There are about ten PLE methodologies available, but there are not yet common agreements on PLE process and artifacts. This makes developers harder to choose a methodology and to apply it in practice. A comprehensive technical evaluation and comparison on existing PLE methodologies would be essential for practitioners. In this paper, we present a technical assessment of representative PLE methodologies; FAST, SEI SPL, PuLSE, Bosch's PL proceis, FOPLE, ESAPS, KobrA/PoLITe, Alexandria, COPA, QADA. They are compared in the criteria of process, artifacts, instructions, and special features. And we identify common or variable elements between methodologies and confirm elements to be improved in each PLE methodology. The assessment result would be well utilized in defining a practical methodology for PLE projects and in choosing an appropriate methodology among available ones.