• Korea Information Processing Society Review
• /
• v.13 no.6
• /
• pp.62-77
• /
• 2006

• The Journal of Society for e-Business Studies
• /
• v.24 no.3
• /
• pp.53-71
• /
• 2019

As software systems become more complex and larger, software systems require a way to reuse software components or modules to provide new functionality. This paper designed a development method of web system combining SOA(Service Oriented Architecture) with MPSL(Multi-Software Product Line). According to provides SOA and MPSL, this paper suggested to service providers and service users to provide and reuse variable services. From the viewpoint of service provider, the suggested method identifies and implements reusable variable services as features by syntax-based, functional-based, and behavior-based methods applying feature identification guidelines and manages them as reuse assets. From the user's point of view, it is possible to develop a web system by constructing a service by workflow model as a method of structure and reconfigure services. As a result of measuring the reuse of the web system constructed in this paper by the function point, the cost reduction effect was verified by applying it to the similar project with the increase of reuse.

• Communications of the Korean Institute of Information Scientists and Engineers
• /
• v.24 no.11 s.210
• /
• pp.59-71
• /
• 2006

• Communications of the Korean Institute of Information Scientists and Engineers
• /
• v.24 no.3 s.202
• /
• pp.50-58
• /
• 2006

• Journal of KIISE:Software and Applications
• /
• v.36 no.6
• /
• pp.431-442
• /
• 2009

The Software Product Line (SPL) engineering is one of the most promising software development paradigms. With Feature-Oriented Reuse Method (FORM), reusable and flexible components can be built to aid the delivery of various software products such as mobile phone and digital TV applications based on commonalities and variabilities identified during Feature modeling. Model Driven Architecture (MDA) is also an emerging technology which supports developing software products to work on different platforms with platform independent models (PIM). Combining advantages of these two approaches is helpful to build a group of software products which share common Features while working on various platforms. As first step to combine FORM with MDA, we extend UML2.0 with profiles by which FORM architectures and parameterized Statecharts can be modeled. Secondly, we provide rules to examine whether Features are allocated at positions of elements of Statecharts consistently between a Feature model and a parameterized Statechart. Some rules are designed to check the consistency between FORM architectures and parameterized Statecharts. A case study on an elevator control system is provided to demonstrate the feasibility of our modeling approach and consistency checking rules.

• The KIPS Transactions:PartD
• /
• v.12D no.4 s.100
• /
• pp.589-600
• /
• 2005

Application developers need effective reuseable methodology to meet rapidly changes and variety of users requirements. Product Line and CBD(Component Based Development) offer the great benefits on quality and productivity for developing the software that is mainly associate with reusable architectures and components in a specific domain and rapidly changing environments. Product line can dynamically focus on the commonality and variety feature model among the products. The product line uses the feature modeling for discovering, analyzing, and mediating interactions between products. Reusable architectures include many variety plans and mechanisms. In case of those architecture are use in product version for a long time, It is very important in architecture product line context for product line design phase. Application developer need to identify the proper location of architecture changing for variety expression. It is lack of specific variety managements to design the product line architecture until nowdays. In this paper, we define various variety types to identify the proper location of architecture changing for variety expression and to design the reusable architecture. We also propose architecture variety on feature model and describe variety expression on component relations. We implemented the web learning system based on the methodology. We finally describe how these methodology may assist in increasing the efficiency, reusability, productivity and quality to develop an application. In the future, we are going to apply the methodology into various domain and suggest international and domestic's standardization.

• Proceedings of the Korean Information Science Society Conference
• /
• 2004.10b
• /
• pp.430-432
• /
• 2004

본 논문에서는 프로덕트 라인 개념을 활용하여 전자 카달로그 운영 프로세스를 구축하고자 한다. 전자 카달로그는 reactive approach(1)방법으로 프로덕트 라인 개발에 접근하여 기본적인 핵심적이고 표준적인 프로세스만 우선적으로 정의하여 각 세부항목을 명시하고 이를 기반으로 프로세스의 기능을 확장하고자 한다 FORM 방법론에서 제안한 휘처 모델링 방법을 통해 얻어진 공통점과 차이점을 이용하여 scoping을 수행하였으며 이를 기반으로 필수 프로세스와 지원 프로세스로 분류하였다. 전자 카달로그 표준안에서 제안한 비즈니스 프로세스, 표준안 보고서, 프로세스 관리 계획 등을 기본 자료로 하여 각 애플리케이션에 적합한 product가 만들어지도록 production plan을 수립하였다.

• Journal of KIISE:Software and Applications
• /
• v.36 no.7
• /
• pp.539-547
• /
• 2009

Software product line (SPL) engineering is an emerging paradigm for successful software reuse and has been adopted for various industrial and consumer products to improve their productivity and quality. However, most SPL methods require high initial costs and long development time, which makes many companies hesitate to adopt the SPL paradigm. In this paper we introduce a method to construct an SPL by extracting core assets from legacy components based on the feature model, which requires less initial time and effort. We also present a case study on cable set-top box software to illustrate the applicability of this method, and lessons learned that will provide guidelines for many companies to adopt the SPL paradigm.

• Journal of KIISE
• /
• v.43 no.4
• /
• pp.460-469
• /
• 2016

Internet of Things (IoT) is an environment where various devices are connected to each other via a wired/wireless network and where the devices gather, process, exchange, and share information. Some of the most important types of IoT devices are mobile IoT devices such as smartphones. These devices provide various high-performance services to users but cannot be supplied with power all the time; therefore, power management appropriate to a given IoT environment is necessary. Power management of mobile IoT devices involves complex relationships between various entities such as application processors (APs), HW modules inside/outside AP, Operating System (OS), platforms, and applications; a method is therefore needed to systematically analyze and manage these relationships. In addition, variabilities related to power management such as various policies, operational environments, and algorithms need to be analyzed and applied to power management development. In this paper, engineering principles and a method based on them are presented in order to address these challenges and support systematic development of IoT device power management. Power management of connected helmet systems was used to validate the feasibility of the proposed method.

• Journal of the Korea Society of Computer and Information
• /
• v.26 no.11
• /
• pp.101-110
• /
• 2021

The Weapon Control Software performs the function of supporting weapon operation within the Naval Combat System in connection with the Weapon System. As Weapon Control Software depends on an Weapon System, it has the characteristic that software modification is unavoidable with the change in Interface information. Modification of software causes an increase in development costs since it must take verification step such as software reliability test. In this paper, We design the standard architecture of weapon control software to minimize the modification elements of existing weapon control software. For Interface information management, Feature Model were applied to make a division between common factor and variable factor. In addition, Strategy Pattern were applied to improve the software design. Software evaluation test results show that new architecture provides better modifiability and reuse than existing software as well as the cost of development decrease.