• Journal of KIISE:Software and Applications
• /
• v.32 no.9
• /
• pp.835-846
• /
• 2005

A Product Line (PL) is a set of products (applications) that share common assets in a domain. Product Line Engineering (PLE) is a set of principles, techniques, mechanisms, and processes that enables the instantiation of produce lines. Core assets, the common assets, are created and instantiated to make products in PLE. Model Driven Architecture (MDA) is a new software development paradigm that emphasizes its feasibility with automatically developing product. Therefore, we can get advantages of both of the two paradigms, PLE and MDA, if core assets are represented as PIM in MDA with predefined automatic mechanism. PLE framework in the PIM level has to be interpreted by MDA tools. However, we do not have a standard UML profile for representing core assets. The research about representing PLE framework is not enough to make automatically core assets and products. We represent core asset in PIM level in terms of structural view and semantic view. We also suggest a method for representing architecture, component, workflow, algorithm, and decision model. The method of representing framework with PLE and MDA is used to improve productivity, applicability, maintainability and qualify of product.

• Journal of KIISE:Software and Applications
• /
• v.33 no.6
• /
• pp.550-563
• /
• 2006

Software product line engineering is a method that prepares for the future reuse and supports to seamless reuse in application development process. Commonality and variability play central roles in all product line development processes. Reusable assets will become core assets by explicitly representing C&V. Indeed, the variabilities that art identified at each phase of core assets development have different levels of abstraction. In the past, these variabilities have been handled in an implicit manner and without distinguishing the characteristics of each core assets. In addition, previous approaches have depended on the experience and intuition of a domain expert to recognize commonality and variability. In this paper, we suggest a 2-dimensional analyzing method that analyzes the variabilities of core assets in software product line. In horizontal analysis process, the variation types are analyzed in requirements, architecture, and component that are produced at each phase of development process. In vertical analysis process, variations are analyzed in different abstract levels, in which the region of commonality is identified and the variation points are refined. By this method, the traceability of variations between core assets will be possible and core assets can be reused seamlessly.

• Journal of KIISE:Software and Applications
• /
• v.33 no.3
• /
• pp.277-288
• /
• 2006

Product line engineering (PLE) is a new effective approach to software reuse, where applications are generated by instantiating a core asset which is a large-grained reuse unit. Hence, a core asset is a key element of PLE, and therefore the reusability of the core asset largely determines the success of PLE projects. A tore asset is a reusable part not a whole system, and supports not only variable functions but also common functions. However, there are limitations to evaluate reusability of core asset that has these unique characteristics. This paper proposes a comprehensive quality system for evaluating the reusability of core assets, based on ISO/IEC 9126. We first identify the key characteristics of core assets, and derive the set of quality attributes that characterizes the reusability of core assets. finally, we define metrics for each quality attribute. In addition, we provide guidelines for applying the metrics and perform a case study based on rental product line. Using the proposed quality system, reusability of core assets can be more effectively and correctly evaluated.

• Journal of KIISE:Software and Applications
• /
• v.32 no.4
• /
• pp.237-246
• /
• 2005

Product Line Engineering(PLE) is one of the technologies that develop applications economically reusing core assets. PLE consists of Framework Engineering(FE) and Application Engineering. Framework Engineering is to develop core assets that have common functionality shared by a set of family members. Application Engineering is to develop a specific application by instantiating the core assets. The PLE process increases reusability and efficiency because a specific application is developed by using core assets with less time and effort. Since definition of PLE artifacts and relationship between artifacts are not clear. developers have several troubles to make artifacts based on PLE process, are difficult to maintain consistency between artifacts, and do not use PLE process more practically. In this paper, we define meta-models of artifacts that are produced in PLE activities of PLE process and describe the traceability relationship between artifacts by using traceability map and guidelines that can apply traceability relationship. Finally, we define the way how trace links and guidelines of traceability map are applied.

• Journal of KIISE:Software and Applications
• /
• v.33 no.2
• /
• pp.154-166
• /
• 2006

Product Line Engineering(PLE) is a software reuse paradigm that core assets are defined using common features in a domain and are instantiated in various applications. To apply the core asset effectively, variants which satisfy application requirements are extracted and the core asset should be also instantiated based on the variants. For the work, variability on architecture and components should be extracted exactly and an instantiation process and guidelines should be defined based on this variability In this paper, we define variability types depending on core assets elements and describe artifact templates related to tile variability. We also propose a systematic process which uses defined core assets including variability and verify practicability of the proposed process and variability expression through doing ease study. If utilizing with the proposed process in PLE, it can be feasible to model concrete core asset and variability and to utilize practical application engineering.

• The KIPS Transactions:PartD
• /
• v.13D no.4 s.107
• /
• pp.565-572
• /
• 2006

Product Line Engineering (PLE) is an effective reuse methodology where common features among members are captured into core assets and applications are developed by reusing the core assets, reducing development cost while increasing productivity. To maximize benefits in developing systems, business case analysis for PLE is essential. If the scope for core assets is excessively broad, it will result in high cost of asset development while lowering reusability. On the other hand, if the scope is too narrow, it will result in a limited applicability which only support a small number of members in the domain. In this paper, we propose a process for business case analysis for PLE and for deciding economical analysis of core asset scope. Then, we define guidelines for each activity of the process. Since variability often occurs in PLE, we significantly treat the variability of features among members in detailed level. By applying our framework for business case analysis, one can develop core assets of which scope provide the most economical value with applying PLE.

• Journal of The Korea Institute of Healthcare Architecture
• /
• v.16 no.2
• /
• pp.47-54
• /
• 2010

This paper is a longitudinal study, comparing survey results between two time periods. A previous survey was conducted in 1999. After 10 years of the first survey, the second survey was conducted while utilizing the same questionnaire. A list of membership of Korea Institute of Heallthcare Architecture was used as a sampling frame. At the first survey in 1999, questionnaires of 27.3 percentage were returned, and 15.5 percentage in the 2008 survey. Healthcare design is one of the highly specialized design types in architecture. In addition, it is demanded highly specialized knowledge to solve healthcare design problems. As a professional service firm(PSF), architectural firm utilizes knowledge assets to provide design service to clients. Specialized knowledge in question is one of the core assets of PSF. The knowledge generates competitive advantages and plays an effective role as a marketing tool for PSF. However, empirical studies dealing with the knowledge characteristics of specialized design(healthcare) firms were hardly found. Thus, this study aims to trace the professional architects' perception of knowledge demands for task performance and architectural knowledge assets. The results can be used as a reference when a specialized firm in healthcare design initiates to build knowledge assets in it.

• Proceedings of the Korea Technology Innovation Society Conference
• /
• 2003.05a
• /
• pp.369-388
• /
• 2003

This research has been focused upon and analyzing Medison, once a leading New Technology-Based Firm (NTBF) in Korea with exceptionally advanced technology in 3D ultrasound diagnostic imaging devices (UDIDs) (armored with 23 subsidiaries at its peak expansion), from the perspective if Dynamic Firm Capability(DFC). The underlying hypothesis is that the various problems from its pointless pursuit of the business styles or precedents of the existing large firms might be traced to its specific characteristics as an NTBF, which should have more preferably been based upon the distinctive competences such as differentiated technologies, institutional linkages, organizational routines, and complementary assets, etc. In conclusion, for the NTBFs with different DFC domains from those of the large firms, the optimal external linkages and comprehensive integration efforts (Process) under their specific organizational characteristics and constraints (Path) are highly recommended for the continuous accumulation of their core capabilities based upon the technological assets (Position).

• Journal of Korea Technology Innovation Society
• /
• v.6 no.2
• /
• pp.228-252
• /
• 2003

This research has been focused upon and analyzing Medison, once a leading New Technology-Based Finn (N1BF) in Korea with exceptionally advanced technology in 3D ultrasound diagnostic imaging devices (UDIDs) (armored with 23 subsidiaries at its peak expansion), from the perspective of Dynamic Finn Capability(DFC). The underlying hypothesis is that the various problems from its pointless pursuit of the business styles or precedents of the existing large firms might be traced to its specific characteristics as an NTBF, which should have more preferably been based upon the distinctive competences such as differentiated technologies, institutional linkages, organizational routines, and complementary assets, etc. In conclusion, for the NTBFs with different DFC domains from those of the large firms, the optimal external linkages and comprehensive integration efforts (Process) under their specific organizational characteristics and constraints (path) are highly recommended for the continuous accumulation of their core capabilities based upon the technological assets (Position).

• Journal of KIISE:Software and Applications
• /
• v.31 no.8
• /
• pp.1010-1026
• /
• 2004

The goal of product line engineering is to support the systematic development of a set of similar software systems by understanding and controlling their common and distinguishing characteristics. The product line engineering is a process that develops reusable core assets and develops a set of software-intensive systems from a common set of core assets in a prescribed way. Currently, many software development technologies are accomplished in context of product line. However, much of the product line engineering research have focused on the reuse of work products relating to the software's architecture, detail design, and code. The product lines fulfill the promise of tailor-made systems built specifically for the needs of particular customers or customer groups. In particular, commonality and variability play central roles in the all product line development processes. These must be treated already during the requirement analysis phase. Requirements in product line engineering are basis of software development just like as traditional system development engineering, and basis of deciding other core assets' property - commonalities and variabilities. However, it is difficult to elicit, analyze and manage correct requirements. Therefore, it is necessary to develop systematic methods which can develop and manage requirement as core asset, which can be stable in anticipative change and can be well adapted to unpredictable change. In this paper, we suggest a method of managing requirements as core asset in product line. Through this method, the reuse of domain requirements can be enhanced. As a result, the cost and time of software development can be reduced and the productivity can be increased.